Changelog

What shipped

Dated, in the order it happened. Every entry below is a change that reached production — there are no roadmap items on this page and no "coming soon". A solo-built product has one honest way to show it is alive, and this is it.

Last updated: August 6, 2026

August 6, 2026

  • Every public bot now has its own address. A bot's profile lives at /b/<slug> with its own title, description, social card and structured data, and appears in the sitemap. The old /b/?bot=<slug> links redirect permanently, so nothing that was shared before stops working.
  • A sitemap that keeps up. It is generated per request, so a bot you make public is listed the same day instead of at the next deploy. Unlisted, invite-only and private bots are never listed.
  • A shorter header on phones. The marketing header was three rows and 151 px tall at 390 px, pushing the page's first heading a third of the way down the screen. It is one 61 px row now; sign-in, the theme toggle and account links moved into the menu.
  • A topic index on Help. All 22 questions are listed alongside the page on a wide screen, and the list follows whichever intent filter is active.
  • Printing and previews work. Sections that animate in as you scroll no longer come out blank in a print, a PDF or a page-preview screenshot.
  • About and Contact are linked from the home page, which was the one page on the site that did not offer them.

From feat(seo,ui) — see the repository history for the diff.

August 5, 2026

  • Verification became the visible part of an answer. Citation markers activate only once the evidence behind them is ready, the source rule resolves after the answer finalizes, and supported, missing-information, refused and unsupported answers now read differently in wording and structure rather than in colour alone.
  • Citations proved end to end. A cited answer keeps exactly its own sources through a reload, a replay, a Markdown export, a JSON export and a shared link — and a share link never carries the quoted excerpts.
  • Setup status is derived, not tracked. The new-bot checklist reads the actual data — whether knowledge exists, whether a test has passed — instead of a flag that drifts from reality.
  • Recovery paths got real. One registry maps every failure state to the help topic that fixes it, an admin session that expires mid-edit no longer loses the draft, and the password-reset flow has its own test suite.
  • The light theme was rebuilt with real surface separation instead of being the dark layout in pale blue-grey.
  • The largest layout shift on the site is gone. The marketing header was oscillating between two and three rows shortly after load, moving the whole page 54 px twice: 0.6874 CLS, against a 0.01 budget. Now 0.0056.

From feat(chat), feat(trust,a11y,theme), feat(activation), feat(recovery) and perf.

August 4, 2026

  • A pricing page, and a third plan. Every plan gets the full product; plans differ only on how many tokens a month your bots can answer with. The page is written from the live plan catalog, so what it shows is what you are charged.
  • The billing server was hardened to a security review. Card details never reach this platform — checkout is a hosted redirect — the client sends a plan key and never a price, and plan changes are written only by the payment provider's signed webhook.
  • Stale JavaScript and CSS stopped being pinned for 30 days. Cloudflare's edge was caching assets by path and ignoring the version query, so a deploy could take weeks to reach a returning visitor.
  • Mobile navigation, chat header, gutters and a batch of accessibility findings from the 2026-08-04 review.

From feat: pricing page, Max plan, /my/ polish, SW runtime cache, feat(payments) and two fix(ui) passes.

July 28, 2026

  • The front end was redesigned onto the Backbone design system — one dark-first palette that owns both themes, one wordmark, one set of type and spacing tokens.
  • The admin console and the account dashboard were rebuilt on the same system.

From front-end redesign and update admin and /my.

July 27, 2026

  • The admin console was rewritten as one page per area, with permissions enforced per area rather than per account.
  • A cookie-consent banner, with theme and other optional preferences gated behind it.
  • Security, data-integrity and role-coverage fixes from an external audit.

From feat: admin console rewrite + consent banner and the audit-remediation commits.

Before that

The platform's earlier history — the grounding pipeline, the capability system, datasets, channels, and the multi-tenant model everything else sits on — predates this page. It is recorded in the repository's own changelog rather than rewritten here, because a changelog invented after the fact is not a changelog.