Ultraplan remote session offers 'implement here' but cannot push code

Description

When running /ultraplan, the remote cloud session generates a plan and then offers an "implement here" option. However, the remote environment is an ephemeral sandbox with no git credentials, no MCP server access, and no ability to push code. Approving the plan for implementation in the remote session results in code that is written but trapped — it cannot be committed or pushed, and the work is lost when the session ends.

Steps to reproduce

1. In a local Claude Code terminal, run /ultraplan with a planning prompt
2. The remote session generates an engineering plan
3. The remote session presents an option to implement the plan in the current session
4. Approve the plan for implementation
5. Implementation runs, but the session cannot git push — the code is stranded

Expected behavior

The remote session should either:

• Not offer "implement here" if it lacks git credentials / push access
• Check for push capability before presenting the implementation option and warn the user
• Default to teleporting the plan to the local terminal for implementation (via __ULTRAPLAN_TELEPORT_LOCAL__)

Actual behavior

The remote session offers implementation as an option, the user approves (reasonably — it was offered), implementation happens in the sandbox, and the result is unreachable. The user has to redo the work locally.

Environment

• Claude Code CLI (invoked via local terminal on macOS)
• Remote session: ephemeral cloud environment (no git auth, no MCP)

Additional context

The remote session itself acknowledged the issue after the fact:

"I should have checked for push access before implementing and told you to teleport the plan locally instead."

The workaround is to reject the plan with __ULTRAPLAN_TELEPORT_LOCAL__ instead of approving, but this is non-obvious and the UI shouldn't present a broken path as a valid option.