← graph

fix-complete-the

Fix: complete the wgnext→nex rename — init-starters must write nex.toml

Metadata

Statusdone
Assignedagent-1082
Agent identityf51439356729d112a6c404803d88015d5b44832c6c584c62b96732b63c2b0c7e
Created2026-04-29T11:55:58.933607353+00:00
Started2026-04-29T12:14:46.679858727+00:00
Completed2026-04-29T12:23:24.268080362+00:00
Tagsfix,profiles,naming, eval-scheduled
Tokens1617895 in / 5147 out
Eval score0.77
└ blocking impact0.76
└ completeness0.85
└ constraint fidelity0.70
└ coordination overhead0.68
└ correctness0.78
└ downstream usability0.75
└ efficiency0.72
└ intent fidelity0.88
└ style adherence0.80

Description

Description

The earlier rename-wgnext-profile task (commit 3eee268de) only added a deprecation warning to wg profile list output. It did NOT:

  1. Make wg profile init-starters write nex.toml (still writes wgnext.toml)
  2. Auto-migrate existing wgnext.toml files on upgrade
  3. Remove wg-next (with hyphen) from the description string

Verified live 2026-04-29: a fresh wg profile init-starters writes ~/.wg/profiles/wgnext.toml and the listing shows the deprecation hint asking the USER to manually mv the file. That's not a rename, that's homework.

User reaction: 'wgnext what is this?? there is no wgnext. should be wgnex or nex!! ideally nex!'

Scope — finish the rename, properly

  1. wg profile init-starters writes ~/.wg/profiles/nex.toml (not wgnext.toml). Single source name.
  2. The starter content's description field reads 'wg nex: in-process nex handler...' — no hyphenated 'wg-next' anywhere.
  3. On wg profile init-starters: if wgnext.toml already exists from a prior run, auto-rename it to nex.toml (idempotent: if nex.toml already exists too, skip with a one-line note). User should never have to mv manually.
  4. The wg profile list deprecation warning can stay (for users with hand-edited or pre-existing wgnext.toml files), but on a system with only nex.toml, no warning should print.
  5. wg profile use wgnext continues to work as a legacy alias (loads nex.toml if wgnext.toml doesn't exist) so existing scripts don't break.
  6. grep the codebase for any remaining wgnext, wg-next, or wg_next strings outside of the legacy back-compat layer; remove from docs, help text, error messages, and CLI examples.

Validation

  • Failing test written first: assert that a fresh wg profile init-starters (against an empty profiles dir) writes nex.toml and NOT wgnext.toml
  • Test: with a pre-existing wgnext.toml, wg profile init-starters auto-renames it to nex.toml (verify by file existence post-run)
  • Test: with both wgnext.toml and nex.toml present, init-starters skips the rename with a one-line note (no clobber)
  • wg profile list on a system with only nex.toml prints no deprecation warning
  • wg profile use wgnext still works as a legacy alias
  • grep the codebase: zero occurrences of wgnext or wg-next outside the legacy back-compat layer
  • Live smoke: rm -rf a tmpdir, WG_DIR=tmp wg profile init-starters, ls the profiles dir, see nex.toml + claude.toml + codex.toml only
  • cargo build + cargo test pass
  • cargo install --path . was run before claiming done

Process note

Same recurring pattern: rename-wgnext-profile claimed done with a deprecation warning instead of actually completing the rename. Per the user's feedback ('verify exhaustively before claiming done'), this task's validation requires evidence — paste ls output of a fresh init-starters into the task log to prove no wgnext.toml is written.

Depends on

Required by

Log