golem15/msd-core
4
0
Fork 0
Code Issues 1 Pull Requests Actions 2 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

22
docs/CANARY.md
View File

@@ -1,10 +1,10 @@
# Canary Stream
The **canary** dist-tag is GSD's earliest preview channel. It exists so contributors and willing early adopters can exercise in-flight features against the long-lived `dev` integration branch before they have any expectation of stability.
The **canary** dist-tag is MSD's earliest preview channel. It exists so contributors and willing early adopters can exercise in-flight features against the long-lived `dev` integration branch before they have any expectation of stability.
## Stream policy
GSD ships through three npm dist-tags, each fed by exactly one git branch. **Streams do not mix.**
MSD ships through three npm dist-tags, each fed by exactly one git branch. **Streams do not mix.**
| Branch | dist-tag | Audience | Stability |
|---|---|---|---|
@@ -20,16 +20,16 @@ A canary build NEVER becomes a `next` build directly, and a `next` build NEVER b
```bash
# One-off invocation (npx)
npx @opengsd/gsd-core@canary
npx @golem15/msd-core@canary
# Pin to the canary dist-tag globally
npm install -g @opengsd/gsd-core@canary
npm install -g @golem15/msd-core@canary
# Pin to an exact canary version
npm install -g @opengsd/gsd-core@1.50.0-canary.1
npm install -g @golem15/msd-core@1.50.0-canary.1
```
The CC installer's defensive purge rewrites stale config blocks left by older GSD versions, so reinstalling on top of an existing project is safe.
The CC installer's defensive purge rewrites stale config blocks left by older MSD versions, so reinstalling on top of an existing project is safe.
## When to install canary
@@ -40,24 +40,24 @@ The CC installer's defensive purge rewrites stale config blocks left by older GS
❌ **Do NOT** install canary on:
- Production projects you depend on for delivery
- A machine where rolling back means recreating GSD state (use a profile or a workspace instead)
- A machine where rolling back means recreating MSD state (use a profile or a workspace instead)
- A demo or onboarding setup — pin to `@latest` so audiences see the stable surface
## Rolling back from canary
```bash
# Back to the current stable
npm install -g @opengsd/gsd-core@latest
npm install -g @golem15/msd-core@latest
# Or to the next/RC train
npm install -g @opengsd/gsd-core@next
npm install -g @golem15/msd-core@next
```
If you have a local project that interacted with canary-only features (for instance, an MVP-mode phase planned by 1.50.0-canary), the planner artifacts in `.planning/` remain valid — older GSD versions will just ignore the `**Mode:** mvp` field on phases.
If you have a local project that interacted with canary-only features (for instance, an MVP-mode phase planned by 1.50.0-canary), the planner artifacts in `.planning/` remain valid — older MSD versions will just ignore the `**Mode:** mvp` field on phases.
## Reporting issues against canary
File against the [issue tracker](https://github.com/open-gsd/gsd-core/issues) with the `bug` template. Include the exact canary version (`gsd-core --version` reports it) so triage can route the report back into the `dev` stream rather than the stable stream.
File against the [issue tracker](https://github.com/open-gsd/gsd-core/issues) with the `bug` template. Include the exact canary version (`msd-core --version` reports it) so triage can route the report back into the `dev` stream rather than the stable stream.
## Where to look next