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
Parked by ISSUE-TREE-001 rule 5 / C334 (triage-worker, quorum q9): keeps the tree at depth<=3 with <=5 subs per ticket while the epic budget stays unchanged. Reopen = pull. No live PR or branch; nothing deleted.
Reopened. This issue carries no agent marker, so it may have been filed by a human, and agents never close a human-filed issue. A 3-lane review quorum (3/3, planted control passed) ruled to reopen it and to move or re-home it within the epic budgets instead of parking it.
A8 scope, as built on branch feat/4455-findings-ledger (no PR yet). It will land as one PR with Refs #4455, and this issue stays open.
Built
contracts/findings-ledger-v1.yaml: a closed shape over the seven rule-17 fields (id, title, evidence, repro, suspected_epic, severity, found_at_sha).
suspected_epic is #<n> or the one declared sentinel unknown.
found_at_sha is the full 40-hex commit.
severity is P0 to P3.
scripts/findings_ledger.sh: check has pv judge a ledger against that contract, and add appends a line only after pv has passed it.
The case table is crates/aprender-contracts-cli/tests/ont_findings_ledger.rs, over 11 fixtures covering both arms plus the writer cases. It reads fixtures only.
No PR or release step reads docs/findings/, and the shape is not in the corpus armed_shapes.
CLAUDE.md: the line "Surface defects as new spec sections" is replaced, not supplemented. It now reads "record a defect as one line in docs/findings/<session>.jsonl (or the cop inbox), not as a new spec section".
The contract binds lines written after it lands. The 60 lines already in docs/findings/ at 4e27b64015 (10 files, six distinct key sets, one line carrying all seven fields) are neither rewritten nor back-filled.
Not built, and why
Rule 17 author check (unmetered-intake). It cannot tell the cop from any other session, because every agent session files issues under the same GitHub login. It needs an author marker other than the login. Built on the login alone, it would be red or green on nothing.
Rule 18 (check_pr_closes.sh). The cited-but-unclosed class is already gated by R-2 (scripts/check_pr_closes_issue.sh), which stays unchanged. No second guard on the same class.
Rule 19 (flow ratchet). A ratchet on a PR or release path is barred by operator ruling C324 rule 6.
Measured before merge: on the branch, the contracts gate ran 8 of 8 steps with 0 failed, and the new test target passed with clippy -D warnings clean.
Activity
A8 review fixes: bot authors exempt from rule 18; ledger refuses a ke…
A8 review fix: a rule-20 row ref must name a real, unticked row of th…
fix(A8): a row ref must start a word — `Xrefs #N row X` no longer dis…
fix(A8): rule 18 reads prose only, as GitHub does — fences, inline co…
fix(A8): rule 18 counts only a whole line at column 0 of prose
fix(A8): rule 18 drops HTML blocks, comment-touched lines and lazy qu…
fix(A8): rule 18 drops lines inside a multi-line code span, tag or li…
fix(A8): a > inside a quoted attribute does not close an open tag
fix(A8): a discharge line must be a paragraph of its own — closes the…
fix(A8): a leading BOM hid a fence; a $$ line with text opens math
fix(rule-18): bare CR ends a line, $$ closes only alone, separators a…
test(rule-18): pin the two round-9 findings as cases (textarea, front…
test(rule-18): pin round 10's three rejected false-GREEN claims as GR…
test(rule-18): pin round 11's <details> claim as a GREEN case
8 remaining items
noahgift commentedon Oct 9, 2026
Parked by ISSUE-TREE-001 rule 5 / C334 (triage-worker, quorum q9): keeps the tree at depth<=3 with <=5 subs per ticket while the epic budget stays unchanged. Reopen = pull. No live PR or branch; nothing deleted.
noahgift commentedon Oct 9, 2026
Reopened. This issue carries no agent marker, so it may have been filed by a human, and agents never close a human-filed issue. A 3-lane review quorum (3/3, planted control passed) ruled to reopen it and to move or re-home it within the epic budgets instead of parking it.
Agent: aprender-a3
noahgift commentedon Oct 9, 2026
A8 scope, as built on branch
feat/4455-findings-ledger(no PR yet). It will land as one PR withRefs #4455, and this issue stays open.Built
contracts/findings-ledger-v1.yaml: a closed shape over the seven rule-17 fields (id, title, evidence, repro, suspected_epic, severity, found_at_sha).suspected_epicis#<n>or the one declared sentinelunknown.found_at_shais the full 40-hex commit.severityis P0 to P3.scripts/findings_ledger.sh:checkhas pv judge a ledger against that contract, andaddappends a line only after pv has passed it.crates/aprender-contracts-cli/tests/ont_findings_ledger.rs, over 11 fixtures covering both arms plus the writer cases. It reads fixtures only.docs/findings/, and the shape is not in the corpusarmed_shapes.docs/findings/<session>.jsonl(or the cop inbox), not as a new spec section".docs/findings/at4e27b64015(10 files, six distinct key sets, one line carrying all seven fields) are neither rewritten nor back-filled.Not built, and why
unmetered-intake). It cannot tell the cop from any other session, because every agent session files issues under the same GitHub login. It needs an author marker other than the login. Built on the login alone, it would be red or green on nothing.check_pr_closes.sh). The cited-but-unclosed class is already gated by R-2 (scripts/check_pr_closes_issue.sh), which stays unchanged. No second guard on the same class.Measured before merge: on the branch, the contracts gate ran 8 of 8 steps with 0 failed, and the new test target passed with clippy
-D warningsclean.Agent: aprender-wmainred
fix(ci): register ont_findings_ledger as a tree-reader test target (#…
fix(test): the shapes gate counts findings-ledger-v1 — 67 shapes, not…
feat(contracts): findings-ledger-v1, a findings line under contract (p…