chore: prepare v3.0.0 stable release

[olliethedev]

Summary

• promote @btst/stack from 3.0.0-rc.4 to 3.0.0
• promote @btst/codegen from 0.2.0-rc.4 to 0.2.0
• pin generated installs to exact @btst/stack@3.0.0 and public @btst/better-auth-ui@2.0.0
• update release-cohort docs and commands from candidate/@next references to exact stable versions
• preserve the historical RC2/RC3 compatibility fixtures and evidence

The workspace lockfile is unchanged because these workspace package versions are represented by links, not embedded package-version entries.

Local release gates

All commands used Node v22.23.2 and pnpm 10.17.1.

• corepack pnpm@10.17.1 install --frozen-lockfile --strict-peer-dependencies
• corepack pnpm@10.17.1 build
• corepack pnpm@10.17.1 typecheck
• corepack pnpm@10.17.1 lint
• corepack pnpm@10.17.1 test — Stack: 87 files / 1,043 tests; Codegen: 11 files / 170 tests
• corepack pnpm@10.17.1 --dir docs build
• release metadata assertion — Stack 3.0.0, Codegen 0.2.0, tag v3.0.0, dist-tag latest
• npm pack --dry-run --json for both packages — btst-stack-3.0.0.tgz, btst-codegen-0.2.0.tgz
• corepack pnpm@10.17.1 test:packed-consumers — 8/8 harness tests
• packed core consumer: npm and strict pnpm typecheck/build
• packed auth consumer: npm and strict pnpm typecheck/build against public @btst/better-auth-ui@2.0.0
• auth graph in both consumers: Better Auth/Core/API-key/passkey 1.6.16, Utils 0.4.1, Fetch 1.2.2, Call 1.3.6, DB 2.2.3
• corepack pnpm@10.17.1 --filter @btst/codegen test:better-auth-ui-fixtures — untouched Next.js, React Router, and TanStack apps all built and typechecked
• corepack pnpm@10.17.1 --filter @btst/stack build-registry — no generated diff
• corepack pnpm@10.17.1 --filter @btst/stack test-registry — clean Next.js npm install and production build passed
• audit found no live RC4 or BTST @next references; only historical RC2 fixtures remain

Public companion metadata was verified before this change: @btst/better-auth-ui@2.0.0 is latest with npm integrity, shasum, and gitHead metadata.

Independent review

• Standards: no documented-standard violations; one non-blocking possible Shotgun Surgery judgement call for deliberate synchronized explicit release pins
• Spec: no findings; complete alignment, no scope creep, historical evidence preserved

The PR-triggered Codegen E2E workflow provides the final Playwright/browser matrix for all three frameworks.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

2 Skipped Deployments

Project	Deployment	Actions	Updated
better-stack-docs	Ignored		Sep 1, 2026 12:49am UTC
better-stack-playground	Ignored		Sep 1, 2026 12:49am UTC

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-01T00:53:29.051543Z	bfb1fe0	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[github-actions]

✅ Shadcn registry validated — no registry changes detected.

[olliethedev]

Final release-candidate CI is fully green at bfb1fe0adfa10a427822ece7681111a7f6b5ce85:

• CI: https://github.com/better-stack-ai/better-stack/actions/runs/33456308391
• packed npm/pnpm core + auth consumers: https://github.com/better-stack-ai/better-stack/actions/runs/33456308331
• init smoke + all-framework Better Auth UI packed fixtures: https://github.com/better-stack-ai/better-stack/actions/runs/33456308539
• Next.js, React Router, and TanStack Playwright E2E: https://github.com/better-stack-ai/better-stack/actions/runs/33456308524
• shadcn registry clean-room install/build: https://github.com/better-stack-ai/better-stack/actions/runs/33456308390

Both Vercel status checks also concluded successfully via their configured ignored-build step. No generated registry diff was produced.