opencode run --interactive/-i is a no-op: interactive mode only activates via hidden --mini

Description

opencode run -i / --interactive (documented as "run in direct interactive split-footer mode") has no effect — the flag is parsed but never read by the handler. The interactive mode is only activated by the hidden --mini flag (top-level opencode mini <message>), which hardcodes interactive: false.

Consequence: in opencode run, every permission request is auto-rejected with "permission requested: ...; auto-rejecting" unless --auto is passed, because the run never enters the interactive branch where a permission prompt UI could be shown.

OpenCode version

1.18.16

Steps to reproduce

1. Run opencode run -i "any message that triggers a permission request" (e.g. a slash command that reads/writes a path outside the working directory).
2. Observe: permission requested: external_directory (...); auto-rejecting — identical to plain opencode run without -i.
3. opencode run --interactive behaves the same.

Code references (dev branch)

• Option declared: packages/opencode/src/cli/cmd/run.ts:236-241 (interactive, alias i)
• Handler never reads it: packages/opencode/src/cli/cmd/run.ts:273 — const interactive = args.mini
• Interactive mode requires top-level mini: packages/opencode/src/cli/cmd/run.ts:296-298 — dies with "--mini must be used without the run subcommand"
• runMini hardcodes mini: true, interactive: false: packages/opencode/src/cli/cmd/run.ts:1000-1001
• Auto-reject loop in the non-interactive path: packages/opencode/src/cli/cmd/run.ts:805-815

Expected behavior

opencode run --interactive should enter the direct interactive split-footer mode (with a permission prompt UI), or the flag should be removed/hidden since only --mini actually works.

Operating System

macOS