feat(reports): leftover-map coverage on grouping comparison graphic (v2.63.0) - #845
Conversation
…v2.63.0) Caption leftover-map complete-case coverage on the grouping comparison leftover-map graphic from already-named leftover_map_coverage (ADR 0306). Distinct accessible name Leftover map comparison graphic coverage. Omit item/incomplete notes on that comparison plot. Never invent a leftover score or a theta.
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueThanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Cycle 2026-08-31 04:40 KST. Writes work as seonghobae. Head Caption leftover-map complete-case coverage on the grouping comparison leftover-map graphic from already-named leftover_map_coverage. Distinct accessible name Independent APPROVE is required. Do not self-approve. Do not squash-merge onto the unprotected leftover base. Issues #79 and #87 stay open. #96 is already closed. |
|
Cycle write probe 2026-08-31: leftover-map comparison graphic coverage (#845 @ 7c026df) remains stacked for independent APPROVE. Next buyer gap is leftover-map item complete-case coverage on that comparison graphic (distinct from strip Leftover map comparison item coverage). Do not self-approve. Synthetic fixtures only. |
1 similar comment
|
Cycle write probe 2026-08-31: leftover-map comparison graphic coverage (#845 @ 7c026df) remains stacked for independent APPROVE. Next buyer gap is leftover-map item complete-case coverage on that comparison graphic (distinct from strip Leftover map comparison item coverage). Do not self-approve. Synthetic fixtures only. |
|
Cycle retry (2026-08-31): GitHub write probe on leftover-map comparison-graphic stack. Independent APPROVE still required; this comment is not a review. Next increment is ADR 0307 / v2.64.0 leftover-map item complete-case coverage on the grouping comparison leftover-map graphic (distinct aria-label "Leftover map comparison graphic item coverage"). Do not squash-merge this stack onto unprotected bases. Leave open. |
|
Stacked next increment opened as leftover-map item complete-case coverage on the grouping comparison leftover-map graphic (ADR 0307 / v2.64.0) on |
Summary
Caption persisted leftover-map complete-case coverage on the grouping-comparison leftover-map graphic when
leftoverMapCoverageCountsreturns usable integers (ADR 0306 / v2.63.0). Post coverage remains independent of item/incomplete coverage. No SQL/new columns and no coverage inference from marker/pair counts or other leftover-map statistics.Live authority
#844@0882cc90a1af545d9d67e0965134c7686a1196718d37896a5246cd0045a9c210b504b95941a78f84Proposedregression through feat(reports): leftover-map axis share on grouping comparison graphic (v2.62.0) #844Parent convergence
The old child was authored against #844
c25b0551.... After #844 moved, #845 inheritedtests/test_compare_graphic_adr_status.py, preserved its ownAmended by ADR 0305 / ADR 0306text while changing ADR 0304Accepted → Proposed, then recorded current #844 as the second parent in8d37896a.... The branch moved only by non-force fast-forward; no valid product delta was dropped.Historical
464-test/oxlint/py_compile evidence predates this exact head and is not transferred. Exact-head required/frontend/browser/a11y and PostgreSQL/k6 evidence plus independent approval remain outstanding. Any direct descendant must be reconstructed against this head before its predecessor evidence can transfer.Product invariants
0 of Mremains valid when stored counts satisfy the contract.Keep Draft until exact-head evidence and independent approval exist. No self-approval, gate bypass, force push, or destructive rebase.