test-lint-fixer agent charter: constraints, assignment shape, and relationship to lint-fixer #312
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#312
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?
Question
What is the test-lint-fixer agent's charter? Assert-preserving constraint wording (it must never change what a test asserts, only style/structure); one assignment file per dispatch (mirroring lint-fixer's fanout shape) vs batch; tool set; what it discloses when a fix would require changing an assertion; and how its charter text relates to lint-fixer's ("never edits tests" stays intact on lint-fixer).
Map: #310
Resolution (2026-08-07)
Charter: mirror lint-fixer, inverted scope. test-lint-fixer fixes exactly the rubocop offenses in its one assignment file, which must be under test_path; it never touches non-test files. Same mechanics as lint-fixer: per-file assignment via the existing worklist/residual machinery (with a test_path split), verbatim offense list, no ticket context, tools Read/Write/Edit/Glob/Grep/Bash, model sonnet, self-verification via rubocop scoped to its file, disclose interpretations, never ask questions, never delete the assignment file. Behavioral verification is not its job — the stepper's red-assert re-run (per #311) owns that.
Assert-preserving rule: assertion-set invariant. The set of assertions and what each asserts must be identical before and after. Allowed: extract setup into helpers, split one test method into several, rename locals, restructure non-assertion code. Forbidden: add, remove, weaken, or merge assertions.
No refusal path. Deliberately no new gate machinery for disclosed-unfixable offenses — no human-pause row, no auto-todo, no fallback re-dispatch. Provenance check: the #261 deadlock's cause was a staffing gap (no worker allowed in test files), fixed by this agent existing; a genuine refusal under the assertion-set-invariant rule has never been observed and the observed offense classes (MethodLength, ParameterLists, ClassLength, Sdlc cops) are all restructure-fixable. The charter keeps the standard "disclose it, do not change it" escape hatch, but a persisting offense is handled by the stepper's ordinary gate-failure behavior and treated as a root-cause defect — a cop misconfigured for test files, or a bad test — fixed via rubocop config or the lint-rule discovery loop, never worked around in the pipeline.