chore(release): restore #1646/#1644 changesets for 0.24.1

[ascorbic]

What does this PR do?

Restores the two changesets that #1651 temporarily removed to publish the already-versioned 0.24.0 (now live on npm + tag + GitHub release).

With 0.24.0 published, these two fixes belong in 0.24.1. Merging this PR makes the next Release run open a fresh ci: release PR for 0.24.1; merging that publishes 0.24.1.

Each changeset carries pinned @changesets/changelog-github magic lines so the generated changelog credits the original PRs and authors, not this release PR:

• fix-1347-taxonomy-parent-locale.md -> pr: 1646, author: mvanhorn, commit: c962929…
• fresh-buckets-exercise.md -> pr: 1644, author: masonjames, commit: d64c961…

Without the override, changelog-github falls back to the commit that re-added the files (this PR), which would strip @mvanhorn's and @masonjames's credit. The magic lines are parsed and removed from the rendered summary, reproducing the exact line the now-closed #1650 generated.

No published-package source changes; this only touches .changeset/ release metadata.

Closes #

Type of change

• Chore (dependencies, CI, tooling)

Checklist

• I have read CONTRIBUTING.md
• pnpm typecheck passes — n/a, no source change
• pnpm lint passes — n/a, no source change
• pnpm test passes (or targeted tests for my change) — n/a, no source change
• pnpm format has been run — n/a, changeset metadata only
• I have added/updated tests for my changes (if applicable) — n/a
• User-visible strings wrapped for translation — n/a
• I have added a changeset — restores the two changesets for the 0.24.1 release
• New features link to an approved Discussion — n/a, not a feature

AI-generated code disclosure

• This PR includes AI-generated code — model/tool: Claude Opus 4.8 (OpenCode)

Screenshots / test output

n/a — release metadata only.

[changeset-bot]

🦋 Changeset detected

Latest commit: dd7f694

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 16 packages

Name	Type
emdash	Patch
@emdash-cms/cloudflare	Patch
@emdash-cms/sandbox-workerd	Patch
@emdash-cms/fixture-perf-site	Patch
@emdash-cms/perf-demo-site	Patch
@emdash-cms/cache-demo-site	Patch
@emdash-cms/do-demo-site	Patch
@emdash-cms/do-solo-demo-site	Patch
@emdash-cms/admin	Patch
@emdash-cms/auth	Patch
@emdash-cms/blocks	Patch
@emdash-cms/gutenberg-to-portable-text	Patch
@emdash-cms/x402	Patch
create-emdash	Patch
@emdash-cms/auth-atproto	Patch
@emdash-cms/plugin-embeds	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[emdashbot]

This is the right change for the right moment: after 0.24.0 shipped, the changesets for the two bug-fix PRs that missed the release need to be back on main so the next Release run opens a clean ci: release PR for 0.24.1.

I checked:

• The diff is limited to two .changeset/*.md files, and .changeset/config.json still lists the full emdash package family in one fixed group, so these patch-level changesets will correctly propagate to all published packages.
• The code each changeset describes is already present in the tree:
  • Taxonomy parent/locale fix: migration 045_taxonomy_parent_group.ts is registered in runner.ts and rewrites taxonomies.parent_id to the parent's translation_group.
  • React 19 dev-warning fix: packages/core/src/astro/integration/shims/use-sync-external-store*.js plus the Vite aliases in vite-config.ts redirect the CJS use-sync-external-store/shim entry points to ESM shims around React's built-in hook.
• Both summaries lead with a present-tense verb and focus on observable user impact (lost parent in translations, dev-console warnings), matching the changeset guidance in AGENTS.md/CONTRIBUTING.md.
• The pr:, commit:, and author: magic lines pin the generated changelog credit to the original PRs/authors rather than this release PR.

I couldn't execute pnpm changeset status or the release tooling here, so I didn't verify the exact rendered changelog line statically; no source change is required for that. No blocking issues found — this is a clean release-metadata restore.