FormRunner seam + shared Lipgloss theme

[maxBRT]

Parent

#66 Spec: Operator CLI UX overhaul (Charm / huh)

What to build

Introduce a FormRunner seam behind Init and Interactive Queue confirmation, and shared Lipgloss theme tokens (amber / green / red, ship brand prefix) reused by later chrome. Production FormRunner still uses today’s typed-line prompts so operator behavior is unchanged; tests can stub FormRunner answers without driving a live TUI. Queue port and orchestrator stay unaware of any TUI library.

Acceptance criteria

• Init and Interactive call FormRunner for operator prompts instead of owning prompt I/O directly
• Non-TTY Init still writes agent: cursor with no prompt; invalid/cancel still fails before writing a Shipfile
• Non-TTY Queue confirmation still returns ErrNonInteractive; cancel / empty / confirm semantics unchanged
• Tests stub FormRunner for Agent pick and Ticket selection outcomes without a live terminal UI
• Shared theme tokens exist for amber wait, green success, red failure, and ship framing
• No Charm huh interactive forms yet; no new Config flags or Shipfile keys

Blocked by

• None — can start immediately.