refactor: hard-fork GSD -> MSD (Make Software Done)

Mechanical rename produced by scripts/msd-rename.cjs: gsd/Gsd/GSD -> msd/Msd/MSD
across contents and paths, upstream package/repo coordinates -> @golem15/msd-core
and golem15com/msd-core. Deep links into upstream history, sibling upstream
packages, the GSD-2 import feature, CHANGELOG.md and .changeset/ are kept as-is.

Hand edits on top: MSD block-letter banner and logos, LICENSE copyright line,
package/plugin identity, regenerated lockfile, install-tree fixtures, derived
registries and benchmark baseline; migration checksum baseline re-locked
(MSD keeps its own install state, so no install had applied the old sums);
sort-order and regex-escaped expectations in tests adjusted.
This commit is contained in:
Jakub Zych
2026-10-06 01:47:40 +02:00
parent fe069b2a56
commit a9a7a328e6
2763 changed files with 78465 additions and 78434 deletions

View File

@@ -1,6 +1,6 @@
# Keep planning docs out of a shared repo
You are working in a team repo and want GSD's `.planning/` artifacts — PLAN.md, SUMMARY.md,
You are working in a team repo and want MSD's `.planning/` artifacts — PLAN.md, SUMMARY.md,
ROADMAP.md, STATE.md — to stay on your machine instead of appearing in commits your teammates read.
This takes four steps, and the third is the one people miss.
@@ -8,10 +8,10 @@ This takes four steps, and the third is the one people miss.
## 1. Turn off doc commits
```bash
gsd-tools config-set planning.commit_docs false
msd-tools config-set planning.commit_docs false
```
`gsd-tools query commit` now returns a `skipped` envelope instead of committing, and every workflow
`msd-tools query commit` now returns a `skipped` envelope instead of committing, and every workflow
that writes a planning artifact honors it.
## 2. Ignore the directory
@@ -23,7 +23,7 @@ Add to `.gitignore`:
```
This is also enough on its own: when `.planning/` is gitignored and `config.json` sets no explicit
value, GSD auto-resolves `commit_docs` to `false`. Setting it explicitly in step 1 is clearer, and
value, MSD auto-resolves `commit_docs` to `false`. Setting it explicitly in step 1 is clearer, and
it survives someone later editing `.gitignore`.
## 3. Untrack what git is already tracking
@@ -32,7 +32,7 @@ it survives someone later editing `.gitignore`.
It has no effect on files already committed — git keeps tracking those, so `git add -A` keeps
staging them even though steps 1 and 2 are both done.
Because GSD's default is `commit_docs: true`, most existing projects already have `.planning/`
Because MSD's default is `commit_docs: true`, most existing projects already have `.planning/`
in history, which makes this the common case rather than an edge case.
```bash
@@ -52,12 +52,12 @@ Any output means git is still tracking those paths.
## 4. Keep search working
With `.planning/` ignored, tools that respect `.gitignore` stop searching it — including GSD's own
With `.planning/` ignored, tools that respect `.gitignore` stop searching it — including MSD's own
broad searches, which is rarely what you want, since the planning docs are exactly what you want an
agent to read.
```bash
gsd-tools config-set planning.search_gitignored true
msd-tools config-set planning.search_gitignored true
```
This adds `--no-ignore` to broad searches so `.planning/` is still found locally.
@@ -65,7 +65,7 @@ This adds `--no-ignore` to broad searches so `.planning/` is still found locally
## Verify
```bash
gsd-tools validate health
msd-tools validate health
```
A clean result means you are done. If you skipped step 3, you will see:
@@ -75,7 +75,7 @@ W029 .planning/ is gitignored but N file(s) are still tracked by git
Fix: git rm -r --cached .planning/ && git commit -m "chore: stop tracking planning docs"
```
`W029` is advisory. GSD will not untrack files for you, and `--repair` deliberately does not act on
`W029` is advisory. MSD will not untrack files for you, and `--repair` deliberately does not act on
it — removing files from the index is destructive and the timing is yours.
## Notes
@@ -96,8 +96,8 @@ team — committed while every other phase stays local, set a `phase_commit_docs
phase's number instead of (or on top of) the project-wide switch:
```bash
gsd-tools config-set planning.commit_docs false
gsd-tools config-set phase_commit_docs.03 true
msd-tools config-set planning.commit_docs false
msd-tools config-set phase_commit_docs.03 true
```
```json
@@ -107,7 +107,7 @@ gsd-tools config-set phase_commit_docs.03 true
}
```
Now `gsd-tools query commit` commits phase 03's artifacts normally, and skips (with the
Now `msd-tools query commit` commits phase 03's artifacts normally, and skips (with the
`skipped_commit_docs_phase_false`-or-`skipped_commit_docs_false` reason depending on which tier
decided) every other phase's — the project-wide setting from step 1 still governs everything
`phase_commit_docs` does not name.
@@ -115,10 +115,10 @@ decided) every other phase's — the project-wide setting from step 1 still gove
A few things worth knowing before you rely on this:
- **The phase-id form doesn't matter.** `phase_commit_docs.3`, `phase_commit_docs.03`, and (if your
project uses a `project_code`) `phase_commit_docs.PROJ-03` all resolve to the same entry — GSD
project uses a `project_code`) `phase_commit_docs.PROJ-03` all resolve to the same entry — MSD
normalizes the phase number before lookup, the same way it does everywhere else phase numbers are
compared.
- **It only applies to a commit that names a phase-scoped file.** `gsd-tools query commit` resolves
- **It only applies to a commit that names a phase-scoped file.** `msd-tools query commit` resolves
the phase from the `--files` paths you pass it (via the `.planning/phases/<phase-dir>/…`
segment). A commit that names no phase file — e.g. a bare `ROADMAP.md` update — has no phase to
look up, so `phase_commit_docs` never applies to it and the project-wide setting governs, same as
@@ -136,33 +136,33 @@ for the complete rules, including how a non-boolean value is handled.
## Pre-commit guard hook (optional)
Steps 1-4 stop **GSD's own** commit path from writing `.planning/`. They do not stop a plain
`git add -A` + `git commit` — run by hand, by a teammate, or by a script outside GSD's own
tooling — from staging and committing `.planning/` anyway. `gsd-tools commit-docs-guard enable`
Steps 1-4 stop **MSD's own** commit path from writing `.planning/`. They do not stop a plain
`git add -A` + `git commit` — run by hand, by a teammate, or by a script outside MSD's own
tooling — from staging and committing `.planning/` anyway. `msd-tools commit-docs-guard enable`
closes that specific gap by installing a `.git/hooks/pre-commit` hook that refuses any commit
staging `.planning/` files while `commit_docs` resolves to `false`. Resolution honors the full
precedence chain above — including a `phase_commit_docs.<phase-id>` override for the phase the
staged `.planning/` files belong to — the same resolution `gsd-tools commit`/`query commit` uses,
staged `.planning/` files belong to — the same resolution `msd-tools commit`/`query commit` uses,
so the hook never contradicts them.
This is opt-in only — no GSD install path wires it in for you:
This is opt-in only — no MSD install path wires it in for you:
```bash
gsd-tools commit-docs-guard enable
msd-tools commit-docs-guard enable
```
If a commit would violate `commit_docs`, the hook blocks it and names the staged files and the
`git reset` command to unstage them, matching `gsd-tools check-commit`'s own message. Remove it
`git reset` command to unstage them, matching `msd-tools check-commit`'s own message. Remove it
with:
```bash
gsd-tools commit-docs-guard disable
msd-tools commit-docs-guard disable
```
**Enable refuses rather than guesses** in three situations, each reported with a reason:
- **An existing `pre-commit` hook you didn't get from GSD.** The file is left byte-for-byte
unchanged; wire the guard into it by hand (`gsd-tools check-commit --raw` is the check to add).
- **An existing `pre-commit` hook you didn't get from MSD.** The file is left byte-for-byte
unchanged; wire the guard into it by hand (`msd-tools check-commit --raw` is the check to add).
- **`core.hooksPath` is already configured.** A hook written to `.git/hooks/pre-commit` would
never run in that case, so nothing is written; add the same check to whatever hook lives at the
configured path instead.
@@ -170,13 +170,13 @@ gsd-tools commit-docs-guard disable
`enable`/`disable` are idempotent and safe to script: a second `enable` is a no-op that reports
success rather than duplicating content, and `disable` on a repo with no hook installed succeeds
rather than erroring. The hook is identified by a stable `# gsd-core:commit-docs-guard` marker
rather than erroring. The hook is identified by a stable `# msd-core:commit-docs-guard` marker
line inside the file, checked by presence rather than exact content — appending your own line to
the installed hook afterward does not make GSD stop recognizing it as its own. In a linked
the installed hook afterward does not make MSD stop recognizing it as its own. In a linked
worktree or submodule (where `.git` is a file, not a directory), `enable` resolves the real,
shared hooks directory via git itself rather than assuming a literal `.git/hooks` path.
Windows note: the hook runs under Git Bash, same as any other git hook. GSD's own remote test
Windows note: the hook runs under Git Bash, same as any other git hook. MSD's own remote test
matrix is Linux-only, so this specific behavior is verified on Linux/macOS plus code review, not
by an automated Windows run.
@@ -185,7 +185,7 @@ by an automated Windows run.
Everything above keeps `.planning/` out of git, and that has one consequence worth knowing before
you commit to it: **parallel executor worktrees stop working.** A worktree is checked out from a
commit, so an untracked or ignored `.planning/` does not exist inside it and the executor has no
`PLAN.md` to read. Untracked planning also has no git history, so `/gsd-undo` and revert paths have
`PLAN.md` to read. Untracked planning also has no git history, so `/msd-undo` and revert paths have
nothing to restore.
If what you actually want is "planning is versioned locally, but never reaches the remote", leave