You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Surfaced by CodeRabbit while reviewing #7047, script-verified there: docs/parser-misparse-backlog.md's aggregates disagree internally, and the gaps pre-date that PR in full (verified at base 14b11cf5b, where the same deltas appear shifted by exactly the one card #7047 removes):
Header "Total card appearances" 4752 vs ranked-table sum 4732 vs section-heading sum 4712 vs actual bullet-count sum 4728 (at base).
Heading-vs-actual-bullet miscounts on causes 1, 2, 3, 5, 22 (e.g. §2's heading said 590 while listing 597 bullets, at base).
Since the file is the canonical §3.1 worklist and its counts steer contributor ROI choices, a regeneration of tables, headings, lists, and aggregates from the clustering source (so the totals are auditable) seems warranted — flagging rather than fixing in a card PR, since a wholesale regeneration is maintainer/tooling scope.
Surfaced by CodeRabbit while reviewing #7047, script-verified there:
docs/parser-misparse-backlog.md's aggregates disagree internally, and the gaps pre-date that PR in full (verified at base14b11cf5b, where the same deltas appear shifted by exactly the one card #7047 removes):Since the file is the canonical §3.1 worklist and its counts steer contributor ROI choices, a regeneration of tables, headings, lists, and aggregates from the clustering source (so the totals are auditable) seems warranted — flagging rather than fixing in a card PR, since a wholesale regeneration is maintainer/tooling scope.