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-response-language-coverage.cjs

@@ -41,10 +41,10 @@ const fs = require('fs');
 const path = require('path');
 
 const ROOT = path.join(__dirname, '..');
-const WORKFLOWS_DIR = path.join(ROOT, 'gsd-core', 'workflows');
+const WORKFLOWS_DIR = path.join(ROOT, 'msd-core', 'workflows');
 // A reference resolves as a sibling of the workflow catalog, so a fixture tree
 // and the real one resolve by one rule.
-const REFERENCE_ROOT = path.join(ROOT, 'gsd-core');
+const REFERENCE_ROOT = path.join(ROOT, 'msd-core');
 const DIRECTIVE_REFS = [
   'references/response-language-directive.md',
   'references/execute-phase-response-language.md',
@@ -91,7 +91,7 @@ const EXACT_INLINE_DIRECTIVE_WORKFLOWS = new Set([
 ]);
 // This lint once carried a third coverage form, for `verify-phase.md`: a
 // workflow file nothing entered directly, covered instead by the directive
-// execute-phase.md injects into its `gsd-verifier` dispatch prompt. `next`
+// execute-phase.md injects into its `msd-verifier` dispatch prompt. `next`
 // deleted that workflow in #3421 (an orphan that shipped ~40 KB to every runtime
 // and was never loaded) and migrated its live gates into the verifier, so the
 // form has no subject left and is gone with it.
@@ -105,7 +105,7 @@ const EXACT_INLINE_DIRECTIVE_WORKFLOWS = new Set([
 // positions against in execute-phase.md) directly against the real tree.
 // Fragment directories produced by the workflow-fragment epic (#1671). A file
 // under one of these is a SECTION of its parent workflow, never an entry point:
-// it is reached by a `read and execute gsd-core/workflows/<path>` stub, which
+// it is reached by a `read and execute msd-core/workflows/<path>` stub, which
 // fires with the parent — and therefore the parent's response-language
 // directive — already loaded.
 //
@@ -336,7 +336,7 @@ function hasResponseLanguageCoverage(content, refRoot = REFERENCE_ROOT) {
 /**
  * How far a read/execute verb may sit from the fragment path it governs on the
  * same line. Sized from the widest shape the catalog actually emits —
- * ``read and execute `gsd-core/workflows/...` `` (14 characters between verb and
+ * ``read and execute `msd-core/workflows/...` `` (14 characters between verb and
  * path) — with room for a variant, and deliberately far short of a sentence, so
  * a verb belonging to a different clause cannot reach across and vouch for a
  * path it never dispatches.
@@ -359,7 +359,7 @@ const ENTRY_POINT_VERB_RE = new RegExp(`\\b(?:read|execute|run)\\b.{0,${ENTRY_PO
  * `<path>` ``, ``Read+execute `<path>` ``, ``Read `<path>` if <condition>``,
  * ``run `<path>` to <effect>`` (the spelling #1689's per-plan executor routing
  * introduced), and the same stub written with the path RELATIVE to the catalog
- * rather than rooted at `gsd-core/workflows/` (#3552's `branching_strategy:
+ * rather than rooted at `msd-core/workflows/` (#3552's `branching_strategy:
  * none` arm). A read/execute/run verb within `ENTRY_POINT_VERB_WINDOW`
  * characters ahead of the path on the SAME LINE covers all five.
  *
@@ -375,7 +375,7 @@ const ENTRY_POINT_VERB_RE = new RegExp(`\\b(?:read|execute|run)\\b.{0,${ENTRY_PO
  * accepted spellings and the rejected mention forms.
  *
  * SECOND LIMITATION, same class: a dispatch line may sit inside a
- * `<!-- gsd:section id="X" when="…" -->` guard, and nothing here checks that the
+ * `<!-- msd:section id="X" when="…" -->` guard, and nothing here checks that the
  * guard is satisfiable or that its `id` still matches the fragment it gates.
  * Every such pairing lines up today. If one drifts, the fragment becomes
  * unreachable while this function still calls it dispatched — an orphan the lint
@@ -388,7 +388,7 @@ function namesFragmentAsEntryPoint(parent, relative) {
   // #3552's `"none"` arm introduced the second one — `Read and execute
   // `execute-phase/steps/protected-branch.md`` — and a rooted-only needle read
   // that live dispatch as no dispatch at all.
-  const needles = [`gsd-core/workflows/${relative}`, relative];
+  const needles = [`msd-core/workflows/${relative}`, relative];
   return parent.split(/\r?\n/).some((line) => needles.some((needle) => {
     const at = line.indexOf(needle);
     // A path character immediately before the match means this is the TAIL of