fix(release): prevent incompatible React core artifacts (#51)

## Summary

Prevent `@domainkit/react` from publishing against an incompatible
DomainKit core range, and make the release gate inspect the same
Bun-produced tarball Tegami publishes.

## Release invariant

```text
workspace:^ remains the source declaration
  -> Tegami applies coordinated versions
  -> post-version bun install refreshes workspace versions in bun.lock
  -> bun pm pack resolves the workspace protocol
  -> inspect packed package.json
  -> require packed domainkit range to contain the current core version
  -> npm publish <tarball>
```

The source manifest remains workspace-native. The Tegami post-version
hook prevents a stale Bun lockfile from producing an outdated dependency
range, and CI plus the publish preflight validate the final packed
manifest.

## Validation

- `bun run release:check`
- Packed Vite consumer on React 19
- Packed Next.js consumer on React 19
- Packed React manifest compatibility assertion
- Seven Playwright browser scenarios