zeroclaw/docs/operations
Argenis cb1134ea44
Merge pull request #2851 from zeroclaw-labs/pr/ci-docs-devex-20260305
docs(ci): add branch-protection baseline, coverage lane, and Windows bootstrap
2026-03-05 09:49:54 -05:00
..
branch-protection docs(ci): add branch-protection baseline, coverage lane, and windows bootstrap guidance 2026-03-05 06:50:00 -05:00
branch-protection.md docs(ci): add branch-protection baseline, coverage lane, and windows bootstrap guidance 2026-03-05 06:50:00 -05:00
canary-gate-runbook.md feat(ci): formalize canary cohorts and observability policy 2026-02-25 22:29:26 +08:00
ci-cd-blacksmith-optimization-report-2026-03-05.md docs(ci): add branch-protection baseline, coverage lane, and windows bootstrap guidance 2026-03-05 06:50:00 -05:00
connectivity-probes-runbook.md ci: remove dev-to-main promotion gate and align main flow 2026-02-28 14:06:08 +08:00
docs-deploy-policy.md docs(ci): document docs deploy promotion and rollback policy 2026-02-25 21:55:13 +08:00
docs-deploy-runbook.md docs(ci): document docs deploy promotion and rollback policy 2026-02-25 21:55:13 +08:00
feature-matrix-runbook.md docs(ci): align nightly governance docs with active matrix profile 2026-02-25 23:01:49 +08:00
ghcr-tag-policy.md docs(release): document GHCR vulnerability gate policy 2026-02-25 21:35:57 +08:00
ghcr-vulnerability-policy.md ci(security): add pre-push trivy gate and workflow-script safety checks 2026-03-05 06:46:35 -05:00
nightly-all-features-runbook.md docs(ci): align nightly governance docs with active matrix profile 2026-02-25 23:01:49 +08:00
prerelease-stage-gates.md ci: remove dev-to-main promotion gate and align main flow 2026-02-28 14:06:08 +08:00
README.md ci: add provider connectivity probes matrix and runbook 2026-02-24 14:38:08 +08:00
required-check-mapping.md docs(ci): add branch-protection baseline, coverage lane, and windows bootstrap guidance 2026-03-05 06:50:00 -05:00

Operations & Deployment Docs

For operators running ZeroClaw in persistent or production-like environments.

Core Operations

Common Flow

  1. Validate runtime (status, doctor, channel doctor)
  2. Apply one config change at a time
  3. Restart service/daemon
  4. Verify channel and gateway health
  5. Roll back quickly if behavior regresses