feat(templates): drop the worktree from the delivery rule and §9 - #26
Merged
Conversation
Version 15 took the worktree out of the procedure and left `delivery.md` pointing at one anyway — a line preloaded into every request describing a step nothing in the flow performs. How a user arranges several sessions against one repo is theirs to set up, and saying that is enough; the rule keeps only what the worktree was ever really carrying, which is to leave the checkout back on `main` and clean. design/orchestration.md §9 loses the same offer, and "separate checkouts" becomes "separate sessions" where the cost of parallel runs is named. The record that it was rejected stays in §5, §8, and changelog entry 15. Template set 17 -> 18. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KA9xRzo3xpYLMZjrtRbcge
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.
What changed
The worktree is gone from the development flow — the mention as well as the use.
internal/assets/templates/rules/delivery.md— the sentence offering the user agit worktreebecomes "how a user runs several sessions against one repo at once is theirs to set up". Same discipline (branch in the checkout you are in, leave it back onmainand clean), no mechanics named.design/orchestration.md§9 — the**A git worktree is not part of this...**paragraph is rewritten as**Nothing here needs a second directory, and the procedure used to make one.**, keeping the cost that motivated the removal. In "What running several sessions still costs",Separate checkouts→Separate sessions, andnamespaces those per checkout→per session.internal/assets/assets.go— template set17→18, required by the convention whenever a workspace template changes, with the changelog entry for it.Why
Version 15 took the worktree out of the procedure and left the rule pointing at one anyway. That is the same cost in a smaller font:
<harness>/rules/*.mdis preloaded into every request on a harness that reads it, so a line describing a step nothing in the flow performs is paid continuously.What deliberately stays
The record that the worktree was rejected —
design/orchestration.md§5 (the removedworktree:frontmatter key), §8 (worktree-per-task in the rejected design), and changelog entry 15 inassets.go. Deleting the rationale is how the idea gets re-proposed.design/research.md§3.2 anddesign/plan-format-v2.mdalso keep theirs: community research and a risk note, not scc's flow.Verified
gofmt -l,go vet ./..., and the full suite pass locally (make checkequivalent —makeis not on this machine).🤖 Generated with Claude Code
https://claude.ai/code/session_01KA9xRzo3xpYLMZjrtRbcge