Ben Stull
72f8457933
Wave 5 / Track A. Roadmap item #13. Folds in #21 Part C user-identity- lifecycle work inline rather than as a follow-up release (operator ask: "implement Amplitude best practices from the very get-go"). Wraps @amplitude/unified with: - consent-gated lazy init (v0.13.0 cookie banner; SDK never loads without explicit analytics opt-in) - amplitude.initAll(KEY, { analytics: { autocapture: true }, sessionReplay: { sampleRate: 1 } }) — vendor-recommended shape - identify({ user_id, properties? }) with set vs setOnce semantics - setUserProperties(properties) for mid-session state changes - anonymize() clears both user_id binding AND property cache Wired into App.jsx (identify on me.user with role / permission_state / passcode_set / device_trusted as set; first_sign_in_at / account_created_at as setOnce; Page Viewed on route change; Sign-out fires User Signed Out + anonymize), Login.jsx (User Signed In + Beta Access Requested), and the per-feature surfaces (ProposeModal, PRModal, RFCView, RFCDiscussionPanel, PRView, Admin). Binding: VITE_AMPLITUDE_API_KEY via `flotilla overlay set` (bundle-embedded public key like VITE_TURNSTILE_SITE_KEY — not secret). Mid-Session-L correction: original dispatch brief specified secret-set; vendor guidance + bundle visibility settled it as overlay. PII discipline: no email, no display_name, no gitea_login, no free-text fields ever sent. Properties are opaque ids + enums + timestamps + booleans only. Subagent ξ shipped the wrapper structure + nine-event taxonomy on feature/v0.15.0-amplitude (0fd8c52+6cfbf69post-correction). Driver-side integration extended the wrapper with setUserProperties + identify properties for the #21 Part C identity-lifecycle work. Frontend build verified green. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
88 lines
4.0 KiB
Bash
88 lines
4.0 KiB
Bash
# Frontend build-time configuration. Copy to `frontend/.env` and fill in.
|
|
#
|
|
# Vite picks up VITE_* variables from these files at build (`npm run build`)
|
|
# and dev (`npm run dev`) time. Real `.env` files are gitignored; only this
|
|
# `.env.example` is committed.
|
|
|
|
# The user-visible name of this deployment. Used as the browser tab title,
|
|
# the header brand, and the landing page H1. Required — the framework
|
|
# ships no default on purpose so each deployment names itself. If unset,
|
|
# `npm run build` fails with a clear message.
|
|
#
|
|
# Examples:
|
|
# VITE_APP_NAME=Wiggleverse RFC
|
|
# VITE_APP_NAME=Wiggleverse Open Human Model
|
|
VITE_APP_NAME=
|
|
|
|
# Optional contact line shown on the /beta-pending page when a deployment
|
|
# is in private-beta mode (i.e. the backend's `allowed_emails` table has
|
|
# rows). Free-text — an email address, a URL, or a one-line instruction
|
|
# tells visitors how to request an invitation. If unset, the page falls
|
|
# back to a generic "contact the deployment operator" line.
|
|
#
|
|
# Examples:
|
|
# VITE_BETA_CONTACT=ben@wiggleverse.org
|
|
# VITE_BETA_CONTACT=DM @ben on Matrix
|
|
VITE_BETA_CONTACT=
|
|
|
|
# Optional URL to the deployment's privacy policy (v0.13.0+, SPEC §14.5).
|
|
# The framework ships a minimal default privacy policy at `/privacy`
|
|
# that describes the framework's stance and lists the cookies the
|
|
# framework sets. When this var is set to an http(s) URL, the page
|
|
# renders the framework's stub above a link to the configured URL —
|
|
# deployments use this to layer their own policy content on top
|
|
# without forking the framework. Unset is OK; the stub is sufficient
|
|
# for a deployment that has nothing specific to add.
|
|
#
|
|
# Examples:
|
|
# VITE_PRIVACY_POLICY_URL=https://wiggleverse.org/privacy
|
|
VITE_PRIVACY_POLICY_URL=
|
|
|
|
# Optional URL to the deployment's cookies policy (v0.13.0+, SPEC §14.6).
|
|
# Same shape as VITE_PRIVACY_POLICY_URL. The framework's default
|
|
# `/cookies` page lists exactly which cookies the framework sets
|
|
# (rfc_session, the consent-choice localStorage entry); a deployment
|
|
# that adds its own cookies (analytics SDK once #13 lands, third-party
|
|
# embeds) points this var at a page that documents the full list.
|
|
# Unset is OK; the stub is sufficient for a default-config deployment.
|
|
#
|
|
# Examples:
|
|
# VITE_COOKIES_POLICY_URL=https://wiggleverse.org/cookies
|
|
VITE_COOKIES_POLICY_URL=
|
|
|
|
# v0.12.0 / roadmap item #10: CloudFlare Turnstile site key (public).
|
|
# Provision a Turnstile site at dash.cloudflare.com → Turnstile → Add
|
|
# site. The site key (this var) is embedded into the frontend bundle at
|
|
# build time and rendered by the Turnstile widget on the /login email-
|
|
# entry step. The secret key (private) lives in the backend env as
|
|
# CLOUDFLARE_TURNSTILE_SECRET — see backend/.env.example. Leave unset
|
|
# in dev to skip the widget; the backend's TURNSTILE_REQUIRED policy
|
|
# decides what happens to a tokenless request.
|
|
#
|
|
# Examples:
|
|
# VITE_TURNSTILE_SITE_KEY=0x4AAAAAAA...
|
|
VITE_TURNSTILE_SITE_KEY=
|
|
|
|
# v0.15.0 / roadmap item #13: Amplitude project API key (public).
|
|
# Embedded in the frontend bundle at build time and used by the
|
|
# analytics wrapper (`frontend/src/lib/analytics.js`) — which loads
|
|
# `@amplitude/unified` (Analytics + Session Replay) when the user
|
|
# has granted analytics consent (v0.13.0 cookie banner). Provision
|
|
# an Amplitude project at app.amplitude.com → Projects → New, copy
|
|
# the API key.
|
|
#
|
|
# Public by design: Amplitude browser keys are bundle-embedded
|
|
# (visible in dev tools), same nature as VITE_TURNSTILE_SITE_KEY
|
|
# (also public; the truly-secret half of that Turnstile pair is
|
|
# CLOUDFLARE_TURNSTILE_SECRET on the backend). For deployments
|
|
# behind flotilla, bind via `flotilla overlay set <deployment>
|
|
# VITE_AMPLITUDE_API_KEY=<key>` — NOT `flotilla secret set`. The
|
|
# vendor's installation wizard shows the key inline as a literal
|
|
# string in the init call, confirming the public framing. Leave
|
|
# unset in dev; the wrapper logs one console warning and no-ops
|
|
# (the app continues to work).
|
|
#
|
|
# Examples:
|
|
# VITE_AMPLITUDE_API_KEY=01234567890abcdef01234567890abcd
|
|
VITE_AMPLITUDE_API_KEY=
|