Source context
A sanctioned fresh lane created by scripts/cursor/provision-lane-worktree.sh at .worktrees/lane-cas-authority-cpr0 cannot establish its own Git custody:
- common
.git/config contains core.worktree = /Users/jasonlee/Developer/console/.worktrees/lane-full-console-g002-s0b;
- from the new lane,
git rev-parse --show-toplevel returns that foreign lane and git rev-parse --is-inside-work-tree returns false;
npm run check:doc-links fails docs/documentation-index.json: index requires a Git worktree;
git status in the new lane reports the foreign lane's unrelated modifications.
No shared config was changed and no foreign modification was cleaned, stashed, reset, or overwritten. The unpublished authority draft was restored byte-for-byte to its HEAD blob.
Blocker class
Shared Git custody / one-writer isolation failure. Any lane can test, stage, or commit the wrong worktree while believing it owns its own path.
Acceptance criteria
- Remove the lane-specific
core.worktree from common config; use correct per-worktree configuration if any explicit value is required.
- For every registered worktree,
git -C <path> rev-parse --show-toplevel equals <path> and --is-inside-work-tree is true.
- Provision a fresh fixture lane through the sanctioned helper and prove
git status --short is isolated.
node --test scripts/check-doc-links.test.mjs and npm run check:doc-links pass from that fresh lane.
- Preserve every existing worktree and all staged/unstaged/untracked user work; no clean/reset/stash/delete.
Verification path
A neutral Rust or existing repository verifier should enumerate git worktree list --porcelain, compare each path with rev-parse --show-toplevel, and fail closed on any mismatch. The protected contexts remain merge authority.
Suggested owner/profile
Repository toolchain/SCM implementer with an independent adversarial reviewer. This blocks the Console C-PR0/C-PR1 cache lanes but is independent of Oyatie PR #1950 and live cluster reachability.
Source context
A sanctioned fresh lane created by
scripts/cursor/provision-lane-worktree.shat.worktrees/lane-cas-authority-cpr0cannot establish its own Git custody:.git/configcontainscore.worktree = /Users/jasonlee/Developer/console/.worktrees/lane-full-console-g002-s0b;git rev-parse --show-toplevelreturns that foreign lane andgit rev-parse --is-inside-work-treereturnsfalse;npm run check:doc-linksfailsdocs/documentation-index.json: index requires a Git worktree;git statusin the new lane reports the foreign lane's unrelated modifications.No shared config was changed and no foreign modification was cleaned, stashed, reset, or overwritten. The unpublished authority draft was restored byte-for-byte to its HEAD blob.
Blocker class
Shared Git custody / one-writer isolation failure. Any lane can test, stage, or commit the wrong worktree while believing it owns its own path.
Acceptance criteria
core.worktreefrom common config; use correct per-worktree configuration if any explicit value is required.git -C <path> rev-parse --show-toplevelequals<path>and--is-inside-work-treeistrue.git status --shortis isolated.node --test scripts/check-doc-links.test.mjsandnpm run check:doc-linkspass from that fresh lane.Verification path
A neutral Rust or existing repository verifier should enumerate
git worktree list --porcelain, compare each path withrev-parse --show-toplevel, and fail closed on any mismatch. The protected contexts remain merge authority.Suggested owner/profile
Repository toolchain/SCM implementer with an independent adversarial reviewer. This blocks the Console C-PR0/C-PR1 cache lanes but is independent of Oyatie PR #1950 and live cluster reachability.