Scope bin/evidence sender matches by receiver class #997
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#997
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?
Problem
The takedown
bin/evidencematchesCLI#runby bare name.final-evidence.txtthen lists unrelated worktree and os-sdlc senders, which hides the real callers.Design
/home/jared/dev/cc-os/.claude/worktrees/prism-architect/docs/takedown/997-20261012-102656/final-design.json
Approach
Fingerprint stops claiming unverified same-name calls as senders of an instance method: only LSP-confirmed references are
sent by, and unconfirmed bare-name matches become one capped UNCONFIRMED candidate line.Required work:
plugins/os-sdlc/lib/os_sdlc/command/fingerprint.rbplugins/os-sdlc/lib/os_sdlc/presenter/fingerprint/sender_row.rbplugins/os-sdlc/lib/os_sdlc/model/report/row_entries.rbplugins/os-sdlc/tests/command/fingerprint_test.rbplugins/os-sdlc/tests/evidence_bin_test.rbplugins/os-sdlc/tests/command/fingerprint_candidates_test.rbAcceptance criteria
EVIDENCE: C#m sent by [lsp] p:l.for the confirmed ones. One cappedUNCONFIRMED:line for the rest, if any remain.sent by. One cappedUNCONFIRMED: C#m — N same-name call sites, receiver type unverified, at …line.UNKNOWNor[lsp]lines.Owner.namematch,sent by.NEVER_SWEPTnames: Unchanged.Owner sketch
OsSdlc::FingerprintProbe::Lsp(unchanged)$RECV.name)Probe.sender(unchanged)UNCONFIRMED:line, capped atSITE_LIMITFingerprint::SenderRowReport::RowEntriesplugins/os-sdlc/tests/command/fingerprint_candidates_test.rbTicket-skeptic verdict (real run; the VERDICT line in the body was written by the filing agent, not the skeptic): CREATE. EvidenceCheck passes only file paths to bin/evidence collect, so the bare-name match must be fixed in bin/evidence.
Session: 3f094e92-202f-41fc-8d9c-b591750d9bc1
Transcript: /home/jared/.claude/projects/-home-jared-dev-cc-os--claude-worktrees-prism-architect/3f094e92-202f-41fc-8d9c-b591750d9bc1.jsonl
Implementation started on branch prism-architect (takedown-implement map, target os-sdlc), design docs/takedown/997-20261012-102656/final-design.json.
Resolution
Done: bin/evidence reports a method's sender as 'EVIDENCE: ... sent by' only when the LSP confirms the reference; unconfirmed bare-name matches become one capped 'UNCONFIRMED:' candidate line. change-auditor, responsibility-auditor, blast-radius and code-probe now treat UNCONFIRMED as a candidate and forbid 'no consumer' while one exists.
Evidence: Implementation 41 complete after two orchestrator reroutes (escalation 18: map defect, existing tests in code_files; escalation 19: report_test.rb pinned the old output and was not in the design). Commits
5e03ed64(production),ea934691(test hand-fixes), plus the agent/skill doc commit. os-sdlc suite 1543 runs, 0 failures. Design docs/takedown/997-20261012-102656.Follow-ups: #1003 (route changed existing tests away from the programmer at place-code). Known limit from the design: a down LSP shows real callers as UNCONFIRMED; no follow-up filed because the line is visible and the readers now handle it.
jared referenced this issue2026-10-14 15:18:06 +00:00