openpress-deploylisted

# open-press Deploy open-press deploy owns the public-release gate. Use it only when the user asks to configure, inspect, dry-run, or publish an open-press document. ## Responsibilities - Inspect deploy config in the workspace `package.json` under the `"openpress.deploy"` field. - Check target adapter, staging source, project name, and confirmation settings. - Run deploy preflight and dry runs. - Keep secrets out of source files. - Require explicit confirmation before publishing. - Report public URL and PDF URL after successful deploy. ## Boundaries - `openpress` owns generic CLI usage, non-deploy validation, local review, and the source/generated boundary. - `openpress-create-pages` owns page artifact content and visual readiness. - `openpress-create-slide` owns slide deck content and visual readiness. - This skill owns public target confirmation and deploy execution. ## Public Deploy Rule Never publish without a clear confirmation that names the target project. Good confirmation shape: ```txt This will publish the current open-press build to Cloudflare Pages project `<projectName>` from `<deploy.source>`. Do you want me to deploy now? ``` ## Preflight Before real deploy, run the commands that prove the output is ready: ```bash npm run build # validates + renders dist-react/ ``` Also scan public-facing source for unfinished markers: ```bash rg "\\[TODO:|\\[FIX:|\\[DRAFT:" "press/*/chapters" press/design.md ``` ### PDF Size Limit Cloudflare Pages