ci: align release workflows with platform runners and path filters

[aryasaatvik]

Summary

Align the release-tooling workflows with the platform repo, and fix a stale lockfile left by the 0.2.0 release.

• Move prepare-release, release-plan, and release-plan-comment onto blacksmith-2vcpu-ubuntu-2404, matching the platform.
• Gate release-plan on the releaseable paths (.tegami/**, root package.json, bun.lock, the tegami scripts, and the two published packages), add the per-PR concurrency group, and trigger on ready_for_review instead of every synchronize.
• Leave publish.yml on ubuntu-latest, matching the platform (publishing stays on GitHub-hosted runners).
• Sync bun.lock workspace versions for packages/better-auth and packages/email-sdk from 0.1.1 to 0.2.0; the version-packages release bumped package.json but not the lock, so every fresh install rewrote it.

Related issue

None.

Verification

• bun run format:check — pass
• bun install --frozen-lockfile — no changes (lock now consistent)
• bun run release:packages:check — pass (2 reproducible Bun tarballs)
• bun run lint — 0 errors (9 pre-existing warnings, unrelated)
• All three edited workflow files parse as YAML; release-plan.yml diff against the platform is now only the repo-specific package list.

No source change, so build/typecheck/test are unaffected.

Checklist

• Conventional Commit title
• bun run build passes — not run (no source change)
• bun run typecheck passes — not run (no source change)
• bun run test passes — not run (no source change)
• bun run lint and bun run format:check pass
• Added or updated tests — n/a (workflow config)
• Updated the package/example README if behavior changed — n/a

[github-actions]

Tegami

This repository uses Tegami to manage releases. When your changes affect published packages, add a changelog file under .tegami/ before merging.

Create a changelog → · Changelog format

No changelogs yet

This PR has no pending changelog files. If your changes require a release, add a changelog before merging.

Run bun run tegami locally to create a changelog interactively.

_{Managed by Tegami.}

[greptile-apps]

Confidence Score: 4/5

The PR is not safe to merge until release plans are regenerated for release-relevant commits pushed after a pull request is opened.

Findings

1.  Release plans become stale ▶

Summary

This PR aligns release-related workflows with the Blacksmith runner, narrows release-plan execution to release-relevant paths, adds per-PR cancellation, and synchronizes local workspace versions in bun.lock.

• The lockfile version corrections preserve the existing dependency graph.
• The new path filters cover the current release-plan inputs.
• Removing the synchronize event prevents release plans from refreshing after subsequent PR commits.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A[PR opened, reopened, or marked ready] --> B{Release path changed?}
  B -->|Yes| C[Generate release-plan.md]
  C --> D[Upload release-plan artifact]
  D --> E[workflow_run completed]
  E --> F[Download artifact for run ID]
  F --> G[Post release-plan comment]
  B -->|No| H[Skip release plan]
  I[Later commit pushed to open PR] --> J[No synchronize trigger]
  J --> K[Existing plan remains stale]

Loading

_{Reviews (1) · Last reviewed commit: "fix(deps): sync published package versio..."}