v1.2.0

Highlights

• Unified execution dialog: one dialog configures a launch end to end — the stored plan (or a pasted one), execution and auditor models and variants, the loop name, and per-loop launch settings. Restart is now a mode of the same dialog, so Execute plan opens it for the current session's plan and falls back to restart when there is no open session.
• Per-loop launch settings: Loop settings overrides max iterations, turns the sandbox off for a single loop, and sets CPUs, memory, and the Docker and cache disk sizes. Overrides persist on the loop row and are applied when its sandbox is created, so a restarted loop keeps its resources and a loop launched without a sandbox stays off. Defaults come from the attached server, so they are correct against a remote one.
• Remote TUI over FORGE_RPC: the TUI reads and changes Forge state — the loop list and sidebar, the stored plan, loop restarts, host-sandbox desired/applied state, the worktree list, and per-session auto-approve — through the server's RPC surface. It holds no Forge database of its own, so it works attached to a remote OpenCode server, and it updates from server-pushed events instead of polling. The TUI and server plugin must run the same Forge version; a mismatch warns.
• Per-session auto-approve: Toggle auto-approve approves a session's requests through OpenCode's permission.evaluate hook, scoped to that session and its Task subagents, with configurable autoApprove.deny rules and a 15-day idle expiry. Explicit OpenCode ask rules and configured denies still deny; loop sessions, whose ruleset already allows everything not denied, are refused.
• Loop sidebar: up to three loops per project, running first, each as a status-coloured row that expands to the current phase, section, and elapsed time.

What's Changed

• feat(tui): per-loop launch settings and unified execution dialog (#107)
• feat(tui): per-session auto-approve and remote TUI over FORGE_RPC (#106)
• docs: update README for the unified TUI and new screenshots