Lead notice for a successful shim turn that said nothing

What it does

When a codex teammate ends a turn successfully without sending any message, the lead is told so instead of hearing nothing. The agy and grok drivers already report this case.

Source

ganja-code-98v (a successful shim turn that said nothing is silent to the lead). The bead's second half, a test-fixture deduplication, is a chore and not part of this idea.

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 teammates driven through other vendors' CLIs, codex among them (README.md:6-8).
• Today's terminal users: A lead waiting on a codex teammate today sees only a note in the member's ring when the turn said nothing.
• Evidence: The gap is codex-only and known from the code: the agy and grok drivers report a turn that succeeded and said nothing (crates/ganja-teammate-local/src/agy.rs:424-432, crates/ganja-teammate-local/src/grok.rs:725-736), while the codex driver always returns refused: None (crates/ganja-teammate-local/src/codex.rs:496) and the shim mails zero messages and returns Ok (crates/ganja-teammate-local/src/shim.rs:1809-1821).

Depends on

Nothing.

Verdict

• Verdict: do
• Size: S — one commit, no plan.
• Exception to the probe rule: no.
• Date: 2026-09-19
• Verdict ticket: #40
• It was first parked on a free slot in #40 and rose to do when the cap rose from three to five do per theme; see the amendment on #40: https://github.com/zchee/ganja-code/issues/40#issuecomment-5739314165

Theme: #53

Start in crates/ganja-teammate-local/src/codex.rs:496 and shim.rs:1809-1821, comparing the successful empty-turn handling in agy.rs:424-432 and grok.rs:725-736. Trace how the shim returns successfully without messages, then verify that a successful codex turn with no message produces the expected lead notice without taking on the separate fixture-deduplication chore.