v0.3.0 — eject ships (experimental), with an honest exit report

New (experimental)

tabula eject now ships as an experimental feature — the one-way freeze and the new reverse-map analysis. The command works and is fully tested, but its surface (flags, report format, tier table) may change in a future minor release; feedback via issues is welcome.

• tabula eject — freeze a verified .tabula/ into a project-owned directory that compiles on stock @tailwindcss/cli with zero class changes. Dry-run by default; fail-closed integrity preconditions; EJECTED.md provenance with the cn() keep-merge policy and exception-expiry table; --write-imports.
• tabula eject --report (new) — an honest answer to "what would leaving Tabula for vanilla Tailwind actually take?": classifies every class your source uses into tiers A (portable as-is) / B (provably-1:1 rename — the only thing --write touches) / C (mechanical but rendering changes, with the exact caveat) / D (no vanilla equivalent). --theme-port shows the scenario where --tb-* namespaces are ported to vanilla ones. On the reference app: 18.9% portable as-is, 62.2% with a theme port — freezing keeps rendering exact, and the report says so.

Docs

Eject guide updated with the experimental status and the full --report tier reference — in English, 한국어, 日本語, 简体中文.

All 10 packages published in lockstep at 0.3.0 with npm provenance. No registry schema change (still v3); v0.2.x projects need no rebuild.