publish — share content, get link

Security — owner token: The ownerToken field from the API response is captured inside the Bash block and written directly to .claude/brewpage-history.md. The LLM only sees OK {url} or FAILED: ... — never the token value, and never the raw response body on failure.

Security — password header: {password_header} is a placeholder in the same class as {content}, {ns} and {days} — the model rewrites it before the block runs. There is no $PASSWORD shell variable and never was one that got assigned; that is exactly what made the pre-5.0.0 version publish unprotected pages. Substituting is mandatory: -H "X-Password: <pass>" when a password was chosen, the whole line deleted when it was not.

History file format — each upload block creates .claude/brewpage-history.md with this header if it does not exist yet, then appends one row:

| Date | URL | Owner Token | TTL | Type |
|------|-----|-------------|-----|------|
| 2026-04-17 12:00 | https://brewpage.app/my-ns/abc123 | `tok_...` | 5d | html |

Delete a published page:

curl -s -X DELETE "https://brewpage.app/api/{ns}/{id}" \
  -H "X-Owner-Token: TOKEN"

For sites use /api/sites/{ns}/{id}.

Update a published site (keep the same URL):

curl -s -X PUT "https://brewpage.app/api/sites/{ns}/{id}" \
  -H "X-Owner-Token: TOKEN" \
  -F "archive=@/absolute/path/to/new-bundle.zip"

To update a published site, PUT the new bundle to the same site URL with your owner token — the uploaded bundle fully replaces the file set (adds new files, removes absent ones, overwrites matching). The link never changes; no DELETE-then-POST needed.

Namespace rules: lowercase alphanumeric + hyphens, 3–32 chars. Auto-suggestion is content-derived (api-docs, report-q2) — never a random string or truncated filename.

Site uploads: directory → scripts/publish.mjs pack --dir <dir> --out <archive.zip> builds the archive, removing any stale target first (a mktemp-created 0-byte file is what made zip exit 3 before this fix), then checks zip’s exit status, verifies the result with unzip -t, and requires a non-zero size — any failure deletes the archive and exits without touching curl. The archive is POSTed as archive=@$TMPZIP and the temp file removed after. User-Agent: ClaudeCode/1.0 header included.

Archive contents — allowlist, not denylist: only known web-asset extensions (.html .css .js .json .svg .png .woff2 .pdf .md …) are packed; dotfiles, .env, .git/, node_modules/ and symlinks are dropped before zip ever runs. A supplied .zip is inspected rather than rewritten — an entry matching a sensitive pattern (.env, id_rsa, secret, credential, password, token, .pem/.key/.p12/.crt/.map) blocks the upload until you confirm.

Tests: bash brewdoc/skills/publish/tests/run.sh — 108 checks across 3 suites (archive build, zip inspection, and the SKILL.md prompt itself), no network, no real upload.