fix: gate rumble/motion on the active path, not the model DB

[emir-hasanbegovic]

Problem

A Switch Pro over USB advertised rumble on Standard and Bluetooth (and left the input inspector's rumble test buttons enabled), but only Direct actually rumbled.

Root causes

1. The capability layer ORed two path-specific signals. CapabilityComposer.deviceControllerLayer and ConfigureBindingsViewModel computed rumble as device.hasRumble || native.modelHasRumble(...). The framework probe is authoritative for Standard/Bluetooth; the model DB (parserHasRumble) only for Direct. ORing let the Direct-only capability leak onto the framework paths.

2. The framework probe is itself a false positive for the Switch protocol. vibratorManager.vibratorIds is non-empty for a Switch Pro — Android registers a vibrator — but it can't drive Nintendo's proprietary HD-rumble, which only our Direct path speaks. So even after fixing (1), device.hasRumble stayed true and the framework paths still advertised rumble that never fires.

Fix

• Per-path resolution (mirrors MainViewModel's existing split): a Direct synthetic reads the parser DB, a framework pad reads the OS probe. CapabilityComposer is the single source of truth; the bindings VM reads it, and the inspector disables its rumble buttons when the path can't rumble.
• Suppress the false-positive probe at its source (probeRumble) for models the native DB maps to the SWITCH_PRO_USB parser — the Pro, Joy-Con Charging Grip, and Online controllers, plus any future Switch-protocol device — via a new modelFrameworkRumbleUnreliable lookup (mirrors modelHasRumble). device.hasRumble is now truthful for every downstream surface (PathCard, composer, bindings, wizard, inspector); Direct still works through the model DB.
• Re-probe the vibrator in onInputDeviceChanged, symmetric with the existing late-gyro re-probe.

Net: rumble shows only where it fires — Direct for Switch-protocol pads; framework for Xbox/PlayStation where the OS actually drives it.

Why the parser, not the Nintendo vendor

Keying on SWITCH_PRO_USB (the native model DB's parser field) targets the exact cause — the proprietary protocol — and covers the whole family without a hand-maintained VID:PID list that could drift from the DB.

Tests

• usb_parsers_test.cpp: parserFrameworkRumbleUnreliable true for SWITCH_PRO_USB, false for the Xbox/PlayStation families.
• CapabilityComposerTest: per-path matrix (framework trusts the probe / ignores the model DB; synthetic reads the model DB; end-to-end capabilityForCandidate for a Standard Switch Pro).

Local CI — all green

clang-format · check_play_metadata · ktlintCheck · detekt · lint · testDebugUnitTest · nativeTest (168/168) · assembleDebug. Emulator instrumented job runs in CI (no local device attached).

🤖 Generated with Claude Code