chore(pricing): record 0.39.54 publish snapshot

[pitimon]

PR Goal (one sentence)

Record the LiteLLM pricing-seed snapshot regenerated by the 0.39.54 npm publish, matching the established pattern (#186, #190).

Scope

• CLI (src/)
• Dashboard (dashboard/)
• Docs / CI / config

Checklist

• npm run ci:local passes
• New copy strings (N/A, data file only)
• Commits follow conventional style
• PR description explains why, not just what
• Version bump (N/A, no version change)
• npm publish state recorded: 0.39.54 published and verified — npm view @ipv9/tokentracker-cli version → 0.39.54; node scripts/verify-registry-package.cjs 0.39.54 → ok, dashboardAssets=16, cliHelp=ok

Why

Same as #190: npm publish prepublishOnly refreshed the pricing seed as a side effect of the 0.39.54 publish (kept_models unchanged at 2633, generated_at -> 2026-08-22T15:32:55.137Z). Recorded so a fresh checkout matches the published artifact.

Re-verified the #187/#193 fixes against this fresh seed:

claude-auto-pilot-fable-v1-canary  => true curated:fuzzy
claude-mythos-v1-canary            => true curated:fuzzy
claude-mythos-preview              => true litellm:exact   (the real collision case from #193, still unaffected)

Regression Test Gate

Verification method

• npm run ci:local full pass on the exact tree that produced this diff, plus a manual pricing-matcher smoke check against the new seed covering both the original Claude auto-pilot/canary model ids (fable/mythos) bill $0 — fuzzy pricing match misses non-contiguous substrings #187 fix and the Pricing matcher has no general normalizer for vendor-renamed auto-pilot/canary model ids (#187 was patched per-name) #193 collision-risk regression.

Uncovered scope

• release: migrate npm publication to Trusted Publishing OIDC #179 (CI OIDC publish) remains open; this release again used the documented local-recovery path.
• Verify claude-fable-5 pinned price ($10/$50) against actual Anthropic billing for canary route #191 (verify Fable 5 rate against a real invoice) remains open, tracked separately.