Conversation
22 requirements, 78 acceptance criteria for plugin-style VCS backend supporting git (with git-town) and Jujutsu. Includes auto-detection, config, pipeline integration, and 7-phase implementation plan. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Resolved OQ-1 through OQ-4 per stakeholder interview: - Doctor validates jj binary + colocated mode - AI conflict resolver adapted for jj syntax - PR-based merge flow (jj git push + gh) - Finalize + reviewer prompts are VCS-aware Added REQ-023 (doctor jj validation, 3 ACs), config schema example, v0.4-beta release gate for jj conflicts. 23 reqs, 81 ACs total. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
72 tasks (36 implementation + 36 test), 5 sprints, 180 hours. 100% traceability to PRD-2026-004's 23 requirements and 81 ACs. Covers: VcsBackend interface, GitBackend extraction, JujutsuBackend, auto-detection, config, prompt templating, conflict resolver adaptation, doctor validation, and sprint-by-sprint release plan. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
… VCS Types (bd-deoi) (#100)
…Backend -- Repository Introspection (bd-zny3)
… Abstraction -- Git and Jujutsu Support (bd-28p7)
When running foreman on a feature branch, agent work was correctly branched from the feature branch but auto-merge and finalize targeted the default branch (dev) via detectDefaultBranch(). This caused merges to land on dev instead of the feature branch. Changes: - Add target branch confirmation prompt in `foreman run` when current branch differs from default — user confirms before dispatch - Thread targetBranch through dispatch → WorkerConfig → agent-worker → autoMerge so merges target the correct branch - Pass targetBranch as baseBranch to finalize prompt so agents rebase onto the correct branch before pushing - Agent worker detects default branch as fallback when targetBranch not provided (fixes pre-existing bug where finalize hardcoded "main") - Force full re-export in bead writer queue (--force flag) to prevent br/bv JSONL desync from stale dirty flags Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- br update changed --labels to --set-labels (br create still uses --labels). Fix beads-rust client to use the correct flag. - Increase timeout for forced br sync after bead writer drain from 30s to 60s — full re-export of 500+ issues was hitting ETIMEDOUT. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Long branch names like feature/trd-2026-004-vcs-backend-abstraction produce labels over 50 characters, which br rejects. Rather than truncating (which would cause refinery to target a non-existent branch), skip the label entirely. The explicit targetBranch threading added in the previous commit handles merge targeting for these cases. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…mplating (v0.4-beta) (bd-kjrl)
…utsuBackend -- Finalize Commands (bd-8lmr)
…csBackendFactory (bd-tket)
…itBackend Branch Operations (bd-60tn)
…Backend -- Branch Operations (bd-yt70)
…itBackend Workspace Management (bd-0ggy)
…Backend -- Commit and Sync Operations (bd-m19i)
…itBackend Commit and Sync Operations (bd-njzr)
…Backend -- Merge Operations (bd-hjhb)
…Backend -- Diff, Conflict, and Status (bd-mj19)
Switch from Date.now()+10 iterations to performance.now()+100 iterations with 5-call warmup. Raise threshold to 200ms total (batch) to match the actual AC-022 criterion (< 1% pipeline overhead, not < 50ms per-call). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Replace absolute 200ms ceiling with 3× relative check (abstractionTime < directTime * 3). The absolute ceiling was too sensitive to machine load when multiple agents run concurrently. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Adds rebaseAfterPhase: developer to the default workflow, activating the TRD-2026-005 RebaseHook machinery. Worktrees now rebase onto origin/dev before QA runs, so agents automatically pick up any fixes that land on dev between dispatch and QA — making refinery test failures self-healing. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
sentinel-fail events have branch/commitHash fields but not seedId/phase, so the detail was blank. Now renders as: sentinel-fail — branch:main a60f767 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
rebaseAfterPhase: developerenabled — worktrees now rebase onto origin/dev before QA runs, making pipelines self-healing against dev divergenceforeman statusdefaults to collapsed single-line agent view in TTY;-e/--expandfor full detailTest plan
foreman statusshows collapsed view in terminalforeman status -eshows full expanded cards🤖 Generated with Claude Code