[msmps]

Pushing a tag like v0.0.12 runs release.yml:

1. verify the tag matches packages/cli/package.json,
2. run the full CI workflow (now reusable via workflow_call),
3. build and publish packages/cli/dist to npm, using OIDC trusted
   publishing (no stored npm token; provenance is attached automatically),
4. create a GitHub release with generated notes.

Prerelease tags (v0.1.0-beta.1) publish to the next dist-tag. Releases were
previously published by hand from packages/cli/dist; the README documents
the new flow and the one-time trusted publisher setup on npmjs.com.

Before the first release: enable trusted publishing on npmjs.com (create-tui → Settings → Trusted publishing → GitHub Actions, repo msmps/create-tui, workflow release.yml).

---

Stack

Merge bottom-up into main: merge #100 first, then each PR above it (GitHub retargets the next one to main).

• 👉 ci: publish releases from version tags with npm trusted publishing #107 ci: publish releases from version tags with npm trusted publishing
• chore: upgrade to TypeScript 7 with Effect diagnostics via @effect/tsgo #106 chore: upgrade to TypeScript 7 with Effect diagnostics via @effect/tsgo
• chore: tighten repository settings and add CI #105 chore: tighten repository settings and add CI
• refactor: address review concerns in the CLI package #104 refactor: address review concerns in the CLI package
• fix: report the real cause of failures instead of hiding it #103 fix: report the real cause of failures instead of hiding it
• fix: keep the project folder inside the current directory #102 fix: keep the project folder inside the current directory
• chore: migrate CLI to Effect v4 #101 chore: migrate CLI to Effect v4
• chore: migrate development tooling to Vite+ #100 chore: migrate development tooling to Vite+
• main