TypeGlish 0.2.1: the playground ships to production

0.2.0 was the big one: agents in a single file, the conditional layer, typed $CONFIG, and the reference sigils that made @{} the one way to point at anything. 0.2.1 is the quiet release that follows a loud one. It ships two things, both about reach rather than language: the deploy config the browser playground needs to run in production, and the repo badges that link the code on GitHub to the package on npm. Nothing in the compiler surface changed, so if you are already on 0.2.0 your prompts check exactly as they did. Upgrade with npm i -D typeglish@latest or run it with no install at all: npx typeglish@latest check **/*.tg.

§1The playground ships to production

The playground is the fastest way to feel what TypeGlish does: paste a prompt, watch the same checker the CLI runs light up the lines it can prove wrong. 0.2.1 lands the production deploy config that makes that playground shippable, and it comes in three concrete pieces.

First, a sub-path base: the app now builds against a configurable base path, so it can be served under a route (say /app) instead of only at a domain root. Second, ES-module workers: the in-browser checker runs off the main thread, and those web workers now load as ES modules, which is what a modern production bundle needs to code-split and cache them cleanly. Third, a Vercel deploy setup, so the build lands on a real host with the routing and headers it expects. None of this is a language feature; all of it is the difference between a checker that runs on your laptop and one that runs in a tab.

Persona IS a customer support agent.

You MUST greet the customer by name before anything else.
You NEVER state a specific refund amount.

WHEN a refund is requested THEN escalate to a human agent.

§2The repo, linked to the package

The other change is documentation, and it earns its line in the changelog because it closes a trust gap. The README now carries three badges: the npm version, the CI status, and the license. Together they answer the three questions someone asks when they land on the GitHub repo cold: which version is actually published, is the build passing right now, and can I use this. A badge is a small thing, but it is the visible link from the code you are reading to the package you would install, and until 0.2.1 that link was implicit.

That is the whole release. Two changes, both about getting TypeGlish in front of more people with less friction, and zero surprises for anyone already writing .tg.