Fleet changelogs · dev.ecs0.net
rdmsm4x-changelog-20260924-0222-xentropy-031-honest-discovery-counts-litellm-retired

rdmsm4x - release - XEntropy 0.3.1 (4): honest discovery counts, LiteLLM lane retired, installer relaunches over SSH - claude@rdmsm4x (648db84f) - ISSUE-20260924-05 / TASK-20260924-01 / DEC-20260924-01 - apps/Xentropy - 20260924-0222

Session: 2026-09-24 01:43:27 EDT to 02:23 EDT Ran on: rdmsm4x · Changed state on: all six Macs (rdmsm4x, rdmbair15m5, rdmpw3275m, rdmbair13m5, jdmbair13m5, rdmpw3265m)

The "5000" on XEntropy's main screen was a stale, capped 0.2.x index shown as "Indexed". Counts are now honest (N+, Outdated/Stopped at limit/Incomplete), the LiteLLM lane is gone (LiteLLM abandoned fleet-wide), and 0.3.1 (4) runs on all six Macs.

Scope

Root cause

Every 0.2.x host kept a schema-1 discovery index that had stopped at the old CredentialScanPolicy.defaults cap of 5,000 observations. That engine only bumped truncatedCount and never recorded match_limit. The 0.3.0 Overview printed records.count with the status "Indexed". Measured: rdmsm4x v1 5,000 (2026-08-29), rdmbair15m5 v1 5,000 (2026-09-05), rdmpw3265m v1 5,000 (2026-08-29); jdmbair13m5 also v1.

Commits (apps/Xentropy)

Commit What
8c5067b fix(app): discovery counts say when they are a floor or outdated
d680343 refactor(gateway): retire the litellm-local lane
4891d9b release 0.3.1 (4); the installer contract test checks version agreement (it had been failing 3 assertions on main)
985a936 merge of the above
4a98373 fix(installer): relaunch the app over SSH through a one-shot Aqua agent in gui/<uid> (launchctl asuser needs root)
3a8fd2e docs: LiteLLM lane scrubbed from agent-facing docs and CLAUDE.md; discovery-count rule
6a9dbbd, cb1edb1 docs: 0.3.1 (4) sections in STATUS / SESSION-STATE / ISSUES / CHANGELOG

Files created

Path What
app/Tests/XEntropyTests/DiscoveryCountHonestyTests.swift 6 tests plus 1 env-gated offscreen render of the Overview
~/Library/Application Support/XEntropy/DiscoveryArchive/20260924-schema1/credential-observations-v1.json (rdmsm4x, rdmbair15m5, rdmpw3265m, jdmbair13m5) copy of each old schema-1 index, 0600, sha256 matched before the rescan
~/Library/Application Support/XEntropy/DeploymentRollback/20260924-02*-4a98373… (all six) installer rollback evidence for 0.3.1 (4)

Files modified

Commands run

swift test --package-path app                                   # worktree, full suite
zsh scripts/install_xentropy_local_instance_v1.0.zsh --dry-run --all
zsh scripts/install_xentropy_local_instance_v1.0.zsh --host rdmsm4x      # canary at 985a936
zsh scripts/install_xentropy_local_instance_v1.0.zsh --all              # at 4a98373
zsh scripts/verify_xentropy_fleet_canary_v1.0.zsh --all
~/.local/bin/xentropyctl discovery scan                          # rdmsm4x; other hosts over SSH (no --notes)
ticket open/claim/comment/resolve (DEC-20260924-01, ISSUE-20260924-05/-07, TASK-20260924-01/-02, FEAT-20260924-02)

Verification performed

How to undo

# code: revert on a branch, rebuild, reinstall
cd ~/dev/apps/Xentropy && git revert -m 1 985a936 && git revert 4a98373
# runtime: each host keeps the 0.3.0 app/CLI under DeploymentRollback/<stamp>-4a98373…; use the documented rollback procedure
# discovery index: copy DiscoveryArchive/20260924-schema1/credential-observations-v1.json back to Discovery/ (mode 0600)

Outstanding

Secrets

None handled. The discovery scans are values-free (paths, aliases, HMAC fingerprints and masked previews stay in each host's owner-only store). Key names mentioned: LITELLM_MASTER_KEY, LITELLM_SALT_KEY (catalog baseline labels only); no LITELLM_* names exist in rdmsm4x ~/.secrets.