poodr map: no role owns test-file lint offenses (repair deadlock) #499

Closed
opened 2026-08-24 12:54:46 +00:00 by jared · 3 comments
Owner

Context

2026-08-24 #491 run: lint gate red on Metrics/MethodLength inside the new test file. programmer-repair correctly refuses to edit tests; the fail edge routes back to programmer-repair, looping two refusal rounds (~58k tokens) until an off-map agent fixed the test file. Dispatches 12-13 handoffs record the refusals.

Task

Route test-sourced lint reds to test-writer, or scope programmer/repair lint to production files and lint test files in the test-writer gate. Record the choice in an ADR if it changes gate semantics.

Origin

  • Trigger: #491 supervised run 2026-08-24.
  • Chain: repair deadlock <- no role may edit test-file lint <- gate/role ownership gap in map design.
  • Skeptic verdict: CREATE (root-cause ownership gap with verbatim evidence).
## Context 2026-08-24 #491 run: lint gate red on Metrics/MethodLength inside the new test file. programmer-repair correctly refuses to edit tests; the fail edge routes back to programmer-repair, looping two refusal rounds (~58k tokens) until an off-map agent fixed the test file. Dispatches 12-13 handoffs record the refusals. ## Task Route test-sourced lint reds to test-writer, or scope programmer/repair lint to production files and lint test files in the test-writer gate. Record the choice in an ADR if it changes gate semantics. ## Origin - Trigger: #491 supervised run 2026-08-24. - Chain: repair deadlock <- no role may edit test-file lint <- gate/role ownership gap in map design. - Skeptic verdict: CREATE (root-cause ownership gap with verbatim evidence).
Author
Owner

Insight from the 2026-08-24 #500 session: recommend deciding this ticket together with #492 (per-gate expect declarations), not before it. #492 already rewrites the test-writer node's gates entry ({gate: test, expect: red}) and its map edges, and requires an ADR amendment — the 'scope programmer/repair lint to production files and lint test files in the test-writer gate' option would touch the exact same map lines and the same ADR, so sequencing them separately means two consecutive map/ADR churns and a rebase. Also relevant prior art: lint-fixer already refuses test files by charter (long-standing), so the 'route test-sourced lint reds to test-writer' option is consistent with existing role boundaries rather than a new exception. The #492 replay is planned for a fresh session; bundling the #499 decision into its map edit is the cheap path.

Insight from the 2026-08-24 #500 session: recommend deciding this ticket together with #492 (per-gate expect declarations), not before it. #492 already rewrites the test-writer node's gates entry ({gate: test, expect: red}) and its map edges, and requires an ADR amendment — the 'scope programmer/repair lint to production files and lint test files in the test-writer gate' option would touch the exact same map lines and the same ADR, so sequencing them separately means two consecutive map/ADR churns and a rebase. Also relevant prior art: lint-fixer already refuses test files by charter (long-standing), so the 'route test-sourced lint reds to test-writer' option is consistent with existing role boundaries rather than a new exception. The #492 replay is planned for a fresh session; bundling the #499 decision into its map edit is the cheap path.
Author
Owner

Work started 2026-08-24: resolving via the #492 bundle as decided — lint_command excludes test files, new test-lint gate on the test-writer node routes test-sourced lint reds to test-writer. See #492 for the acceptance addendum and ADR.

Work started 2026-08-24: resolving via the #492 bundle as decided — lint_command excludes test files, new test-lint gate on the test-writer node routes test-sourced lint reds to test-writer. See #492 for the acceptance addendum and ADR.
Author
Owner

Resolution

Done: Resolved via the #492 bundle: GateCommands#lint_command excludes test-path files, new test-lint gate on the test-writer node owns test-file offenses, so test-sourced lint reds route to test-writer (may edit tests) instead of deadlocking programmer-repair

Evidence: Commit c7ee237; ADR-0147 records the ownership decision; gate_commands_test.rb covers production-lint excluding test files and test-only diffs yielding test-lint with nil lint; consistent with lint-fixer's existing test-file refusal charter

Follow-ups: none

## Resolution **Done:** Resolved via the #492 bundle: GateCommands#lint_command excludes test-path files, new test-lint gate on the test-writer node owns test-file offenses, so test-sourced lint reds route to test-writer (may edit tests) instead of deadlocking programmer-repair **Evidence:** Commit c7ee237; ADR-0147 records the ownership decision; gate_commands_test.rb covers production-lint excluding test files and test-only diffs yielding test-lint with nil lint; consistent with lint-fixer's existing test-file refusal charter **Follow-ups:** none
jared closed this issue 2026-08-24 21:19:11 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
jared/cc-os#499
No description provided.