rdmsm4x - release - XEntropy 0.3.2 (5): complete hub scans, catalog Archive/Restore, fleet-wide LiteLLM sweep - claude@rdmsm4x (648db84f) - ISSUE-20260924-07 / FEAT-20260924-02 / TASK-20260924-02 - apps/Xentropy + fleet - 20260924-0713

Session: 2026-09-24 06:19:04 EDT to 07:14 EDT (after Rich: "why aren't we working on the tickets" / "resolve all open tickets/iterate/execute/resolve/keep going") Ran on: rdmsm4x · Changed state on: all six Macs (XEntropy 0.3.2), plus repos on the hub

Every ticket I had open is resolved. Whole-home discovery now completes on the dev hub (rdmsm4x shows 116,057 · Indexed instead of 50,000+). Both LiteLLM catalog rows are archived on all six Macs. LiteLLM is swept out of every live config, code path and agent-facing doc.

Scope

• Budget usage_status = hold (Anthropic 7-day 77%, vendor-authoritative), so all work was done inline with no subagents.
• Coordinated with the agy overnight run (pid 3624, lead claude@rdmbair15m5) by announcing file lanes on the bus. It had already built the store half of FEAT-20260924-02 (926697c); I finished the app half and deployed.
• Deliberately left: FEAT-20260924-01 (owned by claude@rdmpw3275m and blocked on Rich's logins, exports, DEC-D rule change and DEC-E purchase); third-party references and historical records of LiteLLM.

XEntropy commits (canonical main 306fa74, pushed to fleet/origin/backup)

Other repos

• app-baseline 85b0803: ecs_sign_notarize.zsh v1.1.0 gains an optional --entitlements PLIST; the key assertion was verified both ways; default unchanged for the 19+ calling apps.
• Tyrell 90b1919, b95916e: LiteLLM proxy-spend meter, Usage card and provider entry removed; ISSUES #29 closed won't-do. 184 XCTest + 984 Swift Testing, identical to the main baseline. Not deployed (ships with Tyrell's next build).
• ai/LLM 173a3f876: LiteLLM/ (56,182 files) moved to archive/litellm-20260924/ with a README (still git-ignored).
• fleet d8b0154 (superseded banners on 4 LLM plan docs), ToshLLM 87d8e78, scripts ec0c331 (swarm_monitor), localAI/openrouter c50ed8a (OR-002 resolved), localAI/mem0 b5accf1; ai/Antigravity README edited in place (not a repo).

Verification performed

• Measured first: rdmsm4x lifted-limit scan completed with 3,298,014 entries, 889,480 files, 14.2 GB, 115,063 observations, 528 s, 509 MB peak, 63 MB. Shipping-limit validation also complete: 115,231 observations, 547 s.
• XEntropy suite at 8090474: 461 XCTest (459 passed, 2 env-gated skips, 0 failed) + 5 Swift Testing. Each new check was mutation-tested: the sizing test fails at 50,000, the path test fails with the old guard, the contract test fails on version drift, and the entitlement assertion fails when the key is missing.
• Fleet: install 0.3.2 67f1321 gave INSTANCE_PASS 6/6 launch=running; verify gave ARTIFACT_PASS 6/6 (0.3.2/5, ZU2882L4HT, universal2, schema 2, running).
• Catalogs (read-only CLI, all six): both LiteLLM rows archived, 0 others, 22 rows, marker at mode 600.
• Rescans with the installed CLI: rdmsm4x 116,057 / 10,141 distinct / 892,476 files / 513 s; rdmbair15m5 83,848 / 13,862 / 704,683 / 239 s; both complete, apps relaunched.

How to undo

# XEntropy: each host keeps the 0.3.1 app/CLI under DeploymentRollback/<stamp>-67f1321…
# discovery indexes: DiscoveryArchive/20260924-capped/credential-observations-v1.json → Discovery/ (0600)
# catalog rows: inspector "Restore Record…" returns each LiteLLM row to its seeded status (the marker keeps it restored)
# LiteLLM tree: mv ~/dev/ai/LLM/archive/litellm-20260924/LiteLLM ~/dev/ai/LLM/LiteLLM (contradicts DEC-20260924-01)
# code: git revert the commits above in each repo

Outstanding

• Notarized XEntropy build end to end: ./build.sh --sign-notarize from Terminal on rdmsm4x (the Developer ID identity is only in the login keychain, which a background session cannot unlock).
• Apple Notes discovery and the Chrome Safe Storage prompt each still need one Allow click per Mac.
• Apple Notes entry for this changelog: filed by the hub's com.rdm.claude-notes-autopublish agent on its next run.

Secrets

None handled or printed. Discovery is values-free. Key names mentioned: LITELLM_MASTER_KEY, LITELLM_SALT_KEY (labels only); FLEET_SIGNING_P12_PASSWORD was read by fleet_sign_unlock by name, as build.sh does.