a9a7a328e6
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.
1.2 KiB
1.2 KiB
id, title, group
| id | title | group |
|---|---|---|
| 49 | Forensics | v1.28 Features |
Command: /msd-forensics [description]
Purpose: Post-mortem investigation of failed or stuck MSD workflows.
Requirements:
- REQ-FORENSICS-01: System MUST analyze git history for anomalies (stuck loops, long gaps, repeated commits)
- REQ-FORENSICS-02: System MUST check artifact integrity (completed phases have expected files)
- REQ-FORENSICS-03: System MUST generate a markdown report saved to
.planning/forensics/ - REQ-FORENSICS-04: System MUST offer to create a GitHub issue with findings
- REQ-FORENSICS-05: System MUST NOT modify project files (read-only investigation)
Produces:
| Artifact | Description |
|---|---|
.planning/forensics/report-{timestamp}.md |
Post-mortem investigation report |
Process:
- Scan — Analyze git history for anomalies: stuck loops, long gaps between commits, repeated identical commits
- Integrity Check — Verify completed phases have expected artifact files
- Report — Generate markdown report with findings, saved to
.planning/forensics/ - Issue — Offer to create a GitHub issue with findings for team visibility