Wayfinder map: early test-lint gate + test-file lint routing in os-sdlc:implement

jared commented

2026-08-07 12:54:55 +00:00

Owner

Destination

A locked design (recorded as an ADR) plus fully specified implementation ticket(s), pipeline-ready, for: (1) an early lint gate on test files immediately after test-writer in /os-sdlc:implement, fixed by a new test-lint-fixer agent so the programmer only ever sees lint-clean tests, and (2) test_path-aware routing at the existing late lint gate so test-file residuals dispatch to test-lint-fixer instead of deadlocking on lint-fixer (the #308 deadlock). No implementation happens on this map.

Notes

Engineering effort on plugins/os-sdlc. Skills to consult per ticket: /grilling, /domain-modeling. Decisions must respect the os-adr workflow (/os-adr:find before changing decided approaches, /os-adr:create for the final design). Supersedes the routing proposal in the body of #308 (which suggested re-dispatching test-writer); this map's grilling chose a dedicated test-lint-fixer agent instead.

Constraints already settled while charting (2026-08-07):

Destination is planning-only: design + spec'd tickets, not code.
The early-gate fixer is a NEW dedicated agent, test-lint-fixer (not a test-writer re-dispatch, not a relaxed lint-fixer charter).
Scope covers BOTH gates: the early gate is the optimization; the late-gate routing rule is the actual #308 deadlock fix.

Decisions so far

Early gate placement: where does test-lint run relative to red-assert? (#311) — red-assert brackets the gate (conditional re-run only after fixer edits); scope = files test-writer touched; safe autocorrect first; zero-cost when clean.
test-lint-fixer agent charter: constraints, assignment shape, and relationship to lint-fixer (#312) — mirror lint-fixer with inverted scope (test files only); assertion-set invariant (restructure freely, never change what's asserted); deliberately no refusal-handling machinery — persistent offenses are root-cause defects, not routing cases.
Late-gate routing rule: test_path offenses dispatch to test-lint-fixer (#313) — agent choice is a pure path function (test_path → test-lint-fixer, else lint-fixer) applied at every dispatch point incl. the single-loop path; conditional green-assert re-run when test files were edited; no new machinery.
Record the ADR and spec the implementation tickets (#314) — ADR-0107 recorded; implementation split into tickets #317 and #318; #308 closed as superseded.

Not yet specified

(none — the way is clear)

## Destination A locked design (recorded as an ADR) plus fully specified implementation ticket(s), pipeline-ready, for: (1) an early lint gate on test files immediately after test-writer in /os-sdlc:implement, fixed by a new test-lint-fixer agent so the programmer only ever sees lint-clean tests, and (2) test_path-aware routing at the existing late lint gate so test-file residuals dispatch to test-lint-fixer instead of deadlocking on lint-fixer (the #308 deadlock). No implementation happens on this map. ## Notes Engineering effort on plugins/os-sdlc. Skills to consult per ticket: /grilling, /domain-modeling. Decisions must respect the os-adr workflow (/os-adr:find before changing decided approaches, /os-adr:create for the final design). Supersedes the routing proposal in the body of #308 (which suggested re-dispatching test-writer); this map's grilling chose a dedicated test-lint-fixer agent instead. Constraints already settled while charting (2026-08-07): - Destination is planning-only: design + spec'd tickets, not code. - The early-gate fixer is a NEW dedicated agent, test-lint-fixer (not a test-writer re-dispatch, not a relaxed lint-fixer charter). - Scope covers BOTH gates: the early gate is the optimization; the late-gate routing rule is the actual #308 deadlock fix. ## Decisions so far - [Early gate placement: where does test-lint run relative to red-assert? (#311)](https://forgejo.swansoncloud.com/jared/cc-os/issues/311) — red-assert brackets the gate (conditional re-run only after fixer edits); scope = files test-writer touched; safe autocorrect first; zero-cost when clean. - [test-lint-fixer agent charter: constraints, assignment shape, and relationship to lint-fixer (#312)](https://forgejo.swansoncloud.com/jared/cc-os/issues/312) — mirror lint-fixer with inverted scope (test files only); assertion-set invariant (restructure freely, never change what's asserted); deliberately no refusal-handling machinery — persistent offenses are root-cause defects, not routing cases. - [Late-gate routing rule: test_path offenses dispatch to test-lint-fixer (#313)](https://forgejo.swansoncloud.com/jared/cc-os/issues/313) — agent choice is a pure path function (test_path → test-lint-fixer, else lint-fixer) applied at every dispatch point incl. the single-loop path; conditional green-assert re-run when test files were edited; no new machinery. - [Record the ADR and spec the implementation tickets (#314)](https://forgejo.swansoncloud.com/jared/cc-os/issues/314) — ADR-0107 recorded; implementation split into tickets #317 and #318; #308 closed as superseded. ## Not yet specified (none — the way is clear)

jared added the

wayfinder:map

label

2026-08-07 12:54:55 +00:00

jared referenced this issue

2026-08-07 12:55:11 +00:00

Early gate placement: where does test-lint run relative to red-assert? #311

jared referenced this issue

2026-08-07 12:55:15 +00:00

test-lint-fixer agent charter: constraints, assignment shape, and relationship to lint-fixer #312

jared referenced this issue

2026-08-07 12:55:20 +00:00