Build bin/evidence: deterministic code-probe fingerprint CLI (ADR-0142) #483
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#483
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
User-approved 2026-08-22, designed in-session from the #482 defect. ADR-0142 records the decision: code-probe steps 2-3 (verify definitions, trace call sites) move from prose-prescribed ast-grep queries into a plugin-owned CLI so patterns are frozen in tested code and one tool call replaces N model-composed queries.
Tasks
Acceptance criteria
Origin
Work started in-session 2026-08-22: TDD build dispatched to a worker agent per ADR-0142 design (Resolver → Probes → Fingerprint → Report → Thor CLI → skill/agent doc edits). No branch; working tree of main.
Resolution
Done: bin/evidence built per ADR-0142: Thor CLI + OsSdlc::Evidence::{Resolver,Probe,Fingerprint,Report}; mixed-token varargs with (class,path) dedupe and phantom-as-finding; bare $RECV.NAME sender probe primary; dynamic-send escalation gated to the zero-hit trigger with NEVER_SWEPT guard and grep -P constrained to :name/name:/send(:name) shapes; UNKNOWN lines capped at 3 sites; --explain re-renders memoized probe provenance; code-probe SKILL.md/cheatsheet/agent Bash allowance rewired; plugin cache refreshed; History row added
Evidence: Commit
f1fb658on main (19 files, +1006/-43). All four acceptance criteria verified unfiltered by the orchestrator: WriteGuard brief is 10 lines incl. EVIDENCE deny? sender pre_tool_use.rb:24 and 4 UNKNOWNs correctly flagging VIOLATION_CHECKS hash-shorthand dynamic dispatch at write_guard.rb:59-62; write_guard.rb+WriteGuard dedupe to 1 unit; NoSuchClass exits 0 with phantom line; --explain shows exact ast-grep commands from the same run. Suite 1052 runs/2694 assertions/0 failures; rubocop clean on all touched files. One red-gate round mid-build: initial escalation noise-bombed 78KB/class; fixed with regression test capping the real-repo brief at ≤30 lines.Follow-ups: Three surfaced by the builder, all dropped as speculative (no observed failure): surface captured $RECV collaborators in the brief; normalize trailing-slash root in phantom lines; empty-.rb-file resolver test. One disclosed limitation, deliberate per design: implicit-self-only senders (deny?→write?) emit no line — classification stays agent judgment; revisit only if it bites on a real ticket.