docs: replace canary-gate references with rolling-host rollout - #65
Merged
Conversation
The org retired the isolated canary release-proving process; releases now roll out one host at a time under real production traffic with a lock-revert rollback (melodic-software/provisioning#145). Update every present-tense process claim that named the canary as a live gate: the deferred-capability admission criteria, the runtime-isolation verification claim, the github-jit-proof doctor skip rationale (and its test fake), and the dependency-drift PR guidance. Historical records of what the canary once proved stay, marked as retired. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TPPLWAtX5BWyEmghrKkYYF
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Part of the CI-runner canary decommission (companion to melodic-software/provisioning#145, melodic-software/ci-workflows#125, melodic-software/standards#157). No functional change — prose and one Detail string only.
docs/roadmap.md: deferred-capability admission now requires "a first rolling-host rollout under production traffic with the documented health checklist" instead of a canary.docs/worker-image.md: runtime isolation is observed live during each release's first rolling-host rollout; the zstd origin story is marked as the retired canary process (historical record kept).internal/app/doctor_inspector.go+doctor_test.go:github-jit-proofskip rationale updated together — the first enable on a rolling-host rollout performs the JIT proof under real traffic..github/workflows/dependency-drift.yml: PR-body guidance now says "CI, a rolling-host rollout, and independent review".README.md: drops "isolated canary" from the acceptance-gate sentence.Verification
go test ./...locally: all pass exceptTestCurrentUserNamedPipeRoundTrip, which fails identically on an unmodified tree because this machine's live production controller owns the control pipe — environmental, not related; hosted CI has no live controller.🤖 Generated with Claude Code
https://claude.ai/code/session_01TPPLWAtX5BWyEmghrKkYYF