fix(hooks): print every docs.lanes lane in session-start NEXT
Captures into Muse (canonical) the change that had landed in Git only as c874c15 on fix/session-start-hook-multi-lane. ok status reported muse_sync: pending -- a commit landed in Git without a matching muse commit -- and the edited files were sitting uncommitted on Muse main.
ok next resolves exactly one lane (docs.default_lane when --lane is omitted). The sessionStart/stop hook ran bare ok next, so on a multi-lane repo it presented one lane's NEXT as if it were the whole repo and silently misdirected every session whose work lived in another lane.
The hook now enumerates docs.lanes and emits each lane's fence with a pick your lane note. Repos with no docs.lanes, or one lane, keep the previous single ok next path.
Re-verified in this session (not carried over from the Git commit message): - theBRAIN (lanes: product, app) OLD hook -> 1 CURRENT NEXT fence, app lane never mentioned. NEW hook -> 2 fences, both lanes named, valid JSON, exit 0, empty stderr - overseer-kit (no docs.lanes) NEW hook -> valid JSON, exit 0, empty stderr, single fence unchanged - tests/security/test_lt_security.py + tests/integration/test_lt_integration.py -> 12 passed - full suite -> 16 failed / 1319 passed; no failure touches the hook path (release-workflow, sync, atomic-write, cost-awareness, governance-gates)
Tier 1: feature-branch commit on Muse. No merge to main (Tier 3).
Files Changed
~2
814 in snapshot
0 comments
muse hub commit comment sha256:1927dd90f9afe75932b4a2cb5537d27bc8325e9ad195cc6a7cd05c181c1d576c --body "your comment"
No comments yet. Be the first to start the discussion.