---
name: io-parser-22-milestone-state
description: "IO-PARSER (releases#22): all six builder lanes GATED PASS 2026-08-27; doyle assembling the golden head, todlando stood down until golden verdict or respin"
metadata: 
  node_type: memory
  type: project
  originSessionId: 1be32cdd-c16e-48bb-80d4-de5bf5948892
  modified: 2026-08-28T09:24:22.883Z
---

**IO-PARSER (spt-bs-releases#22) — builder duty COMPLETE 2026-08-27.** Six thin lanes, each gated
by doyle before the next dispatched, all stacked linearly and none merged (ADR-0050 assembly at
milestone end):

- W1 PR #162 `a8f04aff` — funnel, taxonomy, `api state` payload, MSG_IN/MSG_OUT
- W2 PR #163 `769fb0a9` — COMMUNE / COMMUNE_FAIL
- W3 PR #164 `9fc213d8` — `@<…@>` parser, `[io]` manifest gate, DISPATCH_RESULTS
- W4 PR #165 `e1764151` — `;;` seal-mint
- W5 PR #166 `9c3a129a` — now-signal (#233) + the typed `SendVerdict` send-path return
- DOCS PR #167 `b7135d66` — the contract-doc sweep (manifest/api/checklist/llms.txt + pointers)

doyle's docs verdict named the arm that mattered: a consumer read **by a reader who gated the waves
but did not write the docs** — the blind-consumer arm I could not supply myself. My no-e2e call for
a docs lane was confirmed correct (no product behaviour to bind; IR-67 names e2e per BEHAVIOUR
wave). The code-adjacent doc-comment fix was approved in-lane rather than bounced to its own change.

**IR-52 stays OPEN in the register** — the conditional rider only fires if a lane touches the
docs-site CLI reference generator, and the docs lane did not.

**LANDED 2026-08-28.** All six PRs merged at 08:54:21Z under doyle's `96e32db8` *assembly: IO-PARSER
#22 head — W1-W5 + docs lane onto main*; `b7135d66` is an ancestor of main (verified by
`merge-base --is-ancestor`, not by a report). hertz's kill-carrier rider folded next (`594ee4bc`),
then `ba36f221` v0.64.0 shape and `91638eda` the v0.64.0 close sweep — so **IO-PARSER ships in
v0.64.0**. I learned this by reading the record on an idle check; no golden verdict message reached
me, which is worth knowing about how a milestone close arrives.

Pool `io-parser-docs` RELEASED and its target subtree reaped; worktree `.worktrees/io-parser-w1`
still holds the merged branch and its `D22_*` evidence files — removable once nobody wants them.

Fast-follow successor, NOT in this milestone: **#234** (harness-adapter event consumption) — the
funnel's bus is consumer-agnostic so #234 lands as a new reader registering a sink, never a funnel
rework. It gets its own grill first.