Align green_assert_failure_sidecar.rb test-path matching to the segment-anchored convention #469
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#469
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
While extending WriteGuard for #466, plain String#include? test-path matching was shown to false-match paths like Dir.mktmpdir("os-sdlc-test") temp prefixes. WriteGuard now uses a segment-anchored regex ((^|/)<test_path>(/|$)) in plugins/os-sdlc/lib/os_sdlc/write_guard.rb; plugins/os-sdlc/lib/os_sdlc/green_assert_failure_sidecar.rb still uses plain include?, so the same misclassification is live there.
Skeptic verdict: CREATE — real observed bug-class confirmed live in a sibling file, this ticket is the root.
Origin
Work starting via os-sdlc pipeline on branch worktree-worktree-469.
Resolution
Done: Aligned GreenAssertFailureSidecar#under_test_path? to WriteGuard's segment-anchored test-path regex, replacing String#include? substring matching; also removed an unreachable failing_path nil guard flagged in review.
Evidence: os-sdlc map drive reached merge-ready (implementation 2, session 918582d6): programmer + reviewer correction loop, reviewer round-2 verdict pass; full suite green (1007 runs, 2556 assertions, 0 failures), rubocop clean; change on branch worktree-worktree-469, file plugins/os-sdlc/lib/os_sdlc/green_assert_failure_sidecar.rb:50 matches write_guard.rb:125 convention.
Follow-ups: #475 captured (skeptic verdict CREATE): add regression test pinning the segment-anchored boundary; no other follow-ups.