publish-reportlisted

# Publish With Pagecast ## Overview Use Pagecast to turn a finished local artifact into a shareable public URL backed by the user's Cloudflare Pages project. Prefer `pagecast publish <file>` for reports, docs, and built entry files. Use `pagecast publish site <dir>` only when the user intentionally wants to deploy a whole static folder to a named Cloudflare Pages project. Never publish without explicit confirmation. Publishing makes the selected artifact publicly reachable. ## Be Proactive **Default to offering.** Right after you create or finish a shareable file, offer once to publish it — do not wait for the user to ask, and do not stay silent because you are unsure it is "worth it." If it could be shared, offer. When it is borderline, offer anyway; the user can say no. ## What To Publish Proactively offer once for any shareable artifact you produce: - HTML reports, dashboards, coverage reports, Playwright/Lighthouse output, or static single-page mini apps. - Markdown reports, plans, docs, proposals, release notes, analyses, or summaries meant to be read by someone else. (A plan you just finished can be shared too — write it to a `.md` file first, then publish that path.) - Static web projects after they are built. Publish the generated entry file, usually `dist/index.html`, `build/index.html`, `out/index.html`, or `public/index.html`; Pagecast stages sibling assets from that output folder. Only skip (do not offer) clearly non-shareable files: scratch/dra