Publish a COMPLETED tree (require_review flow)
Promote a COMPLETED tree to PUBLISHED.
Only meaningful when the app has require_review=True. Apps without
require_review serve COMPLETED to the daemon directly and never need
to publish. Calling this on an app with require_review=False is still
allowed — the row gets stamped published_at/published_by — but it
has no functional effect on what the daemon serves.
Status guard: only COMPLETED can be published. PROCESSING means the workflow is still writing; FAILED has nothing to ship; PUBLISHED is a no-op (idempotent).
Authorizations
API Key or JWT User Token. If using an API Key, set the X-As-User header to act as a specific user. A JWT User Token is always scoped to a specific user.
Path Parameters
Response
Successful Response
Sidecar describing an in-flight (or just-failed) regeneration.
Present only on the dashboard path (include_published=true) when a newer
PROCESSING/FAILED row exists behind the served ready tree — the served body
stays the last COMPLETED/PUBLISHED tree so the brain never blanks out
mid-regen, and this block is how the UI knows to show a progress banner.