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:
@@ -26,7 +26,7 @@ enumeration reads as a closed list and the class is open (REQ-LANG-04).
|
||||
|
||||
| Form | What it looks like | When it applies |
|
||||
|---|---|---|
|
||||
| Shared reference | `@~/.claude/gsd-core/references/response-language-directive.md` on its own line | The file is loaded eagerly — a top-level workflow. Preferred: one place to maintain the wording for the 42 files that take it. |
|
||||
| Shared reference | `@~/.claude/msd-core/references/response-language-directive.md` on its own line | The file is loaded eagerly — a top-level workflow. Preferred: one place to maintain the wording for the 42 files that take it. |
|
||||
| Own inline directive | One line carrying the directive in the file's own words | The file already has one, or its prose needs local phrasing. Must pass all four predicates (below). |
|
||||
| Pinned inline directive | The canonical line, byte for byte | A lazily-loaded mode/step/template that **cannot prove inheritance**. |
|
||||
| Inherited | nothing in the file itself | A fragment whose parent workflow dispatches it from a read/execute context and is itself covered. |
|
||||
@@ -39,7 +39,7 @@ Answer in this order:
|
||||
is loaded, so this is the cheapest correct answer for a top-level workflow.
|
||||
2. **Is it a fragment under `<workflow>/{modes,steps,templates}/`?** Then check whether
|
||||
`<workflow>.md` dispatches this exact path from a read/execute context *and* is itself covered.
|
||||
The catalog writes that stub two ways — rooted at `gsd-core/workflows/`, or relative to the
|
||||
The catalog writes that stub two ways — rooted at `msd-core/workflows/`, or relative to the
|
||||
catalog — and either one counts; a path with no read/execute/run verb ahead of it on the same
|
||||
line is a mention, not a dispatch, and proves nothing.
|
||||
If both hold, the fragment **inherits** — add nothing. The parent's directive is already in the
|
||||
|
||||
Reference in New Issue
Block a user