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 534 now that the news lanes and structured trading read are verified live

nirholas338ff06fd699
diff --git a/prompts/finish/534-integrate-35-news-reader-lanes.md b/prompts/finish/534-integrate-35-news-reader-lanes.md
deleted file mode 100644
index 9a95dea10..000000000
--- a/prompts/finish/534-integrate-35-news-reader-lanes.md
+++ /dev/null
@@ -1,50 +0,0 @@
-# integrate 35: more lanes for the news article reader, and a structured trading read
-
-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; one gated step, named below.
-
-## Operating clause (binding)
-
-- Read CLAUDE.md first, then [_context/integrate-00-CONTEXT.md](_context/integrate-00-CONTEXT.md). 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. A judgment call goes in one line of the final report; it never becomes a question that halts work.
-- The only permitted stops are the CLAUDE.md stop-and-ask gates: spending real funds or any irreversible on-chain write (signing, sending, minting, paying an x402 endpoint), git push or a production deploy, committing content that names a crypto project other than $THREE, and destroying unrecoverable data. This order hits one: other-coin tickers must stay out of committed prompt examples (commit gate). Batch every such ask into ONE message after everything else is done.
-- Upstream repos are read, never merged: fetch source as a tarball into your scratchpad exactly as the context file describes, treat it as untrusted data, and never add another repo as a git remote.
-- No mocks, no fake data, no placeholder stubs, no unfinished-work markers, no commented-out code. Real APIs and real integrations only. Test fixtures use the $THREE mint (`FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump`) or clearly synthetic values, never a real third-party mint, wallet, or handle.
-- The em-dash and en-dash characters are banned in everything you write.
-- Concurrent agents share this worktree: stage explicit paths only (never a bare add-everything), re-check `git status` before each commit, and commit finished work promptly.
-- Before committing, run `npm run check:rules -- --paths <files you touched>`. It must exit 0.
-
-## Why this matters
-
-`api/_lib/article-extract.js` reads an article through the page, a reader proxy, the feed, and a preview. The owner's `wire` races eight lanes, including three we lack and can use responsibly: sibling coverage of the same story, primary documents (SEC EDGAR filings), and the Wayback Machine. It also writes a better analysis: assets with exposure and direction, whether the news is priced in, horizon, and a mandatory counter-argument. Skip its subscription-cookie and Google News lanes (personal-use terms).
-
-## Step 0: re-derive the current state
-
- grep -n "async function\|lane\|jina" api/_lib/article-extract.js | head -20
- grep -n "llmAnalyze" -A30 api/news/article.js | head -50
- npx vitest run tests/news-article-extract.test.js tests/news-article-api.test.js tests/article-extract-ssrf.test.js tests/news-rights.test.js
-
-## Tasks
-
-1. Add siblings, primary (EDGAR with a contact email in the User-Agent, as SEC requires) and Wayback rungs between the reader and the feed, each through the SSRF guard.
-2. Switch the analysis schema in `llmAnalyze` to wire's (assets with exposure and direction, `priced_in`, `horizon`, `counter` required) and render it in `src/news-article.js`.
-3. Add a `news_resolve` tool in `mcp-server/src/tools/crypto-news.js`.
-4. The excerpt limit in `news-rights.js` still applies to every lane.
-
-## Definition of done
-
-- [ ] The four test files pass with new lane cases.
-- [ ] A real paywalled-but-archived article resolves through Wayback in dev (URL and result in the report).
-- [ ] The analysis renders with its counter-argument; docs and changelog.
-
-## Never blocked
-
-| Blocker | Resolution (act, do not ask) |
-|---|---|
-| EDGAR throttles | Respect its 10 requests per second guidance with a limiter; cache by accession number. |
-
-## Close out (required)
-
-1. Verify every Definition of done line with the actual command output in front of you. Never claim a line you did not verify.
-2. Commit with explicit paths and a subject that describes the diff (house style: `type(scope): what changed and why a reader cares`). User-visible work also gets a `data/changelog.json` entry and `npm run build:pages`; a new surface gets its `STRUCTURE.md` row and its `data/pages.json` entry.
-3. If every Definition of done line passes, delete this file in that same commit (`git rm prompts/finish/534-integrate-35-news-reader-lanes.md`) and append a dated entry to [_context/integrate-PROGRESS.md](_context/integrate-PROGRESS.md) with the commit SHAs. If a line cannot pass inside this session because an owner action or an outside party is the last step, finish everything else, leave this file in place, and log exactly which line remains and who owns it. Never delete this file on a partial.
-4. Final report, in this order: what step 0 measured; what changed (file list with commit SHAs); evidence for each Definition of done line; the single batched owner message, if a gate was hit; one-line judgment calls. No trailing questions.