opencode v2: /move loses parent workspace MCP and skill configuration

Summary

OpenCode V2 loses parent-defined workspace configuration when /move relocates a session into an OpenCode-managed worktree.

The original session detects MCPs and skills configured in the parent repository directory, but the relocated session does not because its generated worktree is outside that configuration hierarchy.

Environment

• opencode version: 0.0.0-beta-18155
• OS: Linux 7.0.0-30-generic (linux x64)
• Terminal: Ghostty (TERM=xterm-ghostty, COLORTERM=truecolor)
• Shell: /usr/bin/zsh
• Install/channel: beta
• Active plugins: configured; omitted for privacy.

Reproduction

1. Keep shared OpenCode MCP and skill configuration in a parent repository directory used by multiple child projects.
2. Start OpenCode V2 in one of the child projects.
3. Confirm that the session detects the MCPs and skills inherited from the parent configuration.
4. Run /move.
5. OpenCode relocates the session to a generated worktree under a path similar to:

   ~/.local/share/opencode/worktree/<id>/<generated-name>
   

6. Inspect the MCPs and skills available in the relocated session.

Expected Behavior

/move should preserve the effective MCP and skill configuration of the source workspace.

If worktree isolation intentionally changes configuration discovery, OpenCode V2 should warn before moving or clearly document that parent-defined configuration will not be available in the relocated session.

Actual Behavior

The relocated session no longer detects MCPs and skills configured in the source project's parent repository directory.

The original session, which remains in the source workspace, continues to detect the same MCPs and skills correctly.

Additional Context

The generated worktree is outside the source repository's parent directory hierarchy, so normal configuration discovery no longer reaches the shared configuration. This changes the available session capabilities unexpectedly after /move.