Skip to content

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.

docs(changelog): address the changelog to the three.ws community instead of token holders

nirholas20541cf9b62b
diff --git a/CLAUDE.md b/CLAUDE.md
index e43d34ebd..2bbabf1c1 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -207,12 +207,12 @@ This file is the operating brain for every agent here, and agents execute what i
## Changelog: every user-visible change gets an entry
-$THREE holders follow the public changelog (three.ws/changelog, RSS, JSON, Telegram). Keep it alive:
+The three.ws community follows the public changelog (three.ws/changelog, RSS, JSON, Telegram). Keep it alive:
- **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, holder-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.
+- **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 holders 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 holders' 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 lane. 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 lane. 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 docs
diff --git a/api/_lib/changelog-push.js b/api/_lib/changelog-push.js
index c8b5aed92..58022d0ec 100644
--- a/api/_lib/changelog-push.js
+++ b/api/_lib/changelog-push.js
@@ -1,5 +1,5 @@
// @ts-check
-// Automatic changelog delivery to the holder channels (Telegram + X).
+// Automatic changelog delivery to the community channels (Telegram + X).
//
// This is the server-side twin of scripts/changelog-telegram.mjs and
// scripts/changelog-x.mjs. Those scripts are manual tools with repo-file
diff --git a/api/cron/changelog-push.js b/api/cron/changelog-push.js
index 626d5c98e..cec95465b 100644
--- a/api/cron/changelog-push.js
+++ b/api/cron/changelog-push.js
@@ -1,16 +1,16 @@
// @ts-check
-// GET /api/cron/changelog-push — automatic changelog delivery to the holder
+// GET /api/cron/changelog-push - automatic changelog delivery to the community
// 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
-// against DB state, and posts anything new to the holders' Telegram channel.
+// against DB state, and posts anything new to the community Telegram channel.
// 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 is retired (owner directive 2026-07-18). The X lane
// (pushXLane) and its manual script stay in the tree but are no longer
-// invoked. Telegram is the only automatic holder channel; the on-site
+// invoked. Telegram is the only automatic community channel; the on-site
// changelog, RSS feed, and GitHub CHANGELOG.md carry the rest.
//
// A lane whose credentials are absent reports { skipped: 'not_configured' }.
diff --git a/scripts/changelog-telegram.mjs b/scripts/changelog-telegram.mjs
index 6cf6605bf..d947e59c4 100644
--- a/scripts/changelog-telegram.mjs
+++ b/scripts/changelog-telegram.mjs
@@ -1,5 +1,5 @@
#!/usr/bin/env node
-// Push new changelog entries to the $THREE holders Telegram channel.
+// Push new changelog entries to the three.ws community Telegram channel.
//
// NOTE: routine delivery is AUTOMATIC now: /api/cron/changelog-push (Cloud
// Scheduler) posts new entries after every deploy, with its own DB state.