{% extends 'base.html' %}{% block title %}The rich-cli case · docs-drift{% endblock %}{% block content %}<main id="main" class="voice-page"><div class="eyebrow">Real repository · pinned evidence · 22 October 2026</div><h1>One letter. A failed command.</h1><p class="subline">During this build session, we tried rich-cli's documented option to render its README with line numbers. It failed. This is a reproduced investigation, not a claim about the owner's past experience.</p>
<section class="insight"><h2>1. Reproduce</h2><pre><code>rich README.md --line-number
Error: No such option '--line-number'.
exit: 2

rich README.md --line-numbers
exit: 0</code></pre><p>Python 3.13.7, rich-cli 1.8.1, Click 8.5.0; UTF-8 console encoding. These runtime checks were separate from the static scanner, which never executes target code.</p><a href="/static/evidence/runtime.json">Actual runtime observations</a></section>
<section class="insight"><h2>2. Follow the evidence</h2><p>Snapshot: <code>46f4d2469097be395558768714a5f07ebccf1412</code></p><ol><li><a href="https://github.com/Textualize/rich-cli/blob/46f4d2469097be395558768714a5f07ebccf1412/README.md#L61">README:61</a> says <code>--line-number</code>.</li><li><a href="https://github.com/Textualize/rich-cli/blob/46f4d2469097be395558768714a5f07ebccf1412/src/rich_cli/__main__.py#L358">Source:358</a> declares <code>--line-numbers</code> / <code>-n</code>.</li><li><a href="https://github.com/Textualize/rich-cli/commit/567f6c848ee5efa8eef9d6c96ffa3c23b802da4f">567f6c84 — added help</a> introduced the incorrect wording, established by Git blame/show.</li></ol><p>The scanner locates the missing option but returns no introducing commit. Manual Git inspection supplies the doc commit above. No later breaking rename is established.</p><a class="example-chip" href="/scan/example-rich-cli-reviewed">Fresh scan and graph →</a></section>
<section class="insight"><h2>3. Check the counterexamples</h2><p>All four drift findings in the saved scan were reviewed by Codex using source and command execution. Selected, agent-assisted sample; no independent human labels or population accuracy claim.</p><table><thead><tr><th>Doc token</th><th>Review</th><th>Evidence</th></tr></thead><tbody><tr><td><code>--line-number</code></td><td>Confirmed defect</td><td>exit 2; plural option exits 0</td></tr><tr><td><code>--p</code></td><td>Confirmed defect</td><td>exit 2; <code>-p</code> exits 0</td></tr><tr><td><code>.md</code></td><td>False positive</td><td>Extension prose; source:514 recognizes it</td></tr><tr><td><code>.json</code></td><td>False positive</td><td>Extension prose; source:516 recognizes it</td></tr></tbody></table><p><strong>Saved sample: 2 confirmed defects, 2 false positives (n=4).</strong> The fresh scanner flags only the bad options. Recall was not measured; the frozen human benchmark is unchanged.</p><p><a href="/static/evidence/saved-scan.json">Saved scan JSON</a> · <a href="/static/evidence/fresh-scan.json">Fresh scan JSON</a> · <a href="/static/evidence/review.json">Review/provenance</a></p></section>
<section class="insight"><h2>4. Review a correction</h2><pre><code>- --line-number
+ --line-numbers
- --p
+ -p</code></pre><p>Agent-reviewed proposal, not an automatically generated or submitted upstream patch. No maintainer acceptance claimed.</p><p><strong>Verified on the pinned snapshot:</strong> the patch passes <code>git apply --check</code>. After applying it to a temporary source snapshot, both corrected option claims resolve to their declarations with verdict <code>ok</code>. This static check did not execute rich-cli and does not establish overall accuracy or recall.</p><p><a href="/static/evidence/rich-cli-correction.patch" download>Download reviewed patch</a> · <a href="/static/evidence/correction-verification.json">Before/after verification and hashes</a></p></section><p>The <code>--port</code> / <code>--listen</code> examples are separately labeled synthetic fixtures and excluded from this sample.</p></main>{% endblock %}