docs(okf-v0.2): D6's checklist item points at the runbook
The verification criterion said the release checklist carries an upstream-version re-check. It now names the procedure that check runs, which is the part that makes it more than a reminder. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01A2aKJxLejT9S8jYwoZ9fut
This commit is contained in:
parent
499e96ed92
commit
99491fa277
1 changed files with 4 additions and 1 deletions
|
|
@ -865,4 +865,7 @@ with ourselves.
|
|||
5. V-A8: the v0.2 fixture validates under upstream's reference implementation.
|
||||
6. Boundary grep-gate still empty (`sanitize|quarantine|lexicon` absent outside
|
||||
guard imports).
|
||||
7. D6: release checklist contains the upstream-version re-check item.
|
||||
7. D6: release checklist contains the upstream-version re-check item, and it
|
||||
points at `docs/upstream-okf-upgrade-runbook.md` — the procedure the standing
|
||||
always-latest policy runs on, written after this round precisely because the
|
||||
spec was read and the shipped example bundles were not.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue