Files
msd-core/.changeset/archived/3610-codex-install-bundled-hooks-blocker.md
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

678 B

type, issue
type issue
Fixed 3610

Fresh npx get-shit-done-cc@latest --codex no longer hard-aborts when leftover bundled hooks/gsd-* files are present — classifyPromptUserAction in installer-migration-report.cjs now recognizes the bundled GSD hooks (hooks/gsd-<name>.{js,sh,cjs,mjs}) as a known category (bundled-gsd-hook) and resolves them to remove so the installer can write the fresh bundled versions. The classifier-based safe-default resolver in bin/install.js now runs regardless of TTY state — gating it on !isTTY made interactive installs throw installer migration blocked pending user choice for files that have no actual user choice to make.