- TOKEN_CLASSIFICATION.md: ASCII decision-flow diagram updated to match the Rev-2 prose (program → extension → lock → empty → non-empty protected → route), no longer routes all Token-2022 to UNSUPPORTED. - CLAUDE.md: removed stale "Token-2022 support" from out-of-scope; documents the gated Token-2022 policy + that classifier code still skips it for now. - status.json: Phase 1 (Wallet Scanner) marked done — app deployed live at feedthepyre.com (app at /, tracker at /status, api at /api), scan verified end-to-end through the public stack. Reviewed by a doc-consistency audit agent (verdict after fixes: consistent). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
PYRE Status Dashboard
A static, self-contained dark "ember"-themed page the team uses to track PYRE MVP progress. It is a snapshot, not live telemetry.
Files
status.json— the single source of truth. All content on the page (phases, checklists, infra, dates, links) comes from here.index.html— the prebuilt rendered page. Committed so the page works even before anyone runs the generator. Self-contained: inline CSS, no external requests, no JS.README.md— this file.
Editing & regenerating
-
Edit
status.json— flip an item's"done"totrue, update a phase"state"(todo/in_progress/done), or bump"updated". -
Regenerate the page from the repo root:
node scripts/gen-status.mjsThe generator is dependency-free (plain Node ESM, no npm install). It reads
infra/status/status.jsonand rewritesinfra/status/index.html, recomputing the overall % complete from the item done-counts. It prints the output path when finished. -
Commit the regenerated
index.htmlalongside thestatus.jsonchange so the prebuilt page stays consistent with the data.
Deployment
The provision script deploys infra/status/* to /var/www/feedthepyre/status,
and nginx serves it as the site root (feedthepyre.com) until the real PYRE app
ships. Because index.html is prebuilt and self-contained, deployment is a plain
file copy — no build step or generator run is required on the server.