chore: baseline-free production-exports cleanup (#1276)

[devin-ai-integration]

Summary

Burn down the 32 baseline-tolerated unused production exports so pnpm check:production-exports no longer relies on a grandfather list.

Classification

Category	Exports	Action
live-seam	parseArgs, listCommandAliasSuggestionEntries, cloud-webdriver factories/capability builders, command-surface/registry introspection helpers, platform reset/clear test hooks, isPlatform, setActiveProviderDeviceRuntimes, ARCHIVE_EXTENSIONS, commands catalog	Keep and annotate with @internal JSDoc visibility tags; fallow now treats them as intentional seams instead of dead exports.
wrapper	commands/index.ts re-exports of ref/selector; daemon/lease-context.ts re-export of buildLeaseDiagnosticsContext	Remove the re-export; update all importers to pull directly from commands/interaction/runtime/selector-read.ts and core/lease-scope.ts.
dead/stale	src/platforms/android/multitouch-helper.ts:resetAndroidMultiTouchHelperInstallCache	Remove stale baseline entry (export no longer exists).

Result

• fallow-baselines/production-unused-exports.json is now empty.
• pnpm check:production-exports passes without a baseline and will fail loudly on any newly introduced dead export.

Note: I used @internal JSDoc tags rather than // fallow-ignore-next-line unused-export because the repo already uses @internal for the same purpose in src/core/interaction-targeting.ts, and visibility tags do not produce stale-suppression warnings in the test-inclusive fallow audit run.

Fixes #1276

Link to Devin session: https://app.devin.ai/sessions/2819f6f9400b455aa9414722ba937d64
Requested by: @thymikee

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring

[github-actions]

Size Report

Metric	Base	Current	Diff
JS raw	1.7 MB	1.7 MB	+45 B
JS gzip	557.5 kB	557.5 kB	+31 B
npm tarball	673.0 kB	673.1 kB	+65 B
npm unpacked	2.4 MB	2.4 MB	-42 B

Startup median (7 runs, lower is better):

Scenario	Base	Current	Diff
CLI --version	23.6 ms	22.3 ms	-1.3 ms
CLI --help	51.1 ms	51.0 ms	-0.2 ms

Top changed chunks:

Chunk	Raw diff	Gzip diff
dist/src/apps.js	0 B	-2 B

[thymikee]

Review — approve with three notes

The classification is honest and the mechanics check out. Verified independently:

• The two wrapper collapses (ref/selector re-export in commands/index.ts, buildLeaseDiagnosticsContext in lease-context.ts) are safe: the published package surface is src/sdk/*, which never exported or imported either — no external-API impact, no changelog needed.
• The baseline-free check:production-exports is green in CI, confirming fallow honors the @internal/@public JSDoc tags with no config change.
• Emptying the baseline is the real win: future dead exports now fail loudly instead of being absorbed (the goal of chore: classify and burn down the 32 baseline-tolerated unused production exports #1276).

Three follow-ups before/at merge:

1. @internal is now a trust-based escape hatch — nothing mechanically distinguishes "annotated live-seam" from "annotated but dead." Worth one line in CONTRIBUTING (or a comment at the fallow config): a new @internal export tag needs the same justification a baseline entry used to get in review.
2. ARCHIVE_EXTENSIONS looks mis-classified. It's tagged @public while having zero consumers anywhere — a frozen copy of an internal constant that exists only to be exported. Either re-export it from src/sdk/install-source.ts so it has a real public consumer story, or delete it as the one genuinely dead export in the list.
3. Trivial: isPlatform's tag reads "Public type guard exposed for unit tests" — public and internal in one sentence; pick one.

[devin-ai-integration]

Thanks for the review. Addressed all three notes:

1. Added a CONTRIBUTING note that intentional non-production exports should use a JSDoc @internal tag with a short justification, treated as a reviewed baseline entry.
2. Restored ARCHIVE_EXTENSIONS and re-exported it from src/sdk/install-source.ts so the public ./install-source package subpath has a real consumer story. Fallow now sees it used by the public SDK entry and it leaves the baseline.
3. Fixed isPlatform's JSDoc to plain @internal and rewrote the wording to remove the public/internal contradiction.

All checks green.

[thymikee]

Review finding at f06b1882592e6973cd9df64e416d125b4970763e:

The export list is burned down correctly, but the claimed baseline-free outcome is incomplete. pnpm check:production-exports still passes --baseline fallow-baselines/production-unused-exports.json, check:production-exports:baseline still regenerates it, and CONTRIBUTING still describes reviewed baseline entries. An empty baseline is still a baseline and can absorb future entries.

Please either:

• remove the --baseline option, baseline-generation script, and corresponding guidance so new unused exports fail without a grandfather file; or
• narrow the PR/issue claim to "empty baseline" rather than baseline-free enforcement.

The export classification and wrapper cleanup otherwise look sound. Current-head iOS smoke was still running at review time.

[github-actions]

PR Preview Action v1.8.1
Preview removed because the pull request was closed.
2026-07-16 09:44 UTC

[devin-ai-integration]

Good catch — I had only emptied the baseline file. Now the check is actually baseline-free:

• Removed --baseline from pnpm check:production-exports.
• Deleted fallow-baselines/production-unused-exports.json.
• Removed the check:production-exports:baseline script.
• Updated CONTRIBUTING.md to describe baseline-free enforcement and dropped the "reviewed baseline entry" language.

pnpm check:production-exports now fails on any new unused production export without a grandfather file. CI is green.

[thymikee]

Re-reviewed current head 49e9ff010f34af7faa82c145d4084b818ce94c65 after the follow-up.

The earlier finding is resolved: the production-export gate no longer passes a baseline, the baseline-generation script and file are removed, and contributor guidance now describes baseline-free enforcement. All 23 current-head checks pass and the PR is clean.

Ready for human merge review.

[devin-ai-integration]

Thanks for the re-review — ready for human merge review.