Named favela-cli and favela-native as the sibling surfaces. Neither exists — `ls` confirms — and the real two are favela-surface and favela-surface-android. The env var count said ~38; bin/favela-web.js reads 33 distinct process.env names. The Run section documented `npm test` as "node suite" and test:ws, and omitted test:bare entirely, which is where the appview and everything that opens a corestore is tested. All three are now listed, with the file count (74) and the reason the node script exists: those files are the runtime-agnostic layer and say so in their own headers. Noted as a divergence from the fleet's brittle-bare gate rather than left to look like an oversight. And stated the failure rather than leaving a reader to find it: `npm test` dies at test/strip-vectors.test.mjs, which reads spec/vectors/markdown-strip.json. That file moved to favela-markdown on 2026-09-02 (spec/MOVED-record-specs.md records the move) and the test did not go with it, so the suite has aborted on the first file since. Pre-existing and unrelated to this commit — the test was added 2026-08-05 in 1be2a41, the vectors left in 71f2724. Not fixed here because removing a test file is a decision, not a docs edit. The case for removing it: favela-markdown's test/strip.test.js runs the same vectors against the real stripper ("every vector reproduces byte-for-byte", plus facet invariants), while this one only ever checked the vectors were well-formed — its own header says "No stripper exists yet". Keeping a validator here also re-creates exactly the coupling the MOVED note gives as the reason for the move. Glyph count 3 -> 0. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>