Code Foundry's documentation is organized by the job you are trying to do. Most guides describe the reusable baseline; platform-specific guides call out their provider assumptions. Adapt repository names, environments, and deployment details before copying any guide elsewhere.
- Initialization and synchronization — install, update, and diagnose a baseline.
- Configuration reference — choose workflows, runtimes, validation, and release policy.
- Workflow and CI conventions — understand triggers, checks, runners, caching, and branch protection.
- Extension points — keep custom workflows and post-release delivery alongside the baseline.
- Agent-facing validation — run local plans and checks with machine-readable evidence.
- Required capabilities and task evidence — require tasks, coverage, and retained receipts.
- Performance budgets — maintain runtime, CI, and package-size budgets.
- Product quality profiles — add acceptance checks for sites, apps, Workers, and packages.
- Merge queue validation — validate GitHub merge-group commits.
- Release management — branch topologies, Release Please, and release permissions.
- Publishing packages — npm, GitHub Releases, and provenance guidance.
- Release integrity and build provenance — immutable releases, verification, and attestations.
- Consumer qualification — test the packaged release across consumer fixtures.
- Qualified publication — publish the exact qualified Code Foundry archive.
- Declarative fleet rollouts — inventory, canaries, staged upgrades, and recovery.
- Fleet release eligibility — require verified release evidence before upgrades.
- Verified Cloudflare delivery — build, verify, canary, and promote Worker versions.
- Caching and remote caching — configure package, build, and Turborepo caching.
Add architecture notes, runbooks, and deployment instructions to this directory.
The initializer preserves docs/ during synchronization. Link supported guides
from this index and prefer task-oriented filenames.