Twinned from https://github.com/cfsh/ninefold/issues/534 by tools/beads/import_github.py's reconcile pass.
rebuild_f5.py (#530) gives each clone its own f5 worktree at ../<clone>-f5. With ninefold-a/b/c that is ~460 MB apiece, ~1.4 GB total, created lazily on each session's next rebuild. The PR asks this in its body; filing it here so it is answerable from the issue list.
A — one worktree per clone (as implemented, recommended default). ~1.4 GB across three clones. No coordination: two sessions can rebuild simultaneously and never see each other.
B — one shared worktree directory for all clones. ~460 MB total. Needs a lock — two sessions rebuilding at once would fight over one tree, and the loser either blocks or corrupts the other's integration. git worktree also registers a worktree to exactly one repository, so "shared" means one clone owns it and the others drive it, which is a new coupling between sessions.
Disk here is cheap and contention is not, which is why A is the default.
Default ships if unanswered — nothing is blocked on this.
None.
No comments.