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>
Builds out the user-facing docs tree alongside the slice-1 build target.
Kept the implementer's planned Task 7 'Slice 1 dev loop' README section
untouched — these docs are the canonical destination for that pointer.
- docs/QUICKSTART.md: 5-min path to 'hear the echo' (libopus install,
cargo run, browser steps, troubleshooting, what's happening under the
hood).
- docs/DEVELOPMENT.md: dev loop — workspace layout, per-crate iteration,
running tests, the 20 ms loop / 'drop + observe' rule, slice-1
boundaries (what NOT to add yet).
- CONTRIBUTING.md (at repo root, conventional): trunk-based dev,
CI gates, commit message style, atomic commits, code style +
learner-facing documentation policy, terminology policy, PR workflow
+ review checklist, GPL-3.0-or-later license.
- README.md: add a Quickstart pointer at the top, a Documentation table
linking to every doc, and the slice-1 build-target status block.
