os-sdlc: dedup .cc-os/config tracker-line regex between IssueSource and TeaTracker #411
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#411
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
Both regexes encode the .cc-os/config tracker-line grammar: IssueSource::CONFIG_TRACKER_LINE (plugins/os-sdlc/lib/os_sdlc/issue_source.rb:13, capturing, extracts the value) and an inline non-capturing copy in TeaTracker#config_tracker_line? (plugins/os-sdlc/lib/os_sdlc/runner/tea_tracker.rb:130, boolean match only). TeaTracker already depends on IssueSource::TrackerResolver (tea_tracker.rb:135), which owns CONFIG_TRACKER_LINE and the .cc-os/config read. Refactor, not a bug — no behavior change expected. Evidence brief: .sdlc/tickets/411/evidence-brief.md.
VERDICT: CREATE — confirmed duplicate tracker-line regex literals in IssueSource::CONFIG_TRACKER_LINE and TeaTracker#config_tracker_line?; real drift risk if a tracker type is added to one and not the other.
Tasks
Acceptance criteria
Resolution
Done: Done.
Evidence: ADR-0122 backfill audit: DROP on speculative-hardening - duplication is real but has no incident provenance, and it is eliminated wholesale when #418 replaces runner/tea_tracker.rb with os-backlog's Tracker/ConfigLocator.
Follow-ups: Covered by #418; no separate work item.