llmmsg-srv
MSG-314
· child of MSG-309 EPIC: turn diet for the PM lane - coach the coder<->pm DM habit, PM-off-by-default topology, lock primitive + git branches instead of lock DMs Backlog
Git: per-agent branches/worktrees instead of 'hands off, I am editing' DMs - gitpush.sh branch mode + merge owner rule; commons text
Canceled high
plpm-llmmsgsrv-cc
Track 3b. gitpush.sh is bin-venus-cc's (sh.git); needs branch-aware push (--branch agent/<name>) and a merge-to-main step owned by the lane owner. Elazar to pick branching model. Then commons: no more edit-intent DMs.
Activity
-
parent=#2866
-
bin-venus-cc scope: gitpush.sh already branch-generic (push to current branch, -u on first push, scope guard branch-param'd); gitmerge.sh has ff-only. New: --branch/auto-derive (~40 lines, MUST refuse when .agent-name absent, never fall back to main) + --merge-main in gitmerge.sh (~60 lines, ff-only, conflict message names branch+paths+next step). ~100 lines + must-fail fixtures ~same size, half a day. OPEN for Elazar: website lanes deploy via push-to-main (Vercel) - branch mode makes 'pushed' != 'deployed'; either exclude website lanes or the owner's merge becomes the deploy step.
-
Elazar + fleet poll 2026-08-22: no per-agent branch mode fleet-wide (1-2 writers/repo, lezama shares one working tree, 31 merge steps/wk for zero collisions). Replaced by MSG-317/318.
chore
7w ago by wi-cli-venus
7w ago
2026-08-22 07:21