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.

docs/design/verifier-reach.md

@@ -5,8 +5,8 @@
 > point-in-time decisions it references are owned by ADR-550, ADR-857, and ADR-1606.
 >
 > **Attribution.** The calibration evidence below is *the author's own research* (the
-> verifier-reach experiment program). It is cited here as the **motivation** for a GSD design
-> principle — it is not claimed as a novel GSD contribution, and the principle's *framing* is
+> verifier-reach experiment program). It is cited here as the **motivation** for a MSD design
+> principle — it is not claimed as a novel MSD contribution, and the principle's *framing* is
 > the author's. External prior art exists for individual pillars (clarification-questioning,
 > omission-decay, conformal abstention); specific citations are deliberately omitted pending
 > primary-source verification before being written down.
@@ -46,7 +46,7 @@ The conclusion is structural: reliability is **not** a verifier-tuning problem.
 is fine *when the predicate exists*; it fails when the predicate was never written. So the
 leverage is upstream — make the missing predicate exist.
 
-## How GSD operationalizes the principle
+## How MSD operationalizes the principle
 
 Three moves, each a member of the probe family or its enforcement seam:
 
@@ -105,7 +105,7 @@ Three moves, each a member of the probe family or its enforcement seam:
   test-tier mechanism); its "Alternatives considered" holds the enforcement-side rejections.
 - **ADR-857** — *"Verification substrate vs. plug-in tier (the predicate boundary)"* section
   (decision #6): the verifier↔predicate contract is core, non-toggleable.
-- Refs: `gsd-core/references/{edge-probe,prohibition-probe}.md`; CONTEXT.md predicate
+- Refs: `msd-core/references/{edge-probe,prohibition-probe}.md`; CONTEXT.md predicate
   `PROBE.principle=verifier-reach-equals-spec-reach`.
 - Author's research (internal): non-inferable corpus; edge-probe residual (n=121); N17
   verifier-abstention; N18 prohibition-elicitation.