msd-core/.changeset/archived/3577-docker-test-fixup.md at 837991d5a298695ee8c69b10d1fdb1d8e6b41084

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

1.7 KiB

Raw Blame History

type, pr

type	pr
Fixed	3577

Docker test fix-forward: 12 ubuntu-only regressions surfaced by gsd-test-summary cleared —

agents/gsd-intel-updater.md retargeted from gsd-sdk query intel.* to gsd-tools intel <subcommand> (intel is out-of-seam per ADR §3 / PRD L160; the SDK has no handler for it, so the agent's CLI calls were broken).
roadmap.get-phase two-pass lookup for project-code-prefixed IDs (port of CJS phaseMarkdownRegexSourceExact, #3599): a PROJ-42 query now matches ### Phase PROJ-42: directly without cross-matching a bare ### Phase 42: that happens to share the trailing integer.
roadmap.analyze extracts the **Mode:** field per phase (parity with roadmap.get-phase).
phase.remove depth-aware end-of-section regex (port of CJS #3601 fix): removing ### Phase 2: stops at ### Phase 2.1: (peer-depth decimal preserved) but continues past #### Phase 27.1: (child-depth decimal of ### Phase 27:). Named capture (?<h>#{2,4}) + backreference \k<h>(?!#) enforces same-depth termination.
phase.remove slugged-plan reference renumbering (port of CJS #3602 fix): the padded-plan-reference pattern now allows arbitrary kebab-case slug segments between NN-NN and the -PLAN.md / -SUMMARY.md suffix, so references like 07-01-cherry-pick-foundation-PLAN.md get renumbered to 06-01-… when Phase 7 is removed.
configNewProject filters out manifest keys that legacy CJS init does not materialize (git.base_branch, resolve_model_ids, context_window, mode, planning, graphify): these have their own resolution paths (auto-detect, opt-in) and materializing manifest values would suppress them. config-get git.base_branch correctly returns "Key not found" so workflows can fall back to origin/HEAD resolution.

1.7 KiB Raw Blame History

1.7 KiB

Raw Blame History