v1.4.3 — three commands told an agent to run things that do not exist

A documentation audit, run as eleven parallel readers over every live document, each finding independently verified against the code before it was believed. Thirty-two survived. Three of them were in the plugin's own commands — the surface an agent reads first.

The commands told an agent to run things that do not exist

/rag-your-code:index offered --compact on bootstrap, which has no such flag: bootstrap . --compact exits 2. /rag-your-code:search sent a reader to open for results the context budget dropped, but open is an action of the JSON-lines agent protocol, not a subcommand. /rag-your-code:status said "any command warns when it is stale", and none of the three commands it prescribes does — staleness is a field (stale_index in describe status, stale in search --json), and config list never opens the index at all.

Two published numbers were wrong, not stale

The vectors are 72.1% of an index, not 65.3% — re-derived from the two indexes that ship (5,229,592 B against 1,459,238 B with the vectors removed; 74.8% on the Flask copy). The figure entered in 1.2.0 and was never re-measured through four releases.

301 units carry a written description, not 304. The sidecar has held 303 entries since 1.4.0 and two are superseded, so no state of this repository ever had 304. describe status had been answering the question all along.

A retired subject was still being quoted as current

"On the foreign ruler a test declaration is 11 of 35 top-1 results" was measured on the repository retired in 1.4.0. On Flask it is 0 of 35 — none of its 1,094 test units reaches rank 1 at all. Re-derived across the three rulers that existed then, a test displaces an accepted answer on 9 of 175 questions, where 10 had been published, and the illustrative case named in ROADMAP (test_readme_badge_match) exists in no corpus a reader can open. It was a test in the retired subject.

Also

• search.vector_recall is gated on a semantic embedder (search.py:509), so the default hash never scans a vector. README section 11 listed the full scan as an unqualified current cost while section 9 already said it stays off.
• ARCHITECTURE said "there is no network code to disable". There has been since 0.8.0; the true claim is the narrower one providers.py makes — the default provider opens no socket.
• Four of twelve settings decide what an index contains became seven of twenty-two. Two rulers became four. The golden fixture is nine units, not sixty. Flask is 1,572 units, not "eighteen hundred".
• CI now runs bootstrap, search --graph and describe promote in the clean-wheel job. It claimed to run every documented command and ran none of those three — including the one SKILL.md prescribes first.

356 tests, unchanged. Every published figure re-reproduced: C 0.443/0.614/0.509 at c9df00350cbd, B 0.314/0.471/0.383 at fb1f841fa43a, A 0.200/0.286/0.238 at 5fd51169eacc, silence 0.967 own and 0.833 foreign.

Full entry: CHANGELOG.md