Codex's adversarial review of the pure core found no *certain* P1. Two
findings taken, both mutation-verified (the fix reverted, the intended test
dies, nothing else moves):
**F2, certain, P2 — `device_props` tested the wrong kind of ambiguity.** It
required exactly one live *Device* on the claimed id rather than exactly one
live *global*. With `[Device, Port]` on one id — a missed removal, the same
precondition as every other recycled-id hazard — it kept answering from the
older Device, so a node claiming that id held a stale `session_device = true`.
That flag strips the node's owner keys and its fail-closed backstop, so a
forwarder wearing it can put its output leg back on the eligible side. Now:
one slot total, and it must be the Device.
**F3, worth checking, P3 — `device.api` was corroborating by presence.**
`device.api=v4l2` under `factory.name=api.alsa.pcm.sink` satisfied the
positive classifier. No truthful configuration produces that pair, which is
the argument for reading it as an observation gone wrong rather than as
corroboration. The API must now equal the one the factory allowlist is
written for, an empty value is not a value, and the two sides disagreeing
fails closed. Tied to the allowlist being ALSA-only via a named constant.
Two findings NOT fixed here, both pre-existing and neither introduced by
round 8 — raised to the design doc instead:
- **P1, worth checking: hardware playback-to-capture paths** (Stereo Mix,
Digital Loopback) on a card whose driver is an ordinary `snd_hda_intel`.
Both its sink and source classify `session_device`, taint cannot cross the
hardware hop, and a capture app reading that source can re-emit the call.
This is `snd_aloop` again in a form the driver name cannot detect;
distinguishing it needs ALSA control inspection, which is a design change
and a new I/O surface, not a local fix.
- **P3: the 2 s readiness budget** can in principle never see an
obligation-free instant under sustained startup churn, and `TimedOut` is
sticky by design, so the process would be silent for its lifetime.
Measured here: readiness at ~3 ms with 19 binds, so the margin is three
orders of magnitude — but it wants a calibration argument, not a guess.
197 unit + 3 live green, clippy -D warnings and fmt clean.
mollusk
471b8221ff