chore(release): 0.39.53

[pitimon]

PR Goal (one sentence)

Bump @ipv9/tokentracker-cli to 0.39.53 to release the fable/mythos canary pricing fix (#187 / #188) through npm.

Scope

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

Checklist

• npm run ci:local passes, or focused test commands are listed below with rationale
• New dashboard/user-facing strings go through dashboard/src/content/copy.csv (N/A)
• Commits follow conventional style (feat: / fix: / refactor: / docs: / chore: / test: / ci:)
• PR description explains why, not just what
• Version bump files are in lockstep when release-bound (package.json, package-lock.json)
• npm publish state is recorded when release-bound (npm view @ipv9/tokentracker-cli version versions --json confirmed 0.39.52 is latest/immutable; npm publish --dry-run verified 174 files, tarball ok, no unexpected pricing-seed diff after revert)

Why

fix(pricing): resolve fable/mythos canary variants via fuzzy match (#188) merged to main as a source-only fix. Per CLAUDE.md release workflow, changes under src/ that affect shipped behavior require a package version bump + npm publication, and .github/workflows/npm-publish.yml only publishes when the on-disk package.json version is not yet on the registry — it skip-noticed on the #188 merge because the version was still 0.39.52.

Version and publish discipline (CLAUDE.md checklist)

1. npm view @ipv9/tokentracker-cli version versions --json → latest published is 0.39.52 (immutable, confirmed unused for 0.39.53).
2. npm version 0.39.53 --no-git-tag-version --ignore-scripts → bumped package.json + package-lock.json only.
3. NODE_ENV=test npm run ci:local → full pass. npm publish --dry-run → 174 files, tarball ok.
4. npm run dashboard:build && node scripts/build-pricing-seed.cjs (via prepublishOnly during the dry-run) refreshed src/lib/pricing/seed-snapshot.json with fresh upstream LiteLLM data — reverted from this PR since it is an unrelated data refresh outside the scope of a version-bump PR (previous releases split this into its own chore(pricing): record publish snapshot PR, e.g. chore(pricing): record 0.39.52 publish snapshot #186). Publish (step 4 below) will regenerate and commit it as intended.
5. Publish will run automatically via .github/workflows/npm-publish.yml on merge to main (Trusted Publishing/OIDC).
6. Local web service deployment/redeploy is out of scope for this change — no local service is running against this checkout that needs the new bundle right now.

Regression Test Gate

Most likely regression surface

• test/web-only-product-scope.test.js hardcodes the expected package.json version as a release-authority guard; updated in lockstep with this bump (was failing 0.39.52 vs actual 0.39.53 before this fix).

Verification method (choose at least one)

• NODE_ENV=test npm run ci:local (full gate, all validators + product + dashboard suites)
• node --test test/npm-publish-workflow.test.js test/release-automation.test.js test/web-only-product-scope.test.js per agent-os/standards/release/version-lockstep.md

Uncovered scope

• Live npm publish + registry smoke test happens via CI after merge (.github/workflows/npm-publish.yml), not locally in this PR.