msd-core/.changeset/archived/178-trace-id-propagation.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

510 B

Raw Blame History

type, pr

type	pr
Added	178

DispatchEvent now propagates parentTraceId (#178) — every DispatchEvent already carries a traceId (P1.3). Hub.dispatch(req) now accepts an optional req.parentTraceId; when present, it appears on the emitted event. This is the seam through which a future init-composer (Phase 2) will correlate child dispatches with their parent. Backward compatible — leaf dispatches that don't set parentTraceId emit events with parentTraceId: undefined exactly as in P1.3.

510 B Raw Blame History

510 B

Raw Blame History