Launch the configured coding agent after openbot update

[danielblignaut]

Outcome

After every openbot update result, automatically launch the user's configured default coding agent with the generated fork-review prompt and update-note path.

ADR-0013 in #8 defines the update-note and semantic-review contract. Launching a process is a handoff, never evidence that review succeeded.

Scope

• Add a renderer-agnostic coding-agent launcher contract and explicit default-agent configuration.
• Support verified installed integrations first; do not guess executable names or interpolate a shell command.
• Launch after merge success, merge conflict/failure, and the no-updates result.
• Pass the complete review prompt and configuration/docs/update-notes/<upstream-head>.md path without exposing secrets.
• Preserve the note before launch so an agent crash cannot lose update context.
• If no supported agent exists or launch fails, print the complete prompt plus a safe manual invocation and return a clear result without changing Git state.
• Do not bypass the coding agent's own sandbox, approval, trust, or permission model.
• Do not push, deploy, resolve conflicts, or mark review complete merely because launch succeeded.

Flow

flowchart LR
  U["openbot update result"] --> N["Persist fork update note"]
  N --> L{"Configured agent launches?"}
  L -->|"yes"| A["Agent reviews fork semantics"]
  L -->|"no"| P["Print complete prompt and manual command"]
  A --> N

Loading

Acceptance criteria

• Success, conflict, failure, and no-update paths all attempt the configured handoff.
• Notes always exist before process launch; no-update notes contain exactly no updates before agent augmentation.
• Arguments are passed without shell evaluation or credential leakage.
• Unsupported/missing agents produce a useful manual fallback and preserve Git/update state.
• Launch success is reported separately from semantic-review completion.
• Tests cover invocation arguments, failed launch, missing integration, conflict handoff, and no-update handoff.
• CLI and configuration READMEs document selection, fallback, and security behavior.

Related

• ADR-0013: repository bootstrap and fork updates (refactor(app): reset UX and split deployments #8)