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,12 +1,12 @@
# Custom PR Body Sections
`/gsd-ship` creates a pull request body from the planning artifacts for a verified phase. Projects can append extra PRD-style sections to that body with `ship.pr_body_sections` in `.planning/config.json`.
`/msd-ship` creates a pull request body from the planning artifacts for a verified phase. Projects can append extra PRD-style sections to that body with `ship.pr_body_sections` in `.planning/config.json`.
Use this when your project needs the PR to carry more release context than the default GSD sections, such as user stories, acceptance criteria, risks, release criteria, or stakeholder approval notes.
Use this when your project needs the PR to carry more release context than the default MSD sections, such as user stories, acceptance criteria, risks, release criteria, or stakeholder approval notes.
## What GSD Always Includes
## What MSD Always Includes
Every generated `/gsd-ship` PR body keeps the required core sections:
Every generated `/msd-ship` PR body keeps the required core sections:
- `Summary`
- `Changes`
@@ -29,7 +29,7 @@ gate-status: skill=3, fallback=1, exempt=0, missing=0
## Configure Sections During Onboarding
During `/gsd-new-project`, GSD can seed optional PRD-style sections into `.planning/config.json`.
During `/msd-new-project`, MSD can seed optional PRD-style sections into `.planning/config.json`.
Recommended onboarding choices:
@@ -38,14 +38,14 @@ Recommended onboarding choices:
- `Success Metrics & Release Criteria` for Definition of Done, measurable outcomes, and release checks.
- `Stakeholder Review & Approval` for sign-off traceability.
Selected sections are written with `"enabled": true`. Seeded but unselected sections are written with `"enabled": false`, so you can enable them later without editing the shipped `/gsd-ship` workflow.
Selected sections are written with `"enabled": true`. Seeded but unselected sections are written with `"enabled": false`, so you can enable them later without editing the shipped `/msd-ship` workflow.
## Configure Sections Manually
Set `ship.pr_body_sections` with `gsd-tools query config-set`:
Set `ship.pr_body_sections` with `msd-tools query config-set`:
```bash
gsd-tools query config-set ship.pr_body_sections '[{"heading":"Risks & Dependencies","enabled":true,"source":"PLAN.md ## Risks || PLAN.md ## Dependencies","fallback":"- No known high-risk rollout dependencies."}]'
msd-tools query config-set ship.pr_body_sections '[{"heading":"Risks & Dependencies","enabled":true,"source":"PLAN.md ## Risks || PLAN.md ## Dependencies","fallback":"- No known high-risk rollout dependencies."}]'
```
You can also edit `.planning/config.json` directly:
@@ -108,7 +108,7 @@ Allowed source files:
- `REQUIREMENTS.md`
- `CONTEXT.md`
If the first selector has no content, GSD tries the next selector. If no selector produces content, GSD uses `fallback` when present. Empty final bodies are omitted.
If the first selector has no content, MSD tries the next selector. If no selector produces content, MSD uses `fallback` when present. Empty final bodies are omitted.
## Template Tokens