weichen/Agent-System-Dev
1
0
Fork 0
Code Issues 1 Pull Requests 8 Actions 3 Packages Projects Releases Wiki Activity

Make the stacked-branch exception explicit in AGENTS.md #82

Merged
weichen merged 4 commits from feature/branch-hierarchy-clause into main 2026-09-30 16:35:35 +00:00
Conversation 0 Commits 4 Files Changed 2
+32
4 Commits
Author SHA1 Message Date
weichen 9bd9ea8f1c Record the sync checkpoint
ci / test (pull_request) Failing after 1m37s
Details
2026-09-30 16:35:09 +00:00
weichen 9e213a89c3 Merge remote-tracking branch 'origin/main' into feature/branch-hierarchy-clause 2026-09-30 16:35:09 +00:00
weichen 5194da2119 Make the stacked-branch exception explicit in AGENTS.md 
Why: worktree feature branches occasionally spawned child branches
(e.g. backend feature/cross-session-reading-1-gcb7f79d) outside the
task-start gate; collaboration.md conditionally allows stacked branches
but the Dev entry never said so, leaving stacking as an automation
blind spot with ad-hoc sha-embedded names.

Evidence: collaboration.md common-baseline section states the stacking
exception verbatim; historical numbered branches are all already merged
into main (origin/main..branch empty); precheck READY at R0=7d45719869.

Impact: AGENTS.md only. Default stays single-level branches from
origin/main with sibling branches for batch subtasks; stacking requires
recording the parent task/PR in the card, child naming without embedded
SHAs, parent-before-child merge order, and a sync back onto latest main
with PR base retargeted before merge (branch protection enforces this).

Refs: task card feature-branch-hierarchy-clause
 2026-09-30 16:35:09 +00:00
weichen ee25cc3a02 Record the task card for feature-branch-hierarchy-clause 2026-09-30 16:34:07 +00:00