Openpress Deploy

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:

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:

npm run build              # validates + renders dist-react/

Also scan public-facing source for unfinished markers:

rg "\\[TODO:|\\[FIX:|\\[DRAFT:" "press/*/chapters" press/design.md

PDF Size Limit

Cloudflare Pages rejects any single file larger than 25 MB. A multi-press or image-heavy PDF commonly exceeds this limit.

Unless the user explicitly asks to publish the PDF, deploy without it:

npm run openpress:deploy -- --confirm --no-pdf

--no-pdf skips PDF generation and excludes it from the deploy source entirely.

If the user wants to check the PDF size first:

npm run openpress:pdf
du -sh .deploy/**/*.pdf 2>/dev/null

If the PDF is over 25 MB and the user still wants it publicly hosted, recommend a separate host (Cloudflare R2, S3, etc.) and set deploymentInfo.pdf to the external URL in the workspace config.

Deploy Commands

Dry run:

npm run openpress:deploy:dry-run

Publish after explicit confirmation:

npm run openpress:deploy -- --confirm

When To Read References

• Read references/cloudflare-pages.md when creating or repairing Cloudflare Pages config, project setup, Wrangler auth expectations, or UI deploy-button behavior.

Cloudflare Pages Deploy

Config Shape

Write confirmed deploy settings into the workspace package.json under "openpress.deploy":

{
  "openpress": {
    "deploy": {
      "adapter": "cloudflare-pages",
      "source": ".deploy/openpress",
      "projectName": "<cloudflare-pages-project>",
      "commitDirty": false,
      "requiresConfirmation": true
    }
  }
}

Prefer an explicit deploy.projectName. If it is missing, ask the user to confirm the project name before writing config or creating a Cloudflare Pages project.

Setup Workflow

1. Discover the workspace and load open-press config. 2. Confirm the document is intended for public hosting. 3. Inspect deploy config and derive the target:

• use explicit deploy.projectName;
• otherwise use a user-confirmed slug;
• do not invent and write a public target silently.

4. Ask whether to create a new Cloudflare Pages project or use an existing one. 5. Verify Wrangler auth outside source control. 6. Run dry run before real deploy.

If creating a new project, ask before running:

npx wrangler pages project create <projectName> --production-branch main

Secrets

Do not write API tokens or secrets into open-press config, Markdown, design.md, or skill files.

UI Deploy Button Contract

A UI deploy button is a review surface over the CLI workflow. It should:

• show target, source, and status before publishing;
• block when deploy.projectName is missing;
• require confirmation before posting to the deploy endpoint;
• call the same CLI-backed deploy path;
• show success URL, PDF URL, failure output, and dirty status.

It must not create a second hidden deployment behavior.