chore: bump version to 0.1.121 - #298

Bumps the package version to 0.1.121. Merging this PR cuts release v0.1.121.

Also carries a ui/dist rebuild. 66d2cd8 (#297) changed ui/src without regenerating the committed bundle, which release builds embed verbatim via rust-embed (src/commands/up.rs:7559). Without the rebuild, v0.1.121 would have shipped #297's Rust telemetry and none of its UI half. Verified: all four new event strings are absent from the old bundle and present in the new one, with 0 string literals lost and the only additions being #297's telemetry tokens. CSS hash is unchanged, consistent with #297 touching no styles.

Releases everything since v0.1.120 (e791d30): #290, #294, #295, #296, #297.

Pre-merge checks

• Confirm production ingests OR-269 feat: emit onboarding, demo, starter and first-action telemetry #297's four new events (onboarding_step_viewed, demo_experiment_started, project_starter_clicked, first_action) before merging. OR-269 feat: emit onboarding, demo, starter and first-action telemetry #297 states it "requires the matching API contract to be deployed first", and this is the first build that ships those emitters. The production_contract_is_accepted publish gate (src/telemetry.rs:1918) does not cover them, so it will pass either way. If production 400s first_action, each install permanently burns its one-per-surface slot on a dropped event (src/telemetry.rs:1074 claims the slot before capture(); a 400 is Rejected and never retried) — that data is not recoverable after the API is fixed.
• Hold other merges to main until the Release run publishes — release.yml tags github.sha (main's tip at dispatch), so anything merged in between ships inside v0.1.121.
• Confirm RELEASE_DISPATCH_TOKEN is valid if the macOS DMG should auto-attach.
• Smoke-test the dashboard from a release build (the rebuilt bundle is not exercised by CI).

Verified locally

• cargo fmt --all --check
• cargo clippy --all-targets -- -D warnings
• cargo build --locked
• cargo test --locked — 766 passed, 0 failed
• UI: check-i18n, paraglide-js compile, tsc --noEmit clean, vite build
• UI unit tests — 153 passed, 0 failed
• Version guard: 0.1.120 → 0.1.121 moves forward, Cargo.lock regenerated, v0.1.121 tag unclaimed

Follow-up (not in this PR)

CI type-checks the UI but never builds it, so nothing catches a stale ui/dist — that gap is what let #297 merge without its bundle. A step that rebuilds and fails on a dirty ui/dist would make the AGENTS.md rule enforceable.

🤖 Generated with Claude Code