The new gate section is deliberately not fence-aware, contradicting an explicit SREQ constraint and a CLAUDE.md convention. #67

New issue

Open

opened 2026-08-25 13:57:46 +00:00 by jbr870 · 0 comments

jbr870 commented

2026-08-25 13:57:46 +00:00

Owner

Spawned from finding F-PO-43-4-14 (in-scope-deferrable) on issue #43 during decision D-PO-43-4-8.

Original scope note: The SREQ's Constraints say 'scripts/lint-conventions.sh is repo-local and fence-aware; new checks must reuse its existing fence tracker rather than line-regexing', and CLAUDE.md carries the same rule with the #50 evidence behind it. The implementation line-regexes and argues its way out in a code comment. The comment's reasoning is genuinely good for the citation checks — a fenced example that restates the rule is a restatement just the same — but the anchor-UNIQUENESS scan is the half where it bites: an anchor phrase appearing inside a fenced counter-example or a quoted 'do NOT write this' illustration in a consumer would be flagged, which is the false-positive class the fence tracker exists to prevent. Worth a recorded decision either way; the deviation currently lives only in a code comment, so a future reader cannot tell it was considered.

Disposition rationale: [CR-14] Reusing the fence tracker for the anchor-uniqueness scan is a substantial change to a gate that currently passes 20 of 20 driver-authored mutations, and substantial work does not fold into a fix round by the recommender's own rule. The deviation also deserves an explicit recorded decision rather than a code comment, because the SREQ constraint and the CLAUDE.md convention both say fence-aware and the implementation chose otherwise for reasons that are good but currently invisible to anyone who has not read that comment. Resolved under a standing instruction from the operator in this session — asked for /dev:resolve to be run and accepted all recommendations — so this follows the recommender's output rather than overriding it. The recommendation itself is disposition-recommend.sh's, computed from the finding's fix_cost, feature_value, adjacent_to_blocking and category.

This issue was deferred out of the parent feature's scope; it carries no PREQ yet. Run /dev:requirements --issue={new-number} to flesh it out before planning.

Spawned from finding `F-PO-43-4-14` (in-scope-deferrable) on issue #43 during decision D-PO-43-4-8. **Original scope note:** The SREQ's Constraints say 'scripts/lint-conventions.sh is repo-local and fence-aware; new checks must reuse its existing fence tracker rather than line-regexing', and CLAUDE.md carries the same rule with the #50 evidence behind it. The implementation line-regexes and argues its way out in a code comment. The comment's reasoning is genuinely good for the citation checks — a fenced example that restates the rule is a restatement just the same — but the anchor-UNIQUENESS scan is the half where it bites: an anchor phrase appearing inside a fenced counter-example or a quoted 'do NOT write this' illustration in a consumer would be flagged, which is the false-positive class the fence tracker exists to prevent. Worth a recorded decision either way; the deviation currently lives only in a code comment, so a future reader cannot tell it was considered. **Disposition rationale:** [CR-14] Reusing the fence tracker for the anchor-uniqueness scan is a substantial change to a gate that currently passes 20 of 20 driver-authored mutations, and substantial work does not fold into a fix round by the recommender's own rule. The deviation also deserves an explicit recorded decision rather than a code comment, because the SREQ constraint and the CLAUDE.md convention both say fence-aware and the implementation chose otherwise for reasons that are good but currently invisible to anyone who has not read that comment. Resolved under a standing instruction from the operator in this session — asked for /dev:resolve to be run and accepted all recommendations — so this follows the recommender's output rather than overriding it. The recommendation itself is disposition-recommend.sh's, computed from the finding's fix_cost, feature_value, adjacent_to_blocking and category. This issue was deferred out of the parent feature's scope; it carries no PREQ yet. Run `/dev:requirements --issue={new-number}` to flesh it out before planning.

jbr870 added the

priority:low

type:tech-debt

phase/backlog

labels

2026-08-25 13:57:46 +00:00

jbr870 referenced this issue

2026-08-25 13:57:46 +00:00

QA: intra-run lane-ownership primitive, plus a void-vs-flaky triage rule #43

jbr870 referenced this issue

2026-08-25 14:59:40 +00:00

lint-conventions.sh's 'gate piped into a filter' check covers only skill markdown, not the helper tier #105