Why the browser extension stops at the draft box
Reuse a platform session without uploading cookies, executing remote code, or bypassing user confirmation.
A browser extension sits in a privileged position. It can read the current page and may reuse the user's authenticated session on a publishing platform. The closer it gets to publication, the clearer its boundary must be.
Platform sessions stay in the browser
The DraPub extension can save a platform draft using the current browser session, but platform cookies, tokens, and tickets are not uploaded to DraPub Backend or written to long-lived logs. DraPub's own JWT stays in session storage.
Web cannot directly command publication
The extension accepts human-approved content packages only and validates the message origin and configured Web Origin. Even an approved package requires final confirmation in the extension before saving.
Persist the task before execution
Manifest V3 service workers can be recycled. A publishing task must enter durable local state before performing platform actions. After interruption, the extension can decide whether to query, retry, or wait instead of creating duplicates.
Stopping at the draft box is not missing capability. It is a practical accountability boundary: the system prepares reliable content while the user keeps the final platform decision.
