msd-core/.changeset/archived/3571-configuration-manifest-install-layout.md at 9e2ef2c94dea3f1267deba570c9a423fb38c2f85

Files

Tom Boucher 8616839cab chore: archive 463 shipped changeset fragments before wiring render (#714 )

CHANGELOG promotion was a manual operator step that was never run, so 463
fragments for work already shipped in <=1.3.1 accumulated in .changeset/.
Their notes were already hand-curated into the dated [1.2.0]/[1.3.0]/[1.3.1]
CHANGELOG sections (#690 backfill, PR #694). Rendering them now would
duplicate and mis-attribute shipped work.

Move them to .changeset/archived/ (read non-recursively by all changeset
tooling, so never rendered), keeping only the 3 genuinely-unreleased
fragments at the top level. Prep for wiring `render` into the release
finalize job (#690 follow-up).

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-05 14:53:17 -04:00

500 B

Raw Blame History

type, pr

type	pr
Fixed	3572

Installed gsd-tools.cjs can load generated configuration manifests — runtime installs now copy config-defaults.manifest.json and config-schema.manifest.json into get-shit-done/bin/shared/, and configuration.generated.cjs resolves that co-located install path before falling back to the source checkout sdk/shared/ path. This prevents direct installed CJS invocations from failing with MODULE_NOT_FOUND when no sibling sdk/ checkout exists. (#3571)

500 B Raw Blame History

500 B

Raw Blame History