Give the behavior-verifier brief the whole implementation diff across targets #1342

Open
opened 2026-10-25 20:38:03 +00:00 by jared · 0 comments
Owner

Problem

When one ticket changes code in two plugins, the behavior-verifier brief carries code_changes for one target only.
The verifier then misses the fix in the other plugin and marks that acceptance criterion outstanding.

Observed

Ticket #1321 changed an os-sdlc cop and a fix in plugins/os-backlog/lib/backlog/cli/project_commands.rb.
The brief for the verifier (dispatch 1403) carried code_changes for the os-sdlc target only.
The verifier marked the os-backlog acceptance criterion outstanding, although the programmer (dispatch 1402) had already made the fix.
The next test-writer round then passed unexpectedly (unexpected_pass:test-writer/diff-test).
The run escalated (implementation 162, escalation 75) and was hand-finished.
Possibly related: #1339 (pipeline routing gaps). This ticket is a brief-content defect, not a routing gap.

Reproduce

n/a: needs a pipeline run on a ticket that changes two plugins; evidence is implementation 162.

Approach

Expected: the verifier brief carries the whole implementation diff, across all targets.

Required work: none beyond the acceptance criteria.

Acceptance criteria

  1. Given a ticket whose implementation changes code in two plugins, when the behavior-verifier brief is built, then it carries code_changes for both targets.

Origin

  • Trigger: /os-sdlc:implement run for #1321 (implementation 162, escalation 75)
  • Improvised this session: hand-finished the run
  • Chain: verifier marks criterion outstanding <- brief lacks os-backlog code_changes <- brief built from one target only (DESIGN: class not yet traced)
  • Root candidate: none found; searched code_changes, test_changes, behavior-verifier, Brief::Facts, target, code_path, cross-target, staged
  • Where: behavior-verifier brief builder in plugins/os-sdlc (exact class not yet traced)
  • Session: eb98cdcd-6783-46a0-b7df-cf18a8fe2a56
  • Transcript: /home/jared/.claude/projects/-home-jared-dev-cc-os/eb98cdcd-6783-46a0-b7df-cf18a8fe2a56.jsonl

VERDICT: CREATE

## Problem When one ticket changes code in two plugins, the behavior-verifier brief carries `code_changes` for one target only. The verifier then misses the fix in the other plugin and marks that acceptance criterion outstanding. ## Observed Ticket #1321 changed an os-sdlc cop and a fix in `plugins/os-backlog/lib/backlog/cli/project_commands.rb`. The brief for the verifier (dispatch 1403) carried `code_changes` for the os-sdlc target only. The verifier marked the os-backlog acceptance criterion outstanding, although the programmer (dispatch 1402) had already made the fix. The next test-writer round then passed unexpectedly (`unexpected_pass:test-writer/diff-test`). The run escalated (implementation 162, escalation 75) and was hand-finished. Possibly related: #1339 (pipeline routing gaps). This ticket is a brief-content defect, not a routing gap. ## Reproduce n/a: needs a pipeline run on a ticket that changes two plugins; evidence is implementation 162. ## Approach Expected: the verifier brief carries the whole implementation diff, across all targets. Required work: none beyond the acceptance criteria. ## Acceptance criteria 1. Given a ticket whose implementation changes code in two plugins, when the behavior-verifier brief is built, then it carries `code_changes` for both targets. ## Origin - Trigger: /os-sdlc:implement run for #1321 (implementation 162, escalation 75) - Improvised this session: hand-finished the run - Chain: verifier marks criterion outstanding <- brief lacks os-backlog code_changes <- brief built from one target only (DESIGN: class not yet traced) - Root candidate: none found; searched code_changes, test_changes, behavior-verifier, Brief::Facts, target, code_path, cross-target, staged - Where: behavior-verifier brief builder in plugins/os-sdlc (exact class not yet traced) - Session: eb98cdcd-6783-46a0-b7df-cf18a8fe2a56 - Transcript: /home/jared/.claude/projects/-home-jared-dev-cc-os/eb98cdcd-6783-46a0-b7df-cf18a8fe2a56.jsonl VERDICT: CREATE
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
jared/cc-os#1342
No description provided.