make-worksgood-thin-existing-graph-launcher

Make worksgood a thin existing-graph TUI launcher

Metadata

Statusdone
Created2026-07-31T08:35:54.972894619+00:00
Started2026-07-31T11:34:06.258287600+00:00
Completed2026-08-03T09:42:52.410712894+00:00
Tagsdraft, worksgood, tui, concierge, ux
Tokens9765311 in / 26063 out

Description

Make bare worksgood a thin launcher once a repository already has .wg. The concierge exists to bootstrap a new repository or when explicitly requested through worksgood setup; it must not run on every normal entry.

Required behavior:

  • Existing repository with .wg: resolve the authenticated absolute sibling wg executable and directly exec/open wg tui with the exact project graph. Do not discover Pi, ensure the Pi plugin, read/reconcile concierge state, print onboarding prose, choose routes, or touch services/config.
  • Repository without .wg: run the minimal new-repo concierge/bootstrap, allowing route-free graph/TUI setup; then open the TUI.
  • worksgood setup: explicit advanced concierge for unattended automation on new or existing graphs.
  • worksgood tui: remain a setup-neutral explicit alias, but bare worksgood on an existing graph should be behaviorally equivalent.
  • TUI owns chat creation and reports executor/Pi availability only when the user chooses that action.

Validation

  • Existing .wg invocation executes the same TUI path/argv and state effects as wg tui, with no Pi/plugin/profile/service/concierge reads or writes.
  • Existing graph opens when Pi is absent; only choosing New chat → Pi produces an actionable Pi error.
  • Fresh repository gets bootstrap exactly once, then subsequent invocations bypass concierge.
  • worksgood setup retains explicit automation route/reasoning/service gates.
  • Credential-free PTY smoke compares bare worksgood, worksgood tui, and wg tui on an existing graph and proves no setup mutation.

Depends on

Required by

Log