microsoft / microsoft/amplifier-bundle-dot-runner
capsule.dot v2 change 4 (held): fan `void` out beside `mutate`/`mutate_b` needs filesystem isolation for parallel makers
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 2
- Avg merge
- 4h 6m
- Merged PRs (30d)
- 88
Description
From the pipeline review (docs/designs/REVIEW-pipelines-2026-09.md §3.3 / §4 change 4, merged via #71). The only structural clock saving found (~90 → ~72 min/round) is running void in parallel with the mutate pair. Blocked on Q1: the three makers write into the same working tree; parallel execution needs per-branch isolation (worktree per branch, or a copy-on-write scratch dir, or a merge step) before the fan-out is safe. This issue tracks the isolation design; do not apply change 4 until it is answered with a design + a test that two concurrent makers cannot clobber each other.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with docs/designs/REVIEW-pipelines-2026-09.md, especially §§3.3 and 4 change 4, and review the Q1 constraint described here. Compare the proposed worktree, copy-on-write scratch directory, and merge-step approaches. Done means a design is selected and a test demonstrates that two concurrent makers cannot clobber each other.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100