docs(protocol): sweep 20 stale PROPOSED → SHIPPED state lines

[NagyVikt]

Summary

Audit pass over docs/future/PROTOCOL.md: every #### X.4.Y improvement
carrying state: PROPOSED was checked against the actual repo + git
history. 20 items have clearly already shipped on main and are flipped
to SHIPPED here. Single-file, fully reversible change.

State counts (before → after)

State	Before	After
PROPOSED	156	136
ACCEPTED	0	0
SCHEDULED	0	0
IN-PROGRESS	0	0
SHIPPED	0	20
DEFERRED	0	0
REJECTED	0	0

Updates (section → slug → representative PR)

• §1.4.1 Formal lifecycle states for every improvement entry → SHIPPED (PR docs(future): 12k-line PROTOCOL.md cataloging per-subsystem improvements #171)
• §7.4.1 Add --help and --version to stall-watcher.sh → SHIPPED (PR pkg: initial repo packaging — README, LICENSE, install.sh, skill, docs #1)
• §9.4.1 Add --help and --version to plan-watcher.sh → SHIPPED (PR feat(codex-fleet): plan-watcher supervisor + claude-runtime fallback #46)
• §10.4.1 Add --help and --version to review-queue.sh → SHIPPED (PR feat(viz): add event-sourced producer for the Review approval queue #37)
• §11.4.1 Add --help and --version to review-pane-scanner.sh → SHIPPED (PR feat(viz): close the Review approval-queue loop end-to-end #41)
• §12.4.1 Add --help and --version to auto-reviewer.sh → SHIPPED (PR Add fleet auto-reviewer daemon #99)
• §17.4.1 Add --help and --version to show-fleet.sh → SHIPPED (PR feat(codex-fleet): add show-fleet.sh operator entrypoint #139)
• §18.4.1 Add --help and --version to token-meter.sh → SHIPPED (PR feat(codex-fleet): token-discipline worker + plan-meta + tiered panes #17)
• §19.4.1 Add --help and --version to warm-pool.sh → SHIPPED (PR pkg: initial repo packaging — README, LICENSE, install.sh, skill, docs #1)
• §20.4.1 Add --help and --version to spawn-fleet.sh → SHIPPED (PR pkg: initial repo packaging — README, LICENSE, install.sh, skill, docs #1)
• §21.4.1 Add --help and --version to dispatch-plan.sh → SHIPPED (PR wip: capture pre-fleet-dispatch openspec scaffolding + script polish #133)
• §23.4.1 Add --help and --version to proactive-probe.sh → SHIPPED (PR pkg: initial repo packaging — README, LICENSE, install.sh, skill, docs #1)
• §24.4.1 Add --help and --version to claim-trigger.sh → SHIPPED (PR pkg: initial repo packaging — README, LICENSE, install.sh, skill, docs #1)
• §27.4.1 Add --help and --version to claude-supervisor.sh → SHIPPED (PR feat(codex-fleet): tighten claude-supervisor classifier + replay harness #116)
• §33.4.1 Add --help and --version to plan-tree-pin.sh → SHIPPED (PR pkg: initial repo packaging — README, LICENSE, install.sh, skill, docs #1)
• §36.4.1 Add --help and --version to supervisor.sh → SHIPPED (PR pkg: initial repo packaging — README, LICENSE, install.sh, skill, docs #1)
• §37.4.1 Add --help and --version to patch-codex-prompts.sh → SHIPPED (PR pkg: initial repo packaging — README, LICENSE, install.sh, skill, docs #1)
• §39.4.1 Add --help and --version to down.sh → SHIPPED (PR pkg: initial repo packaging — README, LICENSE, install.sh, skill, docs #1)
• §41.4.1 Add --help and --version to add-workers.sh → SHIPPED (PR pkg: initial repo packaging — README, LICENSE, install.sh, skill, docs #1)
• §42.4.1 Add --help and --version to codex-fleet-2.sh → SHIPPED (PR pkg: initial repo packaging — README, LICENSE, install.sh, skill, docs #1)

Why bare SHIPPED, not SHIPPED (PR #N)

Both scripts/protocol/check-states.sh and
scripts/protocol/protocol-state.sh parse the state token verbatim:
check-states.sh's awk validates against an exact enum
({PROPOSED, ACCEPTED, SCHEDULED, IN-PROGRESS, SHIPPED, DEFERRED, REJECTED})
and protocol-state.sh counts via ^- state: SHIPPED$. A (PR #N)
suffix would break both. PR refs are captured here in the PR body and
in the commit message instead.

Audit method

For each PROPOSED item I required:

• (a) every path in the proposal's **References.** block exists in the repo, and
• (d) the file's content visibly implements the proposal (e.g. the script's
  arg parser handles --help).

I additionally cross-checked with git log -S '--help' -- <path> to find a
representative PR whose theme matches the proposal. For §1.4.1 the
referenced governance tooling (scripts/protocol/{protocol-state,check-states}.sh)
plus the state lines themselves were shipped under PR #171.

Acceptance evidence

$ bash scripts/protocol/check-states.sh
check-states: ok          # exit 0

$ bash scripts/protocol/protocol-state.sh --summary
protocol-state docs/future/PROTOCOL.md
  PROPOSED     136
  ACCEPTED     0
  SCHEDULED    0
  IN-PROGRESS  0
  SHIPPED      20         # 0 → 20
  DEFERRED     0
  REJECTED     0

$ git diff main -- docs/future/PROTOCOL.md | grep -c '^-.*state: PROPOSED'
20
$ git diff main -- docs/future/PROTOCOL.md | grep -c '^+.*state: SHIPPED'
20

Spot-check evidence (3 items)

# §1.4.1
$ bash scripts/protocol/protocol-state.sh --summary
protocol-state docs/future/PROTOCOL.md
  ... SHIPPED 20 ...
exit=0

# §17.4.1
$ bash scripts/codex-fleet/show-fleet.sh --help
Usage: show-fleet.sh [--rebuild] [--no-kitty] [-h|--help]
...
exit=0

# §19.4.1
$ bash scripts/codex-fleet/warm-pool.sh --help
Usage: warm-pool.sh <command>
...
exit=0

Test plan

• CI: bash scripts/protocol/check-states.sh passes
• CI: bash scripts/protocol/protocol-state.sh --summary runs without
  error and reports SHIPPED count = 20
• Diff is exactly 20 lines flipped; no other content change

Risks / follow-ups

• Items §3.4.1, §4.4.1, §5.4.1, §6.4.1, §8.4.1, §13.4.1, §14.4.1, §15.4.1,
  §16.4.1, §22.4.1, §25.4.1, §26.4.1, §28.4.1, §29.4.1, §30.4.1, §31.4.1,
  §32.4.1, §34.4.1, §35.4.1, §38.4.1, §40.4.1 (--help/--version for other
  scripts) were left as PROPOSED because the target script currently
  lacks --help on main or is in flight on another agent branch. The
  parallel agent A is wiring --help/--version into a few of these
  (cap-probe, score-checkpoint, force-claim); that lane will sweep them
  in a follow-up PR.
• Item §26.4.1 (claude-spawn.sh) was deliberately skipped — the script
  has a --help flag but a pre-arg-parse env precheck fatals before
  --help is reached.
• All *.4.2 (structured logging) proposals stay PROPOSED — no script
  emits level= structured lines yet.
• All rustdoc X.4.1 proposals (43–54.4.1) stay PROPOSED — every crate
  has < 50 lines of //! docs.
• §1.4.2 (captains), §2.4.1 (full justfile), §2.4.2 (script reorg) stay
  PROPOSED — acceptance criteria not yet met.