chore(release): publish already-versioned 0.24.0

[ascorbic]

What does this PR do?

Removes two stray changesets so the next Release run publishes the already-versioned 0.24.0.

main is at 0.24.0 in every package.json and the 0.24.0 changelog is written, but 0.24.0 was never published to npm (latest published is 0.23.0, no emdash@0.24.0 tag exists). The release PR #1629 was merged while these two changesets had already raced onto main. The merge applied the 0.24.0 bumps but left the two changesets in place, so the post-merge Release run found pending changesets, prepared 0.24.1 (PR #1650), and skipped the 0.24.0 publish entirely.

With these two changesets removed, main has zero pending changesets. The Release run then makes changeset version a no-op and falls through to changeset publish, releasing the already-versioned 0.24.0 with full artifacts (npm + git tag + GitHub release + plugin tarballs) via the normal changesets/action path.

These changesets document #1646 and #1644, which belong in 0.24.1. They are restored in an immediate follow-up PR, which cuts 0.24.1 with their text and attribution intact. #1650 has been closed in favor of this recovery.

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, only deletes changeset files
• 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 — intentionally n/a: this PR removes changesets as a release-mechanics fix and does not change a published package
• 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]

⚠️ No Changeset found

Latest commit: 408c15d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[emdashbot]

This is a release-mechanics recovery PR: it removes two stray emdash patch changesets so that the next Release run finds zero pending changesets, makes changeset version a no-op, and proceeds to changeset publish for the already-bumped 0.24.0 packages.

I checked:

• The diff only deletes .changeset/fix-1347-taxonomy-parent-locale.md and .changeset/fresh-buckets-exercise.md; no source files are touched.
• After the deletion, .changeset/ contains only README.md and config.json — zero pending changesets.
• packages/core/package.json (and the fixed-package group, e.g. @emdash-cms/admin) is already at 0.24.0, and the 0.24.0 CHANGELOG entry is already written, confirming the version bump was applied previously.
• .github/workflows/release.yml + .github/scripts/release.mjs run changeset version then changeset publish via changesets/action; with no pending changesets, version is a no-op and publish will release the current 0.24.0 versions.

The approach is sound and matches the stated recovery plan. No AGENTS.md conventions are triggered by deleting release metadata files. LGTM.