refactor(commands): derive pass-through command bindings with a generic BoundOf helper

[thymikee]

What

Replaces the hand-written bind*Commands functions and their mirrored Bound*Commands type declarations with one derived form, for the families that are genuinely pass-through:

• BoundOf<T> mapped type + bindRuntimeCommands(commands, runtime) in runtime-types.ts (~20 lines)
• capture, system, admin, recording, observability: bind function and mirrored type deleted; Bound*Commands becomes a one-line BoundOf<...> alias, bindCommands() calls the generic directly
• apps: keeps bindAppCommands as ...bindRuntimeCommands(appCommands, runtime) plus the manual list override (its resolveAppsFilter normalization is real logic, not boilerplate)
• selectors / interactions: untouched by design — 11 of their 17 entries prepend a positional target/text argument and Omit that field from options, which a mapped type cannot derive

Net −86 lines. From the adversarially-verified overengineering audit (follow-up to #1367; scope was verified there, including the selector/interaction exclusion).

Behavior-preservation notes

• BoundOf has an undefined extends O branch producing (options?: O) => Promise<R>, matching the hand-written optional-parameter shape — zero-arg calls like commands.system.back() type-check exactly as before. A naive RuntimeCommand<O,R> → BoundRuntimeCommand<O,R> mapping would have broken them.
• The mapped type is homomorphic, so property JSDoc on the source command-map types propagates to the derived bound types.
• Bound* type names were never on the published surface (only bindCommands/BoundAgentDeviceCommands escape, to runtime.ts).

Verification

typecheck · lint · check:production-exports · full unit suite (489/489 files) · format

Note

Stacked on #1367 (base = its branch) with the system/runtime/index.ts overlap already resolved as the union of both deletions. After #1367 squash-merges and GitHub retargets this PR to main, rebase with git rebase --onto origin/main <old-base-head> to drop the inherited commits — no conflict resolution remains.

[github-actions]

Size Report

Metric	Base	Current	Diff
JS raw	1.8 MB	1.8 MB	-815 B
JS gzip	577.7 kB	577.5 kB	-186 B
npm tarball	692.3 kB	692.1 kB	-208 B
npm unpacked	2.4 MB	2.4 MB	-815 B

Startup median (7 runs, lower is better):

Scenario	Base	Current	Diff
CLI --version	26.7 ms	27.2 ms	+0.5 ms
CLI --help	57.0 ms	57.2 ms	+0.1 ms

Top changed chunks:

Chunk	Raw diff	Gzip diff
dist/src/runtime.js	-907 B	-254 B
dist/src/tv-remote.js	+99 B	+52 B
dist/src/registry.js	0 B	+11 B
dist/src/interaction.js	+9 B	+8 B
dist/src/cli.js	0 B	-3 B

[thymikee]

Stacked on #1367 (base changed to its branch) with the system/runtime/index.ts conflict pre-resolved — the file is now the union of both deletions (no rotate, derived BoundOf binding). When #1367 squash-merges, GitHub retargets this PR to main; it will then need a git rebase --onto origin/main <old-base-head> to drop the inherited commits — the content conflict itself is already resolved. The "expect a trivial merge conflict" note in the description is obsolete.

[github-actions]

PR Preview Action v1.8.1
Preview removed because the pull request was closed.
2026-07-23 08:22 UTC

[thymikee]

Code review is clean at 2ed9f7c; the generic binder preserves current option/result semantics and the apps list override remains effective. All checks are green. This is not merge-ready yet because it is intentionally based on #1367: after #1367 lands, rebase onto current main, drop the inherited #1367 commits, verify the isolated diff, and rerun checks/review. Please also refresh the stale PR-body notes about system.rotate JSDoc and an expected conflict. No separately authorized cross-vendor review was performed.

[thymikee]

Re-review clean at 4ef8a78 against exact base #1367 b24e812. The isolated diff remains the same seven command-binding files; optional parameters, pass-through delegation, the manual apps.list normalization, and selector/interaction exclusions remain correct. All current checks pass. The PR is still stack-blocked: after #1367 lands, rebase/retarget onto current main, verify the isolated diff, and rerun exact-head checks/review. No separately authorized cross-vendor review was performed.

[thymikee]

Reconciled after #1367's merge: rebased with git rebase --onto origin/main b24e81263 — the branch is now the single commit b7b00f7d4 directly on main@d237bc555, no inherited commits (GitHub had already retargeted the base to main).

Isolated diff verified unchanged: git patch-id --stable of the pre-rebase diff (b24e812..4ef8a78) and the post-rebase diff (origin/main..HEAD) are identical (36bbc374a32b), so the reviewed content at 4ef8a78 carried over byte-for-byte.

Exact-head checks at b7b00f7d4: typecheck · lint · check:fallow (80 changed files, no issues) · format:check · full unit suite (unit-core + android-adb): 487/487 test files pass. Ready for the final review pass.

[thymikee]

Re-review clean at b7b00f7. The branch now targets exact current main, the reviewed tree is unchanged from 4ef8a78, the isolated diff remains the same seven command-binding files, and all exact-head checks pass. Please remove/update the stale PR-body note that still describes #1368 as stacked on #1367 and awaiting a future rebase. Code is ready for human review. No separately authorized cross-vendor review was performed.