fix: mark ACC tire wear unavailable

[Korupt-virus]

Summary

• mark ACC shared-memory tire wear unavailable instead of treating reserved zeroes as fresh tires
• hide unsupported tire wear and degradation across live dashboards, lap exports, comparisons, and AI prompts
• update telemetry capability metadata, generated catalog artifacts, adapter docs, and focused tests

Why

ACC Shared Memory reserves the tyreWear array but documents it as unused. Presenting its zeroes as real data reports 100% tire health and implies degradation coverage ACC does not provide.

Verification

• bun test test/ai/prompts/inputs-compare-prompt.test.ts test/games/acc/acc-parser.test.ts test/lap-analysis/report.test.ts test/telemetry/analysis-telemetry.test.ts test/telemetry/catalog/contracts.test.ts test/tooling/changelog.test.ts --timeout 120000 — 32 passed
• bun run telemetry:catalog:check — passed
• bun run typecheck — passed

[blacksmith-sh]

Found 2 test failures on Blacksmith runners:

Failures

Test	View Logs
src/stories/ dashboards.snapshot.ts:17:3 › snapshot: AccLiveDashboard ──────────────────────────	View Logs
src/stories/ dashboards.snapshot.ts:17:3 › snapshot: SetupBrowser ──────────────────────────────	View Logs

^{Need help on this PR? Tag @codesmith-bot with what you need.}

[github-actions]

🖼️ App UI changes

Current PR screenshots compared with main. Storybook render-vs-committed-baseline failures are listed separately from committed PR-baseline-vs-main changes.

Changed: render-vs-committed-pr-baseline /AccLiveDashboard

Before	After	Diff

_{Rendered from Storybook and responsive app screenshot tests against current main.}

[Snazzie]

Are you sure Tire wear is not available.

[Korupt-virus]

Are you sure Tire wear is not available.

I ran a stint earlier for my golden test and got no tire wear and i had it enabled. Everything i see online is they do not show it in the data. I will double verify again.