Spaces:
Running
Running
Commit History
-
Deploy feature/golden-demo-v3 (2b65dd2826ea97ea4be1a6eb8984b9396d95af83) to the test app Space as one commit
Squashed onto hf-test/main because HF's pre-receive hook rejects binary blobs anywhere in pushed history, and the feature branch's history carries two PNGs (stripped from its tree in 2b65dd2826ea97ea4be1a6eb8984b9396d95af83). This commit's tree == the feature branch tree. Contents: golden demo v3 — 4-KPI standard w/ sparklines, state GEO_AREA, three tabs (Showcase = Muze + GRID_TABLE + heatmap + Demo Guide), blank-tile repair, humanized titles fix, grain enforcement, lab live-verification. See sprint_2026_04.md and dev_notes/DECISIONS_for_boone_2026_09_02.md. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>f7377ae
-
fix(scripts): stop printing trusted-auth keys; correct required var list
Two bugs in the secrets setup script. 1. It printed secret VALUES. TS_ENV_<n>_KEY_VAR normally holds the trusted-auth key itself, and the script's "points at X which is not in .env" warning echoed that key to stdout. Values are never printed now. Root cause: it assumed KEY_VAR was always a variable NAME. Per _ts_env_table() in mcp_server.py, only an "ENV:<NAME>" value is an indirection; anything else is the literal key. The check now mirrors the server. 2. The required-variable list came from README.md, which is stale. It listed MCP_OWNER_EMAIL and MCP_TS_ENV_LABEL — the server reads neither (MCP_OWNER_EMAIL appears only in tests/e2e_mcp.py, MCP_TS_ENV_LABEL only in the README). Replaced with what mcp_server.py actually reads, verified by grep: MCP_ACCESS_TOKEN, SUPABASE_URL, SUPABASE_ANON_KEY, TS_ENV_URL_DEFAULT, TS_USER_DEFAULT, plus the TS_ENV_<n> triplets. LLM key is now "at least one of ANTHROPIC/OPENAI" rather than requiring OpenAI. README.m…d733302 -
chore(scripts): add scripts/ for operational tooling
Moves whats_deployed.py and setup_test_mcp_secrets.py out of scratch/ (which is gitignored and defined as disposable) into a tracked scripts/ dir. Both are standing operational tools, not throwaways — whats_deployed.py is meant to run at the start of every session. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>ae9ba39