rename-wgnext-profile — Workgraph live mirror

Metadata

Status	done
Assigned	`agent-1060`
Agent identity	`f51439356729d112a6c404803d88015d5b44832c6c584c62b96732b63c2b0c7e`
Created	2026-04-29T01:58:12.837527808+00:00
Started	2026-04-29T01:58:40.147187802+00:00
Completed	2026-04-29T02:11:15.491535868+00:00
Tags	`fix,profiles,naming`, `eval-scheduled`
Eval score	0.94
└ blocking impact	0.95
└ completeness	0.98
└ coordination overhead	0.92
└ correctness	0.95
└ downstream usability	0.90
└ efficiency	0.90
└ intent fidelity	0.93
└ style adherence	0.92

Description

The in-process LLM handler is invoked via wg nex (e.g., wg nex --help shows 'Interactive agentic REPL'). But the starter profile is named wgnext (one word, no space) and described as 'wg-next' (with dash) in wg profile list output. Three spellings for one thing.

User caught this: 'wgnext? wg nex right????'

Scope

Pick a single canonical name for this thing and use it everywhere. Recommendation: nex (matches the subcommand exactly).

Changes needed:

The starter profile file written by wg profile init-starters: rename ~/.wg/profiles/wgnext.toml → ~/.wg/profiles/nex.toml
The starter's description field: 'wg nex: in-process LLM handler at a localhost endpoint (edit URL per machine)' (drop the 'wg-next' hyphenation)
The wg profile list output line: [builtin] nex wg nex: in-process LLM handler...
Any docs / help text that says wgnext or wg-next: update to wg nex or nex (as a profile name)
Migration: if a user already ran wg profile init-starters and has wgnext.toml on disk, recognize it as the legacy name (continue to load it) but warn that the canonical name is nex and offer wg profile rename wgnext nex (or just auto-migrate on next wg profile init-starters).

Validation

Failing test written first: assert the starter profile file written by wg profile init-starters is named nex.toml
wg profile list shows the profile as nex (not wgnext)
Existing wgnext.toml on disk continues to work (backward compat) with a deprecation hint
No remaining wgnext or wg-next strings in CLI output, help text, or docs (grep is your friend)
cargo build + cargo test pass
cargo install --path . was run before claiming done

## Description
The in-process LLM handler is invoked via `wg nex` (e.g., `wg nex --help` shows 'Interactive agentic REPL'). But the starter profile is named `wgnext` (one word, no space) and described as 'wg-next' (with dash) in `wg profile list` output. Three spellings for one thing.

User caught this: 'wgnext? wg nex right????'

## Scope
Pick a single canonical name for this thing and use it everywhere. Recommendation: **`nex`** (matches the subcommand exactly).

Changes needed:
1. The starter profile file written by `wg profile init-starters`: rename `~/.wg/profiles/wgnext.toml` → `~/.wg/profiles/nex.toml`
2. The starter's `description` field: 'wg nex: in-process LLM handler at a localhost endpoint (edit URL per machine)' (drop the 'wg-next' hyphenation)
3. The `wg profile list` output line: `[builtin] nex            wg nex: in-process LLM handler...`
4. Any docs / help text that says wgnext or wg-next: update to `wg nex` or `nex` (as a profile name)
5. Migration: if a user already ran `wg profile init-starters` and has `wgnext.toml` on disk, recognize it as the legacy name (continue to load it) but warn that the canonical name is `nex` and offer `wg profile rename wgnext nex` (or just auto-migrate on next `wg profile init-starters`).

## Validation
- [ ] Failing test written first: assert the starter profile file written by `wg profile init-starters` is named `nex.toml`
- [ ] `wg profile list` shows the profile as `nex` (not `wgnext`)
- [ ] Existing `wgnext.toml` on disk continues to work (backward compat) with a deprecation hint
- [ ] No remaining `wgnext` or `wg-next` strings in CLI output, help text, or docs (grep is your friend)
- [ ] cargo build + cargo test pass
- [ ] cargo install --path . was run before claiming done

Depends on

done .assign-rename-wgnext-profile

Required by

(none)

Log

2026-04-29T01:58:12.823392618+00:00 Task paused
2026-04-29T01:58:16.618996256+00:00 Task published
2026-04-29T01:58:38.638332010+00:00 Lightweight assignment: agent=Careful Programmer (f5143935), exec_mode=full, context_scope=task, reason=Careful Programmer with strong prior score (0.76) on 263 tasks is ideal for this refactoring that requires careful test-first implementation, exhaustive reference checking, and backward-compatibility handling
2026-04-29T01:58:40.147192911+00:00 Spawned by coordinator --executor claude --model opus
2026-04-29T01:58:49.972398723+00:00 Starting work — searching for wgnext / wg-next references in the codebase
2026-04-29T01:59:49.842081310+00:00 Plan: rename wgnext.toml->nex.toml; STARTER_NAMES uses 'nex'; init_starters auto-migrates legacy wgnext.toml on disk; load() falls back to wgnext.toml with deprecation hint; update docs + CLI help + smoke test
2026-04-29T02:10:46.929738593+00:00 Validated: cargo build + cargo test (lib + integration_profile_tier_pinning) pass; live-tested wg profile init-starters / list / show / use against fresh and legacy profile dirs; new profile_nex_canonical_name smoke scenario passes
2026-04-29T02:11:06.692325822+00:00 Committed: 575cc4831 — pushed to remote (wg/agent-1060/rename-wgnext-profile)
2026-04-29T02:11:15.491543833+00:00 Task pending eval (agent reported done; awaiting `.evaluate-*` to score)
2026-04-29T02:13:51.846243368+00:00 PendingEval → Done (evaluator passed; downstream unblocks)