Repository navigation
v0.7.0: per-session worktrees
What is new since 0.6.0
- Each OpenCode session starts its Muse session on a server-managed worktree instead of sharing the checkout, so concurrent sessions stop serializing at the workspace lock (tracks #34, which stays open for the remaining lease-protocol and orphans work).
- The human merges through normal source control; the bridge never auto-merges, and purge-on-close removes only provably-empty worktrees.
- Graceful fallback: untrusted workspaces and CLIs without the experimental surface keep the single-writer lock with a conversational notice.
- First-turn labels tell the agent which worktree it is on; PDF staging follows the session onto its worktree.
Strict build, 310/310 tests, and package-contents checks pass. Install snippet pinned to 0.7.0 in the same commit (lockstep rule).