golem15/msd-core
4
0
Fork 0
Code Issues 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

20
docs/agents/issue-tracker.md
View File

@@ -1,6 +1,6 @@
# Issue tracker: GitHub
Issues for this repo live in **GitHub Issues** at `open-gsd/gsd-core`.
Issues for this repo live in **GitHub Issues** at `golem15com/msd-core`.
## Auth
@@ -9,19 +9,19 @@ repo-local `.envrc` before running `gh`.
## Conventions
- **Create**: `gh issue create --repo open-gsd/gsd-core --title "..." --body "..."`
- **Read**: `gh issue view <number> --repo open-gsd/gsd-core --comments`
- **List**: `gh issue list --repo open-gsd/gsd-core --state open --json number,title,labels --jq '...'`
- **Comment**: `gh issue comment <number> --repo open-gsd/gsd-core --body "..."`
- **Label**: `gh issue edit <number> --repo open-gsd/gsd-core --add-label "..." --remove-label "..."`
- **Close**: `gh issue close <number> --repo open-gsd/gsd-core --comment "..."`
- **Create**: `gh issue create --repo golem15com/msd-core --title "..." --body "..."`
- **Read**: `gh issue view <number> --repo golem15com/msd-core --comments`
- **List**: `gh issue list --repo golem15com/msd-core --state open --json number,title,labels --jq '...'`
- **Comment**: `gh issue comment <number> --repo golem15com/msd-core --body "..."`
- **Label**: `gh issue edit <number> --repo golem15com/msd-core --add-label "..." --remove-label "..."`
- **Close**: `gh issue close <number> --repo golem15com/msd-core --comment "..."`
Always pass `--repo open-gsd/gsd-core` explicitly — the local clone has multiple remotes and `gh` may resolve to the wrong one.
Always pass `--repo golem15com/msd-core` explicitly — the local clone has multiple remotes and `gh` may resolve to the wrong one.
## When a skill says "publish to the issue tracker"
Create a GitHub issue at `open-gsd/gsd-core`.
Create a GitHub issue at `golem15com/msd-core`.
## When a skill says "fetch the relevant ticket"
Run `gh issue view <number> --repo open-gsd/gsd-core --comments`.
Run `gh issue view <number> --repo golem15com/msd-core --comments`.

8
docs/agents/triage-labels.md
View File

@@ -1,6 +1,6 @@
# Triage Labels
Maps the five canonical triage roles to the actual label strings in `open-gsd/gsd-core`.
Maps the five canonical triage roles to the actual label strings in `golem15com/msd-core`.
| Canonical role | Label in this repo | Notes |
|-------------------|--------------------------|----------------------------------------------------------------|
@@ -10,7 +10,7 @@ Maps the five canonical triage roles to the actual label strings in `open-gsd/gs
| `ready-for-human` | `approved-enhancement` / `approved-feature` | Enhancement/feature approved by maintainer — human codes it |
| `wontfix` | `wontfix` | Will not be actioned |
| `possible-duplicate` | `possible-duplicate` | Applied by the Duplicate check workflow when a new issue's title closely matches existing open issues. The reporter (or a maintainer) replies justifying why it is not a duplicate within 24h, or the Duplicate auto-close sweep closes it. A reply clears this label and applies needs-maintainer-review for human adjudication. React 👎 to the bot comment to veto auto-close. |
| `needs-version` | `needs-version` | Applied by the Version gate workflow when a bug report is auto-closed for missing a valid GSD Version. Edit the issue to add the version and reopen it. |
| `needs-version` | `needs-version` | Applied by the Version gate workflow when a bug report is auto-closed for missing a valid MSD Version. Edit the issue to add the version and reopen it. |
| `version-exempt` | `version-exempt` | Maintainer-only opt-out label. Prevents the Version gate from closing an issue where a version genuinely does not apply. |
## Notes on this repo's label model
@@ -34,8 +34,8 @@ The `possible-duplicate` label is managed by three GitHub Actions workflows that
The `needs-version` label is managed by a single GitHub Actions workflow that runs immediately on issue open:
1. **Gate on open** — When an issue is opened, `version-gate.yml` checks whether it is a bug report (has the `bug` label, or its body contains a `### GSD Version` heading from the bug template). Non-bug issues are skipped.
2. **Version check** — The gate extracts the value under the `### GSD Version` heading. A value is considered valid if it contains a semver-ish token (e.g. `1.18.0`, `v1.4.1`, `1.18.0-dev`) or a git commit SHA (7-40 hex chars). Missing, blank, `_No response_`, or junk values like `idk` are treated as absent.
1. **Gate on open** — When an issue is opened, `version-gate.yml` checks whether it is a bug report (has the `bug` label, or its body contains a `### MSD Version` heading from the bug template). Non-bug issues are skipped.
2. **Version check** — The gate extracts the value under the `### MSD Version` heading. A value is considered valid if it contains a semver-ish token (e.g. `1.18.0`, `v1.4.1`, `1.18.0-dev`) or a git commit SHA (7-40 hex chars). Missing, blank, `_No response_`, or junk values like `idk` are treated as absent.
3. **Auto-close** — If the version is absent or invalid, the workflow posts a comment with instructions and closes the issue as `not_planned`, then applies `needs-version`.
4. **Reopen path** — The reporter edits the issue to add a valid version and reopens it. Alternatively, a maintainer can add the `version-exempt` label to any bug where a version does not apply (e.g. docs bugs, spec questions), which prevents the gate from closing it on future edits.