Wire test-lint-fixer routing into fix-lints (ADR-0107) #338
Labels
No labels
P0
P1
P2
P3
bug
create
delete
enhancement
filed-by/agent
filed-by/user
frozen
lint-rule
needs-info
needs-triage
next
plugin/cc-architect
plugin/os
plugin/os-adr
plugin/os-aidd-lint
plugin/os-backlog
plugin/os-context
plugin/os-doc-hygiene
plugin/os-sdlc
plugin/os-vault
project/cc-os
ready-for-agent
ready-for-human
recurring
review
update
waiting
wayfinder:grilling
wayfinder:map
wayfinder:map
wayfinder:research
wayfinder:task
wayfinder:task
wontfix
worklist/deviations
worklist/lint-rule
worklist/new-implement-build
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
jared/cc-os#338
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Context
Running /os-sdlc:fix-lints --target os-backlog, the batch phase deadlocked on plugins/os-backlog/tests/checkout_test.rb: os-sdlc:lint-fixer correctly refuses to edit test files (its charter bans it, by design — the guard against assertion-weakening). ADR-0107 already decided this: a dedicated os-sdlc:test-lint-fixer agent, chartered to restructure test files freely without touching assertions, routed to by path (test_path → test-lint-fixer, else lint-fixer) at every batch/iterative dispatch point. But test-lint-fixer doesn't exist in the current os-sdlc plugin build, and fix-lints' skill files (SKILL.md, references/batch-phase.md, references/iterative-phase.md) never mention test_path routing at all — ADR-0107 describes it wired into os-sdlc:implement's gates, not into the standalone fix-lints skill.
Fix: either build test-lint-fixer per ADR-0107 and wire path-based routing into fix-lints' batch/iterative dispatch steps, or extend fix-lints' docs to explicitly route test-file offenses elsewhere (e.g. back to the user) instead of silently deadlocking.
Frozen in the 2026-08-16 backlog reset — see #419 for the expiry procedure. Do not work unless a live run rediscovers this issue.