ffd5370464
* fix(#2903): use the command form that actually works in reader-facing docs Docs told readers to type the colon form, which no runtime registers -- 18 of 19 runtimes use slash-hyphen and the 19th uses shell-var -- so anyone copying an example got an unrecognized command. Swept 178 occurrences across 53 files, locale mirrors included so they do not re-diverge from English. The colon form is a source-authoring token, not a user-facing one: install-time converters key on it to produce the hyphen form runtimes actually register. So the sweep is scoped, and three things are deliberately left alone: - ADRs, which are a historical record; editing their prose falsifies what was written at the time. - The legacy release-notes archive, pending a maintainer decision on whether it follows the same historical carve-out. Excluding it keeps a later reversal additive rather than a revert. - Source artifacts under commands, workflows and agents, where the colon form is load-bearing. Rewriting those would break the installed-skill guarantee across every runtime -- the single largest hazard here. The plugin namespace form is a real, separate token and survives untouched. Adds a lint enforcing exactly that boundary, since the correct form genuinely differs by directory and nothing previously caught the drift. Also fixes a hardcoded colon form in the capability-matrix generator. The sweep alone would have left the generated matrix disagreeing with the template that produces it, so the fix is at the source and the output regenerated. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * fix(#2903): stop the sweep misquoting source frontmatter Adversarial review caught three lines where the sweep rewrote a citation of the literal YAML name: key from a source command file. That key genuinely is the colon form -- this change's own carve-out logic says source-authoring tokens keep it -- so the docs ended up misquoting the real files. One of the three is an acceptance-checklist assertion, which the sweep turned into a false statement. Restored the three citations to match their sources verbatim, surgically: where a line carried both a name: citation and a real reader-facing slash command, only the citation reverted and the command stayed corrected. The guard needed the same distinction, or it would have flagged the restoration and reddened the build: a gsd:<cmd> token preceded by name: is a citation of a source token and is now permitted. The exemption is deliberately narrow -- a bare gsd:<cmd> anywhere else still fails -- with a test pinning that narrowness. Also makes the detection case-insensitive. Review found /GSD:next slipped through silently; no such casing exists in the tree today, so this closes a latent gap rather than fixing a live one. Swept the whole tree for further corrupted citations: none beyond the three. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * fix(#2903): retire the stale-next invariant and sweep next like every other command Maintainer decision on a genuine conflict between two contracts. Invariant #3054 banned the literal /gsd-next from user-facing docs because it named a retired workflow-advance command. But commands/gsd/next.md is a live command -- the state-aware smart-entry launcher -- and this issue requires docs to use the hyphen form every runtime actually registers. Both could not hold for this one command, so docs had been sidestepping the ban by keeping the colon form, which is exactly the defect this issue exists to remove. FEATURES.md already recorded the reassignment: the hyphen form "is not the retired workflow-advance command; it is reserved for the state-aware smart-entry launcher. Workflow advancement remains under /gsd-progress --next." With that reassignment the invariant's premise is obsolete and the guard now contradicts the documented command form, so it is retired with a comment recording why rather than deleted silently. next is now swept like every other command, and the earlier exemption added to the new guard is removed so nothing is special-cased. Four citations of the literal name: frontmatter key stay in colon form, because the source file really does carry name: gsd:next and a doc quoting it must reproduce it verbatim. Two of those lines were reworded to say which side is the frontmatter key and which is the slash command, since they previously conflated the two. Verified the retired scan would now genuinely fail against this tree -- the conflict was real and resolved, not dodged. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * chore(#2903): backfill changeset pr number Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
3.3 KiB
Cleaning Up get-shit-done-cc
Use this procedure when you see a persistent ⬆ /gsd-update indicator in
your statusline even though @opengsd/gsd-core is already up to date. It
removes leftover files from the old get-shit-done-cc package that was
renamed to @opengsd/gsd-core in issue #607.
Why this happens
When the package was renamed, its version counter reset — get-shit-done-cc
reached 1.42.x while @opengsd/gsd-core started at 1.2.0. If the old
package is still installed in any runtime config directory (e.g. ~/.gemini),
its update checker writes a higher latest version into the shared update
cache (~/.cache/gsd/gsd-update-check.json), and older versions of the new
tooling accepted those foreign writes. The statusline then permanently shows
an upgrade that does not exist. The current installer detects and removes
these leftovers automatically, and the update cache is now per-package with a
package_name lineage field that readers validate — so a foreign package can
no longer poison it.
Steps
1. Preview the cleanup (dry run)
Run the installer with --dry-run to see exactly what it would change without
touching anything:
npx -y --package=@opengsd/gsd-core@latest -- gsd-core --claude --global --dry-run
The command prints the removal plan — each file path and the reason it would be deleted — and lists any stale update-cache files it would clear, then exits without making any modifications.
Swap --claude for the flag matching your runtime if you use a different one
(see the runtime flags table).
2. Apply the cleanup
Run the same installer without --dry-run:
npx -y --package=@opengsd/gsd-core@latest -- gsd-core --claude --global
The installer:
- Detects leftover
get-shit-done-ccartifacts across all runtime config directories (~/.claude,~/.gemini,~/.codex,~/.config/opencode,~/.kilo, and others). - Removes orphaned hooks, commands, and any file that references the old package name.
- Clears the stale shared update cache.
- Preserves user-owned artifacts such as
dev-preferences.md, custom agents, and any file not managed by GSD.
3. Manual fallback
If the installer cannot resolve get-shit-done-cc in your environment, or you
prefer to clean up by hand:
-
Check each runtime config directory for a
gsd-core/subtree left by the old package:ls ~/.claude/gsd-core/ ls ~/.gemini/gsd-core/ ls ~/.codex/gsd-core/ ls ~/.config/opencode/gsd-core/ ls ~/.kilo/gsd-core/Remove any directories found there that were written by
get-shit-done-cc(the new package installs under the same path, so only remove the directory if you have not yet run the new installer for that runtime). -
Uninstall the old package if it is still resolvable:
npx get-shit-done-cc --uninstall -
Delete the stale shared cache:
rm -f ~/.cache/gsd/gsd-update-check.json
4. Verify
Open a new terminal session (or restart your AI runtime). The ⬆ /gsd-update
indicator should no longer appear in the statusline. You can confirm the
installed version with:
npx @opengsd/gsd-core@latest -- gsd-core --version