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
docs(x-grok): log order 048, mention store shipped and its migration awaiting a clean apply
nirholas7f459232e149
diff --git a/prompts/finish/_context/x-grok-PROGRESS.md b/prompts/finish/_context/x-grok-PROGRESS.mdindex aa8c0001b..aca8fd329 100644--- a/prompts/finish/_context/x-grok-PROGRESS.md+++ b/prompts/finish/_context/x-grok-PROGRESS.md@@ -20,3 +20,9 @@ Cross-session handoff for the `x-grok-` orders ([x-grok-00-CONTEXT.md](x-grok-00- Shipped `7c2382374`: `api/_lib/x-mention-intents.js` (`parseMentionIntent`, `parseLaunch`, `normalizeText`, `splitLeadingHandles`, `sanitizeArg`, `addressing`), 94 tests in `tests/x-mention-intents.test.js` (83-case corpus, 17 hostile), and a pointer in order 925 to consume this parser.- Step 0: no `api/_lib/x-mention*` existed besides 046's reader; order 925 had not built a parser, so its `launch <NAME> $<TICKER> [description]` grammar was written here first, held to the `/launch` form limits imported from `src/launch/launch-model.js` (the parser's only import; a test asserts it).- Behavior the next orders rely on: money-movement, secret and instruction-override phrasing returns `help` (reason `refused_*`) and never reaches a model. A handle that only rides along in reply handles of a thread already naming us is `inherited`: explicit commands still parse, chatter is `ignore` (the real 2026-10-08 "add me" shape). Unrecognized direct text is `chat` for both company and agent accounts (reason `company_chat` / `agent_chat`); order 051 decides whether the company account answers it. `image3d` args carry `sourceAuthorId` so order 053 can enforce its own-image rule. `$THREE` is a reserved ticker for `launch`.++## 2026-10-08: order 048 (mention events schema) built, migration NOT applied (order file kept)++- Shipped `ab198d4ff`: migration `api/_lib/migrations/20261008170000_x_mention_events.sql`, `api/_lib/x-mention-store.js` (`recordMention`, `updateDecision`, `countByAuthor`, `recentDecisions`, `getMentionEvent`, `getCursor`, `advanceCursor`, `cursorKey`), 18 PGlite tests in `tests/x-mention-store.test.js` built from the migration file itself, including the dedupe race (three concurrent inserts, one wins).+- Schema notes for later orders: `decision` is null until decided and also allows `pending` (052 follow-ups) and `paused` (055 kill switch) beyond the order's list. `reply_tweet_id` is set once and never replaced. Cursor key is `x_mentions_cursor:<kind>:<ref>` and only moves forward (numeric compare in SQL).+- Remaining DoD line: "`npm run db:migrate` applied". Not run because `db:status` showed another pending migration, `20261008150000_revenue_direct_settle_backfill.sql`, untracked (uncommitted, another session's in-flight work) and a payout-ledger backfill, and the owner instruction for this run was not to apply when that is the case. Owner of the last step: whoever lands that backfill (or the owner). Then `npm run db:status` and `npm run db:migrate` apply both; or apply just this one with `node scripts/apply-migrations.mjs --apply --file 20261008170000_x_mention_events.sql`. Until then `db:check` reports it pending and blocks a deploy, as it already did for the backfill.