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.

scripts/lint-state-write-path-drift.cjs

@@ -15,7 +15,7 @@
  * guard used to track as a RATCHETED STRING MATCH against
  * `scripts/state-write-path-drift-baseline.json` — `cmdStateSync`
  * (`src/state.cts`, #905's "let the body win") and `REGENERATE_STATE`
- * (`src/health-diagnostic.cts`, `/gsd-health --repair`'s factory reset) — are
+ * (`src/health-diagnostic.cts`, `/msd-health --repair`'s factory reset) — are
  * NO LONGER TRACKED HERE. Both are now a constructor the type system names
  * (`rebuildStateTransaction`), not an entry a human had to remember to keep
  * acknowledging in a baseline file. That baseline file, and the whole
@@ -79,7 +79,7 @@
  *   dataflow — see the function's own docstring).
  *
  *   AXIS 4 — PROMPT-LAYER WRITE (§8.3, Decision 4(d)). Prose in the prompt
- *   layer instructing an agent to shell out to a write-side `gsd-tools`
+ *   layer instructing an agent to shell out to a write-side `msd-tools`
  *   subcommand is the same write seam, expressed as markdown rather than
  *   TypeScript — a check the type system cannot reach at all, since markdown
  *   is never compiled. Any occurrence is a violation.
@@ -100,7 +100,7 @@
  *     nothing.
  *   - 4(d) the scan surface is DECLARED and is NOT just `src/` — `src/`
  *     alone is itself an allowlist one directory wide; #1762 traced a wrong
- *     count to a shell snippet in `gsd-core/workflows/progress.md`.
+ *     count to a shell snippet in `msd-core/workflows/progress.md`.
  *
  * GOODHART, PER ADR-3408 DECISION 5: "0 violations" is a LAGGING metric — a
  * measure about to become a target. This guard's own `_comment` and its
@@ -133,7 +133,7 @@
  * #3871 review) all remain, because §8.6 names neither them nor anything
  * that makes what they check unrepresentable — a field-name-keyed dispatch
  * branch, an unimplemented `FieldPreservation` policy, an unstripped
- * frontmatter write, prompt-layer prose shelling out to `gsd-tools`, and a
+ * frontmatter write, prompt-layer prose shelling out to `msd-tools`, and a
  * re-assembled write-seam composition are all still exactly as representable
  * in TypeScript (or in markdown, for the prompt-layer one) after the
  * state-transaction constructor as they were before it — the constructor
@@ -144,7 +144,7 @@
 
 const path = require('node:path');
 const { scanTree, sanitizeForReport } = require('./lib/drift-scan.cjs');
-const { escapeRegex } = require('../gsd-core/bin/lib/pattern.cjs');
+const { escapeRegex } = require('../msd-core/bin/lib/pattern.cjs');
 
 const REPO_ROOT = path.resolve(__dirname, '..');
 
@@ -169,7 +169,7 @@ const REASON = Object.freeze({
   // wired terminal in C2 as the residual callers migrate (ADR-3408 §6 phasing).
   OPAQUE_STATE_TRANSFORM: 'opaque_state_transform',
   // Axis 4 (§8.3, Decision 4(d)): prompt-layer prose shelling out to a
-  // write-side `gsd-tools` subcommand — see `findPromptSeamUses`.
+  // write-side `msd-tools` subcommand — see `findPromptSeamUses`.
   PROMPT_LAYER_STATE_WRITE: 'prompt_layer_state_write',
   // Axis 5 (§8.3, RETAINED, issue #3871): a direct `syncStateFrontmatter(` or
   // `applyPostSyncPreservation(` call outside their owner
@@ -183,7 +183,7 @@ const REASON = Object.freeze({
 // result outside any TypeScript this guard could see.
 const SRC_DIRS = ['src'];
 const SRC_EXT = new Set(['.cts']);
-const PROMPT_DIRS = ['gsd-core/workflows', 'commands', 'agents', 'skills'];
+const PROMPT_DIRS = ['msd-core/workflows', 'commands', 'agents', 'skills'];
 const PROMPT_EXT = new Set(['.md']);
 
 // The executor (Axis 1 / Axis 3). Forward-slash literal: every `rel` this
@@ -783,7 +783,7 @@ function findCompositionBypasses(rel, text) {
   return out;
 }
 
-// Prose in the prompt layer shelling out to a write-side `gsd-tools`
+// Prose in the prompt layer shelling out to a write-side `msd-tools`
 // subcommand — the SAME write seam, expressed as markdown instructing an
 // agent to run a command, rather than TypeScript calling a function
 // directly (Decision 4(d)'s "the scan surface is declared, and is not just
@@ -791,7 +791,7 @@ function findCompositionBypasses(rel, text) {
 // carries no comment syntax this guard should be stripping in the first
 // place. `g`-flagged so multiple candidate occurrences on one line are all
 // checked against backtick spans below, rather than only the first.
-const PROMPT_SEAM_RE = /gsd[-_]?tools[^\n]*\b(state\.patch|state\.planned-phase|state\.sync|phase\.complete)\b/g;
+const PROMPT_SEAM_RE = /msd[-_]?tools[^\n]*\b(state\.patch|state\.planned-phase|state\.sync|phase\.complete)\b/g;
 
 /**
  * Every `` `...` `` inline-code span on `line`, as `[start, end)` character
@@ -822,7 +822,7 @@ function isInsideCodeSpan(line, index) {
 
 /**
  * AXIS 4: every prompt-layer line instructing an agent to shell out to a
- * write-side `gsd-tools` subcommand. Terminal (unratcheted): any occurrence
+ * write-side `msd-tools` subcommand. Terminal (unratcheted): any occurrence
  * is a violation — this baseline was always empty for the prompt layer (no
  * prompt-layer entry was ever acknowledged), so removing the ratchet changes
  * nothing observable here.