plan_approval round trip for pane members

What it does

When a pane member runs under planModeRequired, its plan_exit sends a frame to the lead, the lead shows an approval dialog, and the answer is routed back to the member. Today a pane member's plan_exit stays local.

Source

ganja-code-2b6 (the plan_approval round trip for pane members).

The bead is closed when this issue is published, with its external reference pointing here (#38).

File and line references in this issue are to main as of 75a7a92.

Against the three criteria

• Direction (README): The README names the team model as a pillar of the product (README.md:6-8). The idea improves today's local team model; it is not the cloud fleet itself.
• Today's terminal users: A lead who requires plan approval from a pane member gets the approval step it asked for; today the mapping to the plan agent works, but no frame reaches the lead and the lead shows no dialog.
• Evidence: The limitation is written in the docs of the runner (crates/ganja-core/src/teammate/runner.rs:190-193). No user report is recorded; the gap is known from the code.

Depends on

No other idea. The work is a frame, a lead-side dialog and answer routing.

Verdict

• Verdict: do
• Size: M — one plan and one decision number.
• Exception to the probe rule: no.
• Date: 2026-09-19
• Verdict ticket: #40

Theme: #53

Start with crates/ganja-core/src/teammate/runner.rs:190-193 and the team model described in README.md:6-8. Trace how a pane member's plan_exit currently stays local, then follow the existing lead approval flow. Done means the frame reaches the lead, an approval dialog is shown, and the answer is routed back to the member.