docs+status: fix Token-2022 audit findings; Phase 1 live

- 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>

infra/status/status.json

@@ -23,7 +23,7 @@
     {
       "id": 1,
       "name": "Wallet Scanner",
-      "state": "in_progress",
+      "state": "done",
       "items": [
         { "label": "Wallet connect frontend", "done": true },
         { "label": "Scan endpoint (POST /api/scan)", "done": true },
@@ -31,7 +31,7 @@
         { "label": "Basic classification (conservative, 43 tests)", "done": true },
         { "label": "Scan results UI (grouped)", "done": true },
         { "label": "Protected/skipped UI", "done": true },
-        { "label": "Deploy app + live-wallet e2e verification", "done": false }
+        { "label": "Deployed live at feedthepyre.com + scan verified e2e", "done": true }
       ]
     },
     {