Released 2026-09-18 — AI layer, live pricing, team docs
Highlights
Workspace assistant — floating widget on every signed-in page, Conversation memory lives server-side in Postgres: the client sends only the question and the server's stored thread is the sole context — client-supplied is ignored, so a hand-edited request cannot inject turns.
Weekly digest AI paragraph — "This week in numbers", generated from the week's measured rows only, labeled AI-assisted, additive: empty weeks and all-providers-down render the email unchanged .
Live-DB pricing page — plans render per request from the database; price edits go live without a rebuild. Pay-directly CTAs while checkout is inert.
Public docs site — (how-to-use, scoring rules, brand, website handoff, security, changelog) built with a secret/ops scan gate and a never-public list; synced with previous- generation backup and public-HTTPS verification. Main-site footers link it.
Why-header audit — every tracked source file now opens with a why-header
AI layer (free tiers only, self-updating)
Workspace assistant
floating widget on every signed-in page, Conversation memory lives server-side in Postgres: the client sends only the question and the server's stored thread is the sole context — client-supplied is ignored, so a hand-edited request cannot inject turns.
Weekly digest AI paragraph
"This week in numbers", generated from the week's measured rows only, labeled AI-assisted, additive: empty weeks and all-providers-down render the email unchanged .
pricing & billing
Live-DB pricing page
plans render per request from the database; price edits go live without a rebuild. Pay-directly CTAs while checkout is inert.
documentation & team surface
Public docs site
(how-to-use, scoring rules, brand, website handoff, security, changelog) built with a secret/ops scan gate and a never-public list; synced with previous- generation backup and public-HTTPS verification. Main-site footers link it.
Why-header audit
every tracked source file now opens with a why-header
Improvements & fixes
basePath-less client fetches
Worker test suite hardening: the reaper probe takes its start date from the database clock (a host-local "yesterday" flaked across UTC offsets near midnight) and the sync test accepts both ROI skip markers . 9/9 worker tests pass.