golem15/msd-core
4
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

refactor: hard-fork GSD -> MSD (Make Software Done)

Browse Source 
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
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/adr/2008-command-exit-zero-gate.md
View File

@@ -17,7 +17,7 @@ and the loop-resolver (`loop-resolver.cts:renderLoopHooks`) renders all active
gates to the workflow gate-dispatch sites.
Prior to this ADR, only `check.query` was **enforced**: every workflow
gate-dispatch site ran `gsd_run check ${hook.check.query}`, which routes through
gate-dispatch site ran `msd_run check ${hook.check.query}`, which routes through
the fixed if-chain in `check-command-router.cts:routeCheckCommand`. A
`check.predicate` (e.g. the `security` capability's
`artifact-frontmatter-equals` declaration) was **declaration-only** — rendered
@@ -88,14 +88,14 @@ A capability declares a `command-exit-zero` gate under the existing
so it is trivially unit-testable without spawning. A `KIND_TABLE` dispatches
by `predicate.kind`; adding a future kind is a one-line registration.
- `check-command-router.cts` gains a `predicate` subcommand
(`gsd_run check predicate --predicate '<json>' [--phase-dir …] [--phase-number …]
(`msd_run check predicate --predicate '<json>' [--phase-dir …] [--phase-number …]
[--phase-req-ids …] --raw`). It parses flags, builds the production deps
(wrapping `execTool`), calls `evaluatePredicate`, and emits the standard
`{ block, message, details? }` envelope via `output()`.
- The three generic workflow gate-dispatch sites — `execute:wave:post`,
`execute:post`, `plan:post` — now branch on the gate's `check` shape:
`check.query` → existing `gsd_run check <query>` path; `check.predicate` →
`gsd_run check predicate`. The two-step Step-1 (command-failure → `onError`)
`check.query` → existing `msd_run check <query>` path; `check.predicate` →
`msd_run check predicate`. The two-step Step-1 (command-failure → `onError`)
/ Step-2 (`block` → halt) contract is **unchanged** — the predicate path
emits the same envelope and the same check-command-failure semantics.