Runner commit subject is the last handoff's summary, which is the contract-auditor's audit note #1115
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#1115
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 behavior-verifier brief carries no
test_changes. The verifier cannot see tests that already exist in the working tree. It marks work as outstanding when that work is done.Observed
Implementation 65 of #1105, target os-backlog.
The programmer went green in dispatch 582.
The behavior-verifier brief in dispatch 583 carried no
test_changes.The verifier marked the AC2 nonzero-exit case and the AC4 ten-name pins as outstanding. Both tests were already in the working tree and green.
The Runner sent the run to test-writer in dispatch 584. Its diff-test returned
unexpected_pass.The run escalated to needs-orchestrator (escalation 38). The orchestrator hand-finished the work.
Reproduce
n/a: the evidence is implementation 65 of #1105 (dispatches 582-584, escalation 38).
Approach
Enrich
test_changes(andred_tests, if the verifier needs them) at the behavior-verifier node, or haveBrief::Factssupply them to that node.Required work:
test_changesto the behavior-verifier node — check: presenttest_changesinplugins/os-sdlc/maps/poodr-ticket-implementation.yamlAcceptance criteria
test_changes.Owner sketch
Origin
Resolution
Done: Folded into #987 as evidence
Evidence: Same mechanism; see occurrence comment on #987
Follow-ups: none