Delivery
Build, release, and documentation output authorities.
HEAD a63778e| Concern | Authority |
|---|---|
| Commands, dependency order and workspace composition | Root package.json |
Docs prerender and apps/site/dist/docs merge | apps/docs/react-router.config.ts and scripts/docs/merge-build.mjs |
| Emitted pages, search and Agent resources | scripts/docs/verify-build.mjs |
| Package version, provenance and publication | Release workflow and scripts/release |
Development exposes Canvas at / and proxies Fumadocs at /docs. Production
deploys Canvas from apps/canvas/dist and assembles the public site in
apps/site/dist; deployment settings
belong to the site. Delivery composes outputs but does not own their business or wire contracts.
Documentation freshness
apps/docs/content/docs-head.json is the committed source revision against which
the whole documentation set was last reviewed.
- Review committed changes after that revision plus the current worktree.
- Route affected contracts through Development; update an owner route when a new contract has no destination.
- Leave prose unchanged when implementation changes preserve the documented contract, but still count the page as reviewed.
- After affected pages and emitted outputs pass verification, advance
headto the full SHA of the reviewed commit.
A clean review may advance head without a prose change. Never record dirty or
worktree state, and never advance the baseline automatically during a build.
A release tag is stable SemVer shared by both package manifests and their lockfile entries. Packed tarballs must pass installation, public export and font asset smoke checks before publication. Reruns skip each package version already on npm and replace assets on an existing GitHub release.