Add feature flags to a project that already has (or is adding) bq-analytics, then operate them — flip on/off, change rollout %, manage allowlists, materialize cohorts from BigQuery, and evaluate flag impact. Backed by Vercel Edge Config; exposures auto-track to events.raw. Use when the user wants flags, says "add…
Install AND instrument bq-analytics in a project. Phase 1 detects the runtime and wires the SDK. Phase 2 scans the repo for auth / payment / key feature surfaces, suggests events, and instruments track/identify/group inline. Phase 3 (optional) provisions feature flags via Vercel Edge Config. Use when the user wants to…
Add release-time UX (force-update gate, post-update what's-new sheet, channel-aware store deeplinks) to a project that has bq-analytics, then operate it — draft release notes, flip the gate, push hard-blocks during incidents. Backed by Vercel Edge Config under the key release. Use when the user wants force-update /…
Add a new runtime guarantee, safety property, or feature to Blaze the theorem-with-test way — attacking concurrent test first, then implementation, then the README claims table. Use whenever the user asks to add, harden, or make safe any runtime behavior (limits, isolation, EditClass semantics, metrics, canary policy…
Run Blaze's benchmark suite (reload latency, call throughput, interpreter comparison, canary overhead) and update every performance number in the README honestly and machine-labeled. Use when the user asks about performance, "how fast is it", re-measuring, updating benchmark or README numbers, preparing…
Add a language feature to Blaze — a token, operator, statement, control-flow form, or type — through the full seven-station pipeline with the diagnostics gate kept in lockstep with the lowerer. Use whenever the user asks for new syntax or semantics ("add strings", "support for-loops", "a modulo operator", "explicit…