veronica
f0d2dd9920
Applies the document contract from
docs/plans/2026-08-20_stack-docs-flatten-and-alignment.md section 3, partially:
`kind` and `status` only. `parent` is deliberately held until the flatten in
section 4 lands, so that 127 documents do not have to be re-pointed by hand
when docs/fleet/NORTH_STAR.yaml moves to docs/NORTH_STAR.yaml.
Scope, measured on origin/next at 63069149:
127 live docs = all *.md under docs/ minus docs/archive/ minus docs/_old_structure/
104 stamped here
19 held operator judgement (plan section 9), worklist in the same PR
3 held the SUPERSEDED TASKS.md stamps, which cite the moving path
1 untouched docs/fleet/FLEET-DOCTRINE.md, already stamped in W1
Kinds applied: 54 guide, 34 record, 9 spec, 6 tracking, 1 projection.
Every row carries a confidence and a one-line rationale in the worklist.
Two collisions with the existing state, both flagged rather than resolved:
1. docs/README.md:150-160 already documents a front-matter convention
(title/type/audience/status/source_of_truth) with its own allowed values.
It is applied to 4 of 127 files. Its `status` vocabulary is
current|draft|deprecated|historical; the new contract's is active|superseded-by.
The key collides. This commit lets the new contract win and rewrites
`status: current` to `status: active` on those 4 files, keeping their other
legacy keys untouched. No code reads any of them: `git grep source_of_truth`
outside docs/ returns nothing. docs/README.md still prescribes the old
convention and is an operator row, so it is not edited here.
2. Two of the plan's 20 operator rows are YAML files, not markdown
(docs/fleet/examples/roster-v2.yaml, docs/openapi-tess.yaml), and the
contract's front-matter form has no defined meaning for a .yaml document.
That gap also applies to docs/fleet/NORTH_STAR.yaml, the source of truth
itself. Raised in the worklist.
A third row from the plan, docs/fleet/north-star.md, no longer exists: W1
renamed it to docs/fleet/FLEET-DOCTRINE.md.
Verification: 104/104 parse with the expected kind and status in front matter;
the check was shown to reject a wrong kind before it was trusted. The diff
removes 4 lines total, all of them `status: current`.
39 lines
1.5 KiB
Markdown
39 lines
1.5 KiB
Markdown
---
|
|
kind: spec
|
|
status: active
|
|
---
|
|
|
|
# CI Queue Guard Purpose Semantics
|
|
|
|
- **Issue:** #1146
|
|
- **Target branch:** `next`
|
|
|
|
## Problem
|
|
|
|
`ci-queue-wait.sh` treats any result other than terminal success as asserted non-readiness. That is correct for merge readiness, but incorrect for the pre-push queue guard: a terminal failure or an empty status set means no pipeline is queued or running, so the queue is clear.
|
|
|
|
## Design
|
|
|
|
Make final-state handling purpose-sensitive while preserving the existing provider and payload safeguards:
|
|
|
|
- `--purpose push`
|
|
- wait while state is `pending`;
|
|
- return success for `terminal-success`, `terminal-failure`, and `no-status`;
|
|
- continue rejecting `malformed`, `unknown`, and unrecognized states.
|
|
- `--purpose merge`
|
|
- return success only for `terminal-success`;
|
|
- continue rejecting `terminal-failure`, `no-status`, malformed, unknown, and unrecognized states.
|
|
- `--require-status` remains authoritative: `no-status` fails for either purpose when it is supplied.
|
|
|
|
Diagnostics will explicitly distinguish a queue-clear push result from successful CI so callers cannot mistake an old failure for a green pipeline.
|
|
|
|
## Testing
|
|
|
|
Extend the process-level tri-state regression harness with separate push and merge assertions:
|
|
|
|
1. Push passes for terminal success, terminal failure, and no status.
|
|
2. Push still fails for pending, malformed, and unknown states.
|
|
3. `--require-status` makes push/no-status fail.
|
|
4. Merge behavior remains fail-closed except for terminal success.
|
|
5. Existing provider-unavailable audit behavior remains unchanged.
|