suite-check receives ticket_brief it never reads; drop it from all three maps #688
Labels
No labels
P0
P1
P2
P3
bug
category/code-change
category/cross-repo
category/eval-run
category/investigation
category/no-test-target
category/owner-ruling
category/prose-artifact
category/recurring-chore
category/structure
category/umbrella
crc-refactor
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
rule-proposal
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#688
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?
#688 suite-check receives ticket_brief it never reads; drop it from all three maps (open)
@jared created 2026-09-24 13:11
Problem
coding.yaml:38, poodr-implementation.yaml:146, poodr-ticket-implementation.yaml:157 give suite-check enrich: [ticket_brief]. The charter procedure (agents/suite-check.md:10-26) runs os-sdlc-runner gate <dispatch_id> once and settles a handoff with empty items and disclosures. No step reads ticket content. The charter Input line (suite-check.md:12) says the prompt supplies the ticket brief, but nothing acts on it. Measured ticket_brief: median 5,500 chars, max 16,211.
Reproduce
n/a: design audit finding, not a runtime defect.
Approach
Change the three enrich lists to [] (or remove the key if the schema allows). Edit suite-check.md:12 to name only the dispatch ID.
Required work:
Acceptance criteria
Owner sketch
Maps: the three files above. Charter: plugins/os-sdlc/agents/suite-check.md line 12. Tests: the map tests under plugins/os-sdlc/tests/ that assert suite-check enrich lists. The loader already accepts an empty enrich list (plugins/os-sdlc/lib/os_sdlc/pipeline/map/node_spec.rb:39).
Evidence
Audit row from #676: suite-check | ticket_brief | DROP | suite-check.md:10-26 procedure never references the ticket.
Origin
• Trigger: #676 enrich-fact audit, run in session 9434289b
• Improvised this session: none
• Chain: oversized or duplicated brief facts <- enrich lists chosen per node without a per-role byte audit <- DESIGN (map enrich model)
• Root candidate: this ticket
• Where: the map/charter/composer paths named in the draft
• Parent: #676
• Session: 9434289b-c48f-4a8a-8add-0d82068e2c3f
• Transcript: /home/jared/.claude/projects/-home-jared-dev-cc-os/9434289b-c48f-4a8a-8add-0d82068e2c3f.jsonl
Skeptic verdict: CREATE (os-backlog:ticket-skeptic, session 9434289b, citations verified).
Work started on branch ticket-688 via /os-sdlc:implement, session 9434289b.
Resolution
Done: suite-check enrich list is [] in coding.yaml, poodr-implementation.yaml, and poodr-ticket-implementation.yaml. suite-check.md Input line names only the dispatch ID. New test file asserts both.
Evidence: os-sdlc implementation 25, 8 dispatches all pass, 0 retries, 473s; suite gate green (36,694 ms); branch ticket-688, 5 files.
Follow-ups: none