Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
fix(changelog): keep X retired as a changelog lane and watch the X content queue on the ops board
overstepping0f2901aac34d
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex efeb65a62..8c4c417ad 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -4,10 +4,6 @@Public history for [three.ws](https://three.ws), newest first. New pages come from `added` dates in data/pages.json; everything else is curated in data/changelog.json. Also available as [JSON](https://three.ws/changelog.json) and [RSS](https://three.ws/changelog.xml), live at [three.ws/changelog](https://three.ws/changelog).-## 2026-09-24--- **Every release now posts to the @trythreews X thread again**: Changelog entries go out automatically to X as replies in one running thread on @trythreews, alongside the Telegram channel. The newest releases post first, the lane waits out X rate limits on its own and resumes, and it rebuilds the thread if a post in it is ever deleted. (`/changelog`) `[improvement, infra]`-## 2026-09-22- **Authorize the three-ws CLI** (`/cli/authorize`): Approve a sign-in started by npx three-ws in your terminal. Check the code matches, choose what the new API key may do (money-moving permissions are flagged and can be removed), and the CLI finishes setup on its own.diff --git a/CLAUDE.md b/CLAUDE.mdindex 5aa5e0430..ff1ec27c2 100644--- a/CLAUDE.md+++ b/CLAUDE.md@@ -212,7 +212,7 @@ The three.ws community follows the public changelog (three.ws/changelog, RSS, JS- **New page?** Nothing extra: the `added` date in `data/pages.json` feeds the changelog automatically.- **Everything else users would notice** (feature, improvement, fix, SDK release, security work): append an entry to `data/changelog.json` with date, community-readable title + summary (plain language, no commit jargon), and tags from: feature, improvement, fix, sdk, infra, docs, security. Optional `link` must be a live page path.- `npm run build:pages` regenerates CHANGELOG.md, public/changelog.json, and public/changelog.xml. It also validates your entry and fails the build on a malformed one.-- **Delivery to the community is automatic.** `/api/cron/changelog-push` (Cloud Scheduler, every 20 min) reads the feed baked into the running image, diffs it against DB state (`app_settings`), and posts anything new to two lanes: the community Telegram channel (`TELEGRAM_CHANGELOG_CHAT_ID`, @three_ws) and a reply thread on the @trythreews X account (`pushXLane`, `X_API_KEY`/`X_API_SECRET`/`X_ACCESS_TOKEN`/`X_ACCESS_SECRET`). X was retired on 2026-07-18 and turned back on by the owner on 2026-09-24. The X lane posts the newest releases first under a daily cap, backs off on a 429 until X's reset time, and re-chains itself if a thread tweet is deleted; its state is `changelog_push_x` in `app_settings`. The lanes are independent, and a failing lane makes the tick answer 502, which shows red on `/api/ops/health`. An entry goes out on its own shortly after the deploy that ships it; there is no manual push step. Credentials live on the Cloud Run service. Do NOT run `npm run changelog:push` / `changelog:push:x` for routine releases anymore: their file-based state (`data/changelog-*-state.json`) is separate from the cron's DB state, so a manual push double-posts. The scripts remain for `--dry-run` previews and owner-directed backfills only.+- **Delivery to the community is automatic.** `/api/cron/changelog-push` (Cloud Scheduler, every 20 min) reads the feed baked into the running image, diffs it against DB state (`app_settings`), and posts anything new to the community Telegram channel (`TELEGRAM_CHANGELOG_CHAT_ID`, @three_ws). **X.com delivery is retired** (owner directive 2026-07-18): `pushXLane` and `scripts/changelog-x.mjs` stay in the tree but the cron never calls them, so do not describe X as an automatic changelog lane. @trythreews posts come from the reviewed X content queue instead (`docs/x-content-pipeline.md`). An entry goes out on its own shortly after the deploy that ships it; there is no manual push step. Credentials live on the Cloud Run service. Do NOT run `npm run changelog:push` / `changelog:push:x` for routine releases anymore: their file-based state (`data/changelog-*-state.json`) is separate from the cron's DB state, so a manual push double-posts. The scripts remain for `--dry-run` previews and owner-directed backfills only.- Internal-only chores (CI, lockfiles, refactors with no visible effect) do NOT get entries.## Documentation: every feature ships with its docsdiff --git a/api/cron/changelog-push.js b/api/cron/changelog-push.jsindex e97ec2a36..0c5dc62c9 100644--- a/api/cron/changelog-push.js+++ b/api/cron/changelog-push.js@@ -1,6 +1,6 @@// @ts-check// GET /api/cron/changelog-push - automatic changelog delivery to the community-// Telegram channel and the @trythreews X thread.+// Telegram channel.//// Runs every 20 minutes. Reads the changelog feed baked into the running// image (public/changelog.json, regenerated by every deploy build), diffs it@@ -8,17 +8,16 @@// Because the feed ships inside the image, entries go out shortly after the// deploy that made them live, with no manual `npm run changelog:push` step.//-// X.com delivery was retired on 2026-07-18 and turned back on by the owner on-// 2026-09-24. X posts are capped well under the account's write budget and-// back off on a 429 until X's own reset time, so it is a showcase of the-// newest releases, not the full log; the on-site changelog and RSS carry that.+// X.com delivery is retired (owner directive 2026-07-18): @trythreews posts+// come from the reviewed X content queue (api/cron/x-content.js), not from+// every release. The X lane in api/_lib/changelog-push.js stays but is unused.+// Telegram is the only automatic changelog channel; the on-site changelog,+// RSS feed, and GitHub CHANGELOG.md carry the rest.//// A lane whose credentials are absent reports { skipped: 'not_configured' }.// Telegram: TELEGRAM_BOT_TOKEN + TELEGRAM_CHANGELOG_CHAT_ID-// X: X_API_KEY + X_API_SECRET + X_ACCESS_TOKEN + X_ACCESS_SECRET//-// The lanes are independent: one failing never stops the other from posting.-// Either failing answers 502, which wrapCron records as a failed heartbeat, so+// A failing lane answers 502, which wrapCron records as a failed heartbeat, so// a stalled lane turns red on /api/ops/health instead of passing silently.//// A DB lock (app_settings) keeps overlapping ticks from double-posting.@@ -27,7 +26,7 @@// remain for previews (--dry-run) and backfills only.import { error, json, method, wrapCron } from '../_lib/http.js';-import { acquireLock, releaseLock, loadFeed, pushTelegramLane, pushXLane } from '../_lib/changelog-push.js';+import { acquireLock, releaseLock, loadFeed, pushTelegramLane } from '../_lib/changelog-push.js';import { requireCron } from '../_lib/cron-auth.js';export default wrapCron(async (req, res) => {@@ -48,15 +47,12 @@ export default wrapCron(async (req, res) => {return;}- // A throw (DB outage mid-lane, an unexpected library fault) is contained to- // its own lane and reported like any other lane error.- const runLane = (lane) => lane(feed).catch((err) => ({ error: String(err?.message || err) }));try {- const telegram = await runLane(pushTelegramLane);- const x = await runLane(pushXLane);- const failed = Boolean(telegram.error || x.error);- if (failed) console.warn('[cron] changelog-push lane error', { telegram, x });- json(res, failed ? 502 : 200, { ok: !failed, telegram, x });+ // A throw (DB outage mid-lane) is reported like any other lane error.+ const telegram = await pushTelegramLane(feed).catch((err) => ({ error: String(err?.message || err) }));+ const failed = Boolean(telegram.error);+ if (failed) console.warn('[cron] changelog-push lane error', { telegram });+ json(res, failed ? 502 : 200, { ok: !failed, telegram, x: { skipped: 'retired' } });} finally {await releaseLock().catch(() => {});}diff --git a/api/ops/health.js b/api/ops/health.jsindex 3c6ece9bc..bbc596d43 100644--- a/api/ops/health.js+++ b/api/ops/health.js@@ -165,9 +165,10 @@ export const CRONS = [// sit in 'rigging' forever).{ id: 'db-retention', label: 'DB retention' },{ id: 'reconstruct-sweep', label: 'Reconstruct sweep' },- // Community delivery: posts every shipped release to Telegram and the X- // thread. It answers 502 when either lane fails, which reads as red here.- { id: 'changelog-push', label: 'Changelog push (Telegram + X)' },+ // Community delivery: posts every shipped release to Telegram, and the+ // reviewed @trythreews queue. Each answers 502 on failure, red here.+ { id: 'changelog-push', label: 'Changelog push (Telegram)' },+ { id: 'x-content', label: 'X content queue' },].map((c) => {const schedule = CRON_SCHEDULES.get(c.driven_by || c.id) || null;return { ...c, schedule, stale_after_ms: deriveStaleAfterMs(schedule) };diff --git a/data/changelog.json b/data/changelog.jsonindex 0feebfc0a..7ffbdc8be 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -28698,16 +28698,6 @@"infra","improvement"]- },- {- "date": "2026-09-24",- "title": "Every release now posts to the @trythreews X thread again",- "summary": "Changelog entries go out automatically to X as replies in one running thread on @trythreews, alongside the Telegram channel. The newest releases post first, the lane waits out X rate limits on its own and resumes, and it rebuilds the thread if a post in it is ever deleted.",- "tags": [- "improvement",- "infra"- ],- "link": "/changelog"}]}diff --git a/public/changelog-recent.json b/public/changelog-recent.jsonindex 48ccddff4..b08914404 100644--- a/public/changelog-recent.json+++ b/public/changelog-recent.json@@ -1,25 +1,14 @@{- "generated_at": "2026-09-24T05:04:10.646Z",+ "generated_at": "2026-09-24T06:25:11.639Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws","url": "https://three.ws"},- "total": 3752,+ "total": 3751,"complete": false,"full_feed": "/changelog.json","entries": [- {- "date": "2026-09-24",- "type": "update",- "title": "Every release now posts to the @trythreews X thread again",- "summary": "Changelog entries go out automatically to X as replies in one running thread on @trythreews, alongside the Telegram channel. The newest releases post first, the lane waits out X rate limits on its own and resumes, and it rebuilds the thread if a post in it is ever deleted.",- "link": "/changelog",- "tags": [- "improvement",- "infra"- ]- },{"date": "2026-09-22","type": "launch",@@ -1610,6 +1599,17 @@"improvement","fix"]+ },+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "The Oracle reference now reads the model it is describing",+ "summary": "The complete Oracle documentation at /oracle/docs described version 2 of the conviction model while production had moved on to version 3, and the difference was not cosmetic. Version 3 changed the question the score answers: earlier versions ranked the odds of a spike, and version 3 ranks the odds of a spike that holds, counting a launch as a hit only if a holder who bought at first sight is still up. A coin that ran 3x and gave it all back was a success under the old target and is a miss under the new one, which is why the base rate underneath every figure on the page is far lower than it used to be. The page had the old target, the old tier probabilities and the old holdout numbers throughout, and its roadmap still promised fitted weights and calibration that had already shipped. Every model figure on the page is now read live from the published model card when you open it, because the engine refits itself every six hours behind a promotion gate and any number typed into a document goes stale on a clock. When that read fails the page says so, shows the values it was published with, explains that they may trail production, and offers a retry rather than a blank space. Two public endpoints that existed but were undocumented are now in the reference: the one that publishes the whole scoring machine, weights and holdout curve and the record of every fit ever refused, and the one that publishes the realized win rate per conviction band from real fills. The tier ladder used to truncate its own evidence, cutting off the sample counts on every band below the top, and now gives each band a full line. In light mode the tier names were near-white on a white card and the strongest bands were invisible; they now have their own ramp.",+ "link": "/oracle/docs",+ "tags": [+ "docs",+ "fix"+ ]}]}diff --git a/public/changelog.json b/public/changelog.jsonindex 8d64a37d0..c6ccc65ae 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,22 +1,11 @@{- "generated_at": "2026-09-24T05:04:10.617Z",+ "generated_at": "2026-09-24T06:25:11.616Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws","url": "https://three.ws"},"entries": [- {- "date": "2026-09-24",- "type": "update",- "title": "Every release now posts to the @trythreews X thread again",- "summary": "Changelog entries go out automatically to X as replies in one running thread on @trythreews, alongside the Telegram channel. The newest releases post first, the lane waits out X rate limits on its own and resumes, and it rebuilds the thread if a post in it is ever deleted.",- "link": "/changelog",- "tags": [- "improvement",- "infra"- ]- },{"date": "2026-09-22","type": "launch",diff --git a/public/changelog.xml b/public/changelog.xmlindex a5582c781..93b1173fb 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -6,14 +6,6 @@<atom:link href="https://three.ws/changelog.xml" rel="self" type="application/rss+xml"/><description>What's new on three.ws: features, improvements, and releases, newest first.</description><language>en</language>- <item>- <title>Every release now posts to the @trythreews X thread again</title>- <link>https://three.ws/changelog</link>- <guid isPermaLink="false">2026-09-24:Every release now posts to the @trythreews X thread again</guid>- <pubDate>Thu, 24 Sep 2026 12:00:00 GMT</pubDate>- <category>improvement</category>- <description>Changelog entries go out automatically to X as replies in one running thread on @trythreews, alongside the Telegram channel. The newest releases post first, the lane waits out X rate limits on its own and resumes, and it rebuilds the thread if a post in it is ever deleted.</description>- </item><item><title>Authorize the three-ws CLI</title><link>https://three.ws/cli/authorize</link>diff --git a/public/features.json b/public/features.jsonindex 9846b9f35..1d1c24c23 100644--- a/public/features.json+++ b/public/features.json@@ -1,5 +1,5 @@{- "generated_at": "2026-09-24T05:04:10.605Z",+ "generated_at": "2026-09-24T06:25:11.604Z","generated_by": "scripts/build-page-index.mjs from data/pages.json","site": {"name": "three.ws",