Skip to content

docs: sync coverage/test/Python numbers to post-#119 state - #120

Merged
DLANSAMA merged 1 commit into
mainfrom
docs/truth-sync-numbers
Aug 14, 2026
Merged

docs: sync coverage/test/Python numbers to post-#119 state#120
DLANSAMA merged 1 commit into
mainfrom
docs/truth-sync-numbers

Conversation

@DLANSAMA

Copy link
Copy Markdown
Owner

PR 1 of the documentation reconciliation pass (truth/numbers area). Numbers-only — letter grades and narrative are deliberately untouched.

Reconciles stale snapshots across the scoreboard docs against the measured post-#119 state (verified locally + from CI run this session):

Was Now
Coverage 89.1 / 89.2% 90.99% Linux / 90.68% Windows
Tests 1419 / 1459 1499 non-live (1 live deselected)
Statements 8120 8368
Python Linux 3.9 / py39 3.10 / 3.12 / 3.14
Floor margins vs Windows 88.8% recomputed vs Windows 90.68% (floor 86)

docs/quality-roadmap.md was internally contradictory — the current scoreboard table disagreed with its own header, floor-history, and ratchet-headroom paragraphs. Those now agree. Dated historical records (the 5b08720 re-verification blockquote) are preserved, with a current 2026-08-13 entry appended.

Verified: tests/test_docs_consistency.py passes (7/7), including the floor-match and the coverage-%-≥-floor drift guards.

Follow-ups (separate PRs): user-facing accuracy fixes (camera fail-closed docs, --confirm job/send semantics), historical-plan cleanup, mutation-baseline reconciliation.

Truth-sync only (grades and narrative untouched). Reconciles stale
snapshots against the measured post-#119 state:
- coverage: 89.1/89.2% -> 90.99% Linux / 90.68% Windows
- tests: 1419/1459 -> 1499 non-live (1 live deselected)
- statements: 8120 -> 8368
- Python: drop the stale "Linux 3.9" / py39 refs -> 3.10/3.12/3.14
- floor-history / ratchet-headroom margins recomputed for the 86 floor

quality-roadmap.md was internally contradictory (current scoreboard vs
stale header + floor-history + ratchet paragraphs); those now agree.
Historical dated records (the 5b08720 re-verification blockquote) are
preserved as-is and a current 2026-08-13 entry appended. docs-consistency
test passes.
@DLANSAMA
DLANSAMA merged commit df57201 into main Aug 14, 2026
6 checks passed
@DLANSAMA
DLANSAMA deleted the docs/truth-sync-numbers branch August 14, 2026 12:04
DLANSAMA added a commit that referenced this pull request Aug 14, 2026
Re-verified the 2026-07-31 post-audit residual table against current main
rather than trusting the audit snapshot. Four residuals it lists as open are
closed, and one the follow-up notes recorded as closed is not:

- S5 closed: utils.py:63-67 is now a shim delegating to jsonio; both spellings
  redact the audit's own repro identically. No weaker second implementation.
- A4 closed: mqtt_port is wired end to end (context -> printer -> mqtt_tls
  _mqtt_port -> client.connect). Doctor no longer reports a port it ignores.
- T1 closed: textual is pinned >=8.0,<9.0 (#115), not <2.0.
- A3/Q1/S1/B1/R1/R3 closed by #119, the camera opt-in work, and the TUI merge.
- Q4 NOT closed: #116 removed 81 setdefault stubs across 33 files but
  tests/bambu_test_base.py:26-29 still assigns MagicMock to sys.modules for
  paho at import time and never restores it, which is also order-dependent.
- P1, Q5, Q6, A1, A2, S3, R2, T2/WS4, W3.4 re-confirmed open with current
  file:line evidence; A1's target moved to bambu_cli.cliparse.

Plan headers carried numbers from before #119/#120 and read as live state.
Both gameplans now lead with measured current values (1499 non-live, 90.99%
Linux / 90.68% Windows over 8368 statements, floor 86, Python 3.10/3.12/3.14)
and keep the old figures marked as historical, including the a-plus W1 sizing
that was derived from the 89.4% baseline.

mutation-baseline.md claimed its per-module table reconciles to the 50.7%
headline. It does not: the seven rows are the whole only_mutate scope yet sum
to 2010 mutants against a headline 2091, leaving 81 unattributed (37 survived,
41 killed, 3 timeout). Also corrected the "residual survivors should be
cosmetic" prediction, which the same file already disproves at 21.8% with 269
survivors, and the stale "re-run mutmut on slicer/output.py" note, which was
already done on 2026-08-04.

tui-plan.md kept imperative branch instructions after its own "implemented"
banner; folded into the historical framing.

Also drops AI-vendor attribution from these two plan docs: the audience and
source lines, the "pasteable brief for a new <vendor> session" heading, and
the trailer rule, which now reads "AI/session attribution trailers" instead of
naming a product. References to the local-only agent notes filename are left
intact where removing the name would void the rule.

Docs only, no code changes. Gates: 1499 passed / 1 deselected, 91.0% total;
test_docs_consistency + test_docs_links 25 passed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant