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.

chore(prompts): retire order 410, the awesome-solana-ai submission doc is marked unpublished

nirholasd234b5de228f
diff --git a/prompts/finish/410-auto-register-awesome-solana-doc.md b/prompts/finish/410-auto-register-awesome-solana-doc.md
deleted file mode 100644
index 9b640d3a9..000000000
--- a/prompts/finish/410-auto-register-awesome-solana-doc.md
+++ /dev/null
@@ -1,48 +0,0 @@
-# 410. Register `docs/awesome-solana-ai-submission.md` in `data/pages.json`, or mark it deliberately unpublished
-
-How to run: paste this file's repo path into a fresh Claude Code chat in this repository and say "run this work order". Runnable now, no gate, no owner action required.
-
-## Operating clause (binding)
-
-- Read CLAUDE.md first. CLAUDE.md overrides everything, including this file.
-- Finish 100% in this session. Never end the turn with a question, an option list, or an unexecuted plan.
-- The only permitted stops are the CLAUDE.md stop-and-ask gates (spend/on-chain writes, push/deploy, posting externally, committing content referencing a crypto project other than `$THREE`, destroying unrecoverable data). This order touches none of them.
-- Concurrent agents share this worktree: stage explicit paths only (never `git add -A` or `git add .`), re-check `git status` and `git diff --staged` before committing.
-- The em-dash and en-dash characters are banned in everything you write.
-
-## Step 0: re-derive the current state
-
- npm run audit:docs
-
-Confirm it still reports exactly this finding (it may have already been fixed by another agent; if `npm run audit:docs` is already clean, verify that, then retire this order the same way described below instead of making a change):
-
- Public docs missing from data/pages.json (live but undiscoverable) (1):
- docs/awesome-solana-ai-submission.md served at /docs/awesome-solana-ai-submission but absent from data/pages.json, so no crawler can find it.
-
-This was surfaced by order 409 (evolve/main reconciliation merge) as a pre-existing gap: the doc was added by main commit `0e0a806cd` ("docs(parity): add the awesome-solana-ai submission kit...") without a matching `data/pages.json` entry, so it has been live and undiscoverable since that commit, unrelated to the merge itself.
-
-## Task
-
-1. Read `docs/awesome-solana-ai-submission.md` to confirm what it documents and whether it is meant to be a crawlable, linked-to doc page or an internal-only submission kit (check whether anything in the repo links to `/docs/awesome-solana-ai-submission`; `npm run audit:links` output and a `grep -rn 'awesome-solana-ai-submission'` across `pages/`, `docs/`, and `prompts/` will show this).
-2. If it is meant to be discoverable (the common case for `docs/*.md`): add an entry for it in `data/pages.json`, matching the shape and section used by sibling doc entries already there (title, description, path `/docs/awesome-solana-ai-submission`, section, dates).
-3. If it is deliberately internal (for example, a one-time submission packet for a third-party directory rather than ongoing user-facing documentation): add its slug to the `UNPUBLISHED_DOCS` map in `scripts/audit-docs.mjs` (around line 287) with a one-line reason, following the existing entries' format exactly.
-4. Run `npm run audit:docs` and confirm the finding is gone.
-5. Run `npm run audit:links` to confirm no new dangling/broken link resulted.
-6. Run `npm run check:rules -- --paths <files you touched>` and fix anything it flags.
-
-## Done when
-
-- `npm run audit:docs` exits with 0 findings.
-- `npm run audit:links` shows no new broken/dangling entries caused by this change.
-- This file is removed with a dated entry in `prompts/finish/_context/production-100-PROGRESS.md` citing the fix commit SHA.
-
-## Never blocked
-
-| Looks like a blocker | It is not | Do this |
-|---|---|---|
-| Unsure whether the doc should be public or internal | The doc's own content and whether anything already links to it settles this | Read it; check for existing inbound links; default to publishing (the audit's own preferred fix) unless the content is clearly a one-time internal packet |
-| Another agent already fixed this | Routine for a shared worktree | Re-run `npm run audit:docs` first (step 0); if clean, retire this order without a code change |
-
-## Report format
-
-State: the step-0 `npm run audit:docs` result, which of the two fixes was applied and why, the post-fix `npm run audit:docs` and `npm run audit:links` output, and the commit SHA.
diff --git a/prompts/finish/_context/production-100-PROGRESS.md b/prompts/finish/_context/production-100-PROGRESS.md
index 627d9c38c..047b78007 100644
--- a/prompts/finish/_context/production-100-PROGRESS.md
+++ b/prompts/finish/_context/production-100-PROGRESS.md
@@ -1551,3 +1551,13 @@ Did, test-first: added two cases to `tests/world-health-asset-sweep.test.js` (no
`npm run check:rules` exits 0 on all 4 touched files. Filed OWNER-ACTIONS row 68 for the underlying decision (redeploy `hyperfy-world` or formally retire `world.three.ws`); row 67 was already taken by a prior concurrent entry, confirmed by re-reading the file before numbering. Fix commit: `118649a47`.
Left: nothing for this order beyond OWNER-ACTIONS row 68, which is an owner decision, not a bug. `prompts/finish/413-auto-world-health-down-masked-unknown.md` deleted in this closing commit.
+
+## 2026-10-24: order 410 (awesome-solana-ai submission doc missing from pages.json) closed
+
+Measured: `npm run audit:docs` reported two findings, not the one the order was filed against: `docs/awesome-solana-ai-submission.md` (this order's target) and `docs/simready-assets.md` (a separate, newer gap already owned by order 414, confirmed by reading that file and leaving it untouched).
+
+Read `docs/awesome-solana-ai-submission.md`: a one-time PR packet preparing a `solana-foundation/awesome-solana-ai` README submission, ending in an "Owner message (one yes)" section gating the actual PRs on explicit owner approval. Nothing in `pages/`, `docs/`, or `prompts/` links to `/docs/awesome-solana-ai-submission` except the order files that reference it by path. This is the internal-packet case the order's task 3 describes, not the common discoverable-doc case, so registered it in `UNPUBLISHED_DOCS` in `scripts/audit-docs.mjs` (new entry `awesome-solana-ai-submission`, after the existing `listings-registry` entry) with the reason, rather than adding a `data/pages.json` entry.
+
+`npm run audit:docs` now reports only the pre-existing `docs/simready-assets.md` finding (order 414's scope); the targeted finding is gone. `npm run audit:links` shows 0 broken/dangling/stub links. `npm run check:rules -- --paths scripts/audit-docs.mjs` exits 0. Fix commit: `3e8bac005`.
+
+Left: nothing for this order. `prompts/finish/410-auto-register-awesome-solana-doc.md` deleted in this closing commit.