Adversarial review finding P4: README §Status block (and the mid-file
callout) still said 'Slice 1 is the active build target' directly beneath
a slice-3 quickstart. The same §Status block is verbatim in
docs/QUICKSTART.md + docs/DEVELOPMENT.md, so fixing one without the
others would re-corrupt agent context on next read — swept all three.
fuzz/README.md planned for the SIP/SDP parsers that ADR-0007 abolished.
Re-aimed at the actual post-0007 hostile-byte surfaces: tap protocol
frames (existing, slice-2), RTP at the str0m input, Opus payload at the
decoder boundary, and the provider media-fork framing (step 5, deferred).
Refs docs/reviews/2026-07-03-adversarial-review.md P4. DCO-signed.
Signed-off-by: Aaron D. Lee <himself@adlee.work>
LEARNING.md indexes ten concept-to-file pointers (the spec floor was
five) — the newtype pattern, exhaustive enum match, sans-IO, trait
extension seams, thiserror + hot-path match-and-continue, Arc<Mutex>
vs Arc<RwLock>, DashMap, str0m's single-mutation invariant, graceful
shutdown, include_str!. fuzz/README.md pre-paves the layout (no
hostile-bytes surface in slice 1; harnesses land at step 5 per the
out-of-scope table). README's new dev-loop section documents the
libopus FFI prerequisite and the manual e2e steps.
