chore: classify and burn down the 32 baseline-tolerated unused production exports

[thymikee]

Context

fallow-baselines/production-unused-exports.json tolerates 32 exported symbols with no known production consumers (pnpm check:production-exports passes only because of the baseline). Verified on the #1217 head: the PR adds none of them — this is standing debt, concentrated in:

• src/core/command-descriptor/registry.ts (4)
• src/commands/index.ts (3)
• src/cloud-webdriver/aws-device-farm.ts (2) + src/cloud-webdriver/browserstack.ts (2)
• src/commands/interaction/runtime/selector-read.ts (2)
• src/platforms/android/ime-lifecycle.ts (2)
• singles in src/cli/parser/args.ts, src/cli/parser/command-suggestions.ts, src/commands/command-metadata.ts, src/commands/command-surface.ts, and others (run npx fallow dead-code --config fallow-production-exports.json --production --unused-exports for the full list).

Method

Classify each entry before touching it (from the prior production-vs-default differential audit, three sub-types):

1. dead — nothing reaches it: delete the export and its tests;
2. live-seam — a deliberate extension point (plugin/registry surface): keep, annotate with fallow-ignore + reason so it leaves the baseline;
3. wrapper — reachable only through a re-export that production bypasses: collapse the wrapper.

Goal: shrink the baseline toward zero so check:production-exports runs baseline-free and new dead exports fail loudly instead of being absorbed.