Two reviews in one round. The repair planner returned changes-requested (no P1s,
four reachable P2s, all applied in pixelpass `9145b2a`); the 0c actor design
returned four blocking issues, all accepted, plus a concession on epoch.
Recorded because three of them generalise:
- A prescribed fix was not implementable as written. "Use `pactl -f json list
modules`" is sound reasoning against an API that does not exist: on pactl 17
those records carry no module index, and `unload-module` takes only an index.
The reachability rule now applies to prescriptions, not just findings.
- The actor's bounded join would have disarmed `Drop` by moving the thread handle
into `spawn_blocking` — the same defect shape as round 15's, a defence disarmed
exactly when needed.
- Epoch was over-specified and my vacuity instinct was right: serial equality is
the entire identity guarantee, so epoch is diagnostic and explicitly not a gate.
Measured on the live graph rather than argued: recorded module arguments are
byte-exact with `@DEFAULT_SINK@` unresolved (both load-bearing for exact-form
matching), and two sinks may share one `node.name` with capture attaching to the
OLDER one in 3 of 3 trials — so a surviving wedged owner silently steals the next
session's capture instead of merely risking a collision.
0c step 2 is sliced into S2–S5 so each lands reviewed. Nothing reopens D6: the
connection-owned-sink design is unchanged, and a material part of the growth is
pre-existing debt 0c forced into the light.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
molluskandClaude Opus 5
76c1a13e11