design-canonical-wg — Workgraph live mirror

Metadata

Status	done
Assigned	`agent-814`
Agent identity	`f51439356729d112a6c404803d88015d5b44832c6c584c62b96732b63c2b0c7e`
Created	2026-04-27T17:38:33.203733849+00:00
Started	2026-04-27T18:40:54.723805623+00:00
Completed	2026-04-27T18:45:30.467757630+00:00
Tags	`eval-scheduled`
Tokens	0 in / 0 out

Description

Based on the audit produced by research-audit-wg, design the user-facing config UX:

Canonical default values for the global config that will ship as built-in defaults (no user file needed). Goal: a fresh install with no ~/.wg/config.toml should Just Work for the most common case (claude CLI executor, opus model, sensible parallelism).
wg setup improvements — interactive wizard for first-run that writes a minimal ~/.wg/config.toml AND/OR a project-local .wg/config.toml. Existing wg setup exists per CLAUDE.md — review and propose what changes.
wg config init — non-interactive command to write a minimal sane config to either global or local scope. wg config init --global / wg config init --local.
Migration path for existing users with stale configs (deprecated keys, old model strings, executor= keys). Two options:
- A. wg migrate config — opt-in command that rewrites configs to canonical form
- B. Auto-detect and warn-only (current behavior) until a future major version
TUI integration — wg setup from inside the TUI? A 'Settings' tab that edits config keys? Per memory feedback_launcher_history_in_config_ui.md, configuration UIs should also surface launcher_history.

Required artifacts

A design doc docs/config-ux-design.md with:

Decision: which config keys are global-only, project-only, or overridable
Concrete ~/.wg/config.toml and .wg/config.toml example files (the 'after' state)
Wireframes (text-based OK) of wg setup interactive flow
Decision: A vs B vs both for migration
One-line reason for each decision so a worker agent can implement without re-deciding

Validation

Design doc exists at docs/config-ux-design.md
Cites the research audit doc for every keys-decision
Concrete example files present and runnable (paste into ~/.wg/config.toml and wg starts cleanly)
Migration path picked with rationale
TUI integration scope decided (in-this-task vs follow-up task)
No design forks left for the implementer to decide; if any remain, list them as open questions for the user

## Description

Based on the audit produced by `research-audit-wg`, design the user-facing config UX:

1. **Canonical default values** for the global config that will ship as built-in defaults (no user file needed). Goal: a fresh install with no `~/.wg/config.toml` should Just Work for the most common case (claude CLI executor, opus model, sensible parallelism).

2. **`wg setup` improvements** — interactive wizard for first-run that writes a minimal `~/.wg/config.toml` AND/OR a project-local `.wg/config.toml`. Existing `wg setup` exists per CLAUDE.md — review and propose what changes.

3. **`wg config init`** — non-interactive command to write a minimal sane config to either global or local scope. `wg config init --global` / `wg config init --local`.

4. **Migration path** for existing users with stale configs (deprecated keys, old model strings, executor= keys). Two options:
   - A. `wg migrate config` — opt-in command that rewrites configs to canonical form
   - B. Auto-detect and warn-only (current behavior) until a future major version

5. **TUI integration** — `wg setup` from inside the TUI? A 'Settings' tab that edits config keys? Per memory `feedback_launcher_history_in_config_ui.md`, configuration UIs should also surface launcher_history.

## Required artifacts

A design doc `docs/config-ux-design.md` with:
- Decision: which config keys are global-only, project-only, or overridable
- Concrete `~/.wg/config.toml` and `.wg/config.toml` example files (the 'after' state)
- Wireframes (text-based OK) of `wg setup` interactive flow
- Decision: A vs B vs both for migration
- One-line reason for each decision so a worker agent can implement without re-deciding

## Validation

- [ ] Design doc exists at docs/config-ux-design.md
- [ ] Cites the research audit doc for every keys-decision
- [ ] Concrete example files present and runnable (paste into ~/.wg/config.toml and wg starts cleanly)
- [ ] Migration path picked with rationale
- [ ] TUI integration scope decided (in-this-task vs follow-up task)
- [ ] No design forks left for the implementer to decide; if any remain, list them as open questions for the user

Depends on

done .assign-design-canonical-wg

Required by

(none)

Log

2026-04-27T17:38:33.189912149+00:00 Task paused
2026-04-27T17:38:54.607780855+00:00 Task published
2026-04-27T17:39:52.733731773+00:00 Lightweight assignment: agent=Careful Programmer (f5143935), exec_mode=light, context_scope=task, reason=Careful Programmer understands system architecture and can synthesize design docs with implementation-aware UX decisions; Careful tradeoff suits the deliberate thinking required for config UX design.
2026-04-27T17:49:31.409626452+00:00 Spawned by coordinator --executor claude --model opus
2026-04-27T17:49:34.823380715+00:00 Task marked as failed: Agent exited with code 1
2026-04-27T18:39:11.139741402+00:00 Reset by `wg recover` — reason: openrouter outage cleanup; everything moved to claude:opus
2026-04-27T18:40:54.723807606+00:00 Spawned by coordinator --executor claude --model opus
2026-04-27T18:41:05.299988329+00:00 Resuming task — reading research audit doc to inform design
2026-04-27T18:41:40.591231243+00:00 Audit reviewed; drafting docs/config-ux-design.md with built-in defaults, wg config init subcommand, route-based wg setup, migration pick, and TUI scope decision.
2026-04-27T18:45:06.035011943+00:00 Validated: all 3 example TOMLs (minimal global, openrouter global, local repo override) load cleanly via 'wg config --show' with no warnings.
2026-04-27T18:45:26.342172593+00:00 Committed: a08033b9f — pushed to remote
2026-04-27T18:45:30.470791970+00:00 Task marked as done