[quickbeard]

Summary

The first-run Configure CoDev Code gate can no longer be escaped into an unconfigured chat. Previously Option 2 (Custom provider) and Option 3 (Connect provider) each dropped the user into chat if they hit Esc — the code comments literally said "escaping here lands in an unconfigured chat." This closes that.

Approach

Instead of freezing Esc per-step (which for Option 3 would mean invasive edits across upstream's multi-step dialog-provider.tsx, and would also kill Esc inside OAuth and remove in-flow back-navigation), the gate now re-asserts itself. The one-shot open-on-startup effect in app.tsx becomes a stateless invariant:

createEffect(() => {
  if (sync.status !== "complete") return
  if (connected()) return
  if (dialog.stack.length > 0) return
  dialog.replace(() => <DialogConfigure />)
})

While unconfigured with no dialog open, the gate (re)opens. Consequences, all desired (confirmed with the requester):

• Esc at any depth of Option 2 or Option 3 → stack empties → gate reopens ("back to the gate"). Works for upstream's Connect-provider dialog with zero upstream edits.
• Credential-only save (Option 2, empty base URL) → provider isn't usable, connected() stays false → gate reopens ("block it").
• Errors / cancels → gate reopens. Only a real provider or double-Ctrl+C (quit) leaves the gate.
• A configured user is never trapped — connected() is true, so /connect, /models, and /configure stay dismissable to chat.

Scope note: an unconfigured user who opens /connect or /models manually and escapes also bounces to the gate — a natural consequence of "force configuration," and the same mechanism that makes Option 3 work without touching upstream.

Changes

• packages/tui/src/app.tsx: transition-only gate effect → the invariant; dropped the now-unused on import.
• packages/tui/src/component/dialog-configure.tsx: refreshed the two stale Option 2/3 comments.
• DIVERGENCES.md: updated the existing app.tsx row.

Test plan

• packages/tui: typecheck green; 220 pass / 1 fail — the pre-existing app-lifecycle epilogue flake, identical on clean main.
• End-to-end in tmux (mock /v1/models, isolated XDG dirs), all confirmed:
  • Option 2, Esc at the API-key step → back to gate.
  • Option 2, empty base URL → credential saved (toast) → back to gate.
  • Option 3 → Anthropic → Esc at the depth-2 API-key step → back to gate.
  • Full success (mockgw + models) → lands in chat, gate does not reopen.
  • Configured user: /connect then Esc → returns to chat (not trapped).

🤖 Generated with Claude Code