Align release policy and operational documentation
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# Release Workflow Implementation Plan
|
||||
|
||||
Status: ready for implementation; no stages completed by this planning pass.
|
||||
Status: implemented on 2026-09-28. All stages are complete.
|
||||
|
||||
Implement the [release roadmap](release.md) in the numbered order below. Each
|
||||
stage is a bounded work unit for a gpt-5.6-terra coding agent; finish its tests
|
||||
@@ -177,6 +177,12 @@ no longer require a manually recorded candidate before single-command publicatio
|
||||
|
||||
## Stage 3 — Complete documentation alignment and integrated validation
|
||||
|
||||
**Completed 2026-09-28.** Reconciled the adopted release policy with its pinned
|
||||
upstream source and ConfigKit decisions; aligned the runbook, development guide,
|
||||
and roadmap records with the implemented command. Bash syntax, focused release
|
||||
tests, local documentation links, whitespace review, and the final real baseline
|
||||
release checker passed on Linux. No publication or push was performed.
|
||||
|
||||
Reconcile `docs/policy/release.md` with the pinned upstream release policy. Adopt
|
||||
shared paragraphs verbatim except for substantive local decisions. Remove the
|
||||
temporary deferral, all-remotes freshness rule, and stale prospective v0.3.0 note
|
||||
|
||||
Reference in New Issue
Block a user