Remove stale Google catalog reference from metric tile tests #562

Description

At main 53e53837981121ab3a13986ed5630b9ce52d0b67, MetricTileContentRegressionTests.swift:37 still uses GoogleUsageMetricCatalog.disabledReason in testUnavailableReasonRemainsDistinctFromReportedValues. The production catalog was removed with Google provider removal #556. Package.swift still declares the metric-tile test target, so SwiftPM compiles it even when filtering for Claude reset tests.

During PR #561 validation, Xcode 26.6 produced this sanitized diagnostic before any filtered tests ran:

MetricTileContentTests/MetricTileContentRegressionTests.swift:37:57:
error: cannot find 'GoogleUsageMetricCatalog' in scope

The unchanged test reference remains in the merged main. The same four Claude reset suites passed all 20 tests through their existing Xcode target; that does not clear the SwiftPM compile failure.

Why

A stale test dependency prevents developers from running unrelated filtered SwiftPM regressions. Restoring a retired provider to satisfy a test would undo the explicitly adopted removal.

Goal

Restore SwiftPM test compilation with a provider-independent unavailable-reason fixture while keeping Google Gemini and Antigravity support removed.

Acceptance Criteria

• The metric-tile regression tests compile without referencing the removed Google catalog.
• The unavailable-reason test still proves that unavailable, setup-required, custom and empty reasons remain distinct from reported usage and credit values; do not remove or weaken its assertions.
• The filtered Claude reset test command compiles and executes its selected tests with zero failures.
• No Google provider, catalog, authentication, endpoint, account migration or retired fixture is restored. Automatic CI workloads and triggers remain unchanged.

Definition of Done

• A separate issue-linked PR contains the bounded test repair, relevant validation evidence, required SwiftLint and clean current-head review.
• Record actual SwiftPM test and pinned-lint results at the implemented head. Any additional baseline defect remains explicit rather than being hidden by skipped compilation or relaxed checks.
• This filing makes no source change and authorizes no release, account operation or live-provider test.

Validation

On an initialized Mac/Xcode toolchain, use canonical LF source and an explicit build environment:

export DEVELOPER_DIR=/Applications/Xcode_26.6.app/Contents/Developer
xcrun swift test --filter MetricTileContentRegressionTests
xcrun swift test --filter ClaudeUsageReset
SWIFTLINT_EXCLUDED_GITHUB_BILLING="$PWD/GitHubBillingFixtureTests" \
  xcrun swift package plugin --allow-writing-to-package-directory \
  swiftlint lint --no-cache --reporter xcode .

• Both filtered test commands exit zero and execute their named tests; the reported missing-symbol diagnostic is absent.
• Pinned SwiftLint exits zero. Keep the existing CI exclusion scoped to the standalone lint command, since exporting it to SwiftPM test builds can make the excluded target's plugin report no lintable files.
• Inspect the diff to confirm the Google removal remains intact and automatic CI has no added work.

Duplicate search covered open and closed issues for the exact symbol, test class and SwiftPM/Google compile scope. Existing #556 describes the completed provider removal, #400 concerns earlier Cursor/Grok behavior, and #559 only records this failure as a validation limitation; none defines this test repair.