nntrivi2001
9c573f1e3c
Decisions, environment quirks and pitfalls learned while working on AgentHub (docs/claude-memory/, indexed by MEMORY.md). Notes holding personal account details are left out. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.4 KiB
name, description, metadata
| name | description | metadata | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| workspace-rename-step4 | Removing the old `agenthub lanes`/`--lane` CLI names is deferred to ≥3 releases after the aliases ship; never touch stored data |
|
On 2026-10-06 the user had steps 1–3 of the lane→workspace rename built (aliases /api/workspaces, agenthub workspace, --workspace; help/docs on the new name; a stderr deprecation note for agenthub lanes/--lane). Step 4 (removing the old CLI names, moving client+CLI requests to /api/workspaces) is deferred until the THIRD release after the first one that ships the aliases (the first release after v2.0.1). The plan, checklist and "never touch" list are in docs/plans/workspace-rename/README.md.
Why: the user wants existing installs to update gradually and NOT lose any data — DB tables/columns, response keys, tmux names agenthub-lane-<id>, env vars, on-disk paths and browser storage keys must never be renamed.
How to apply: when cutting a release, check whether it is ≥ R+3 (R is recorded in that plan file — fill it in when R is cut) and remind the user that step 4 is due; keep /api/lanes unless the user decides otherwise (step 4c, default keep).
R = v2.1.0 (released 2026-10-06), so step 4 is allowed from the 3rd release after v2.1.0.