publish-artifact-to-sites — Claude skill: ship reports to Sites

What publish-artifact-to-sites does

The skill takes a validated artifact — a canonical manifest plus a bounded snapshot — and puts it on Sites. No live source connection follows it there. What readers open is the state captured at export time.

The flow has two moving parts. $sites-building creates or reopens a checkout from the worker starter (--starter worker), one per logical report or dashboard, and later versions reuse the same Site. Then export_artifact_package writes the package: the project goes into the compatibility field site_creator_project_id, the checkout path into output_dir. $sites-hosting polls the deployment until it reaches a terminal state.

Access policy gets read before anything ships. A workspace Site counts as owner-only when the policy is custom, there is exactly one allowed_account_user_id, the single allowed_users entry carries that same id with a non-empty email, and no groups are allowed. Asked to widen reader access? That change waits until the package is exported, otherwise the verified creator seed is gone. Presentation editing needs the D1 binding named DB; swapping in a different binding name breaks it.

If the Sites lifecycle cannot be called in Work Mode, the skill retries once and falls back to the self-contained HTML mode of the owning workflow. When you asked for Sites specifically, it reports the blocker instead of quietly switching surfaces.