feat: expose web screen recording

[thymikee]

Summary

Expose web screen recording by reusing the agent-browser recording backend through the recording backend seam merged in #893.

Adds WebM output path handling, remote artifact projection, concrete web recording validation/record-only cleanup hooks, provider-backed tests, and web capability/help coverage.

Closes #885

Touched files: 16; scope is web recording feature only.

Validation

Verified after rebasing onto main with formatter, TypeScript, focused recording/web Vitest suite, and build/declaration bundling.

[github-actions]

Size Report

Metric	Base	Current	Diff
JS raw	1.3 MB	1.3 MB	+3.0 kB
JS gzip	437.8 kB	438.8 kB	+945 B
npm tarball	576.1 kB	577.0 kB	+880 B
npm unpacked	1.9 MB	1.9 MB	+3.0 kB

Startup median (7 runs, lower is better):

Scenario	Base	Current	Diff
CLI --version	27.6 ms	26.5 ms	-1.0 ms
CLI --help	48.2 ms	46.8 ms	-1.4 ms

Top changed chunks:

Chunk	Raw diff	Gzip diff
dist/src/record-trace-recording.js	+1.9 kB	+520 B
dist/src/9919.js	+344 B	+103 B
dist/src/cli-help.js	+298 B	+57 B
dist/src/9722.js	+114 B	+29 B
dist/src/session.js	+100 B	+26 B

[thymikee]

Review pass complete: I do not see a code blocker in the implementation path.

Checked against #885 and the production route: web now advertises record, record start/stop --platform web flows through the daemon recording handler into the managed WebProvider, the agent-browser provider delegates to record start/stop, stop waits for a finalized non-empty WebM file, and the remote artifact default is .webm. The focused tests cover command mapping, daemon start/stop, stable requested artifact paths, and missing-file failure.

Before calling this merge-ready, please add one live managed-web smoke result that actually creates the recording artifact, for example agent-device web setup, open a web session, record start ./artifacts/web-recording.webm --platform web --json, record stop --platform web --json, and close the session. If that is blocked, state the exact blocker and command/device context. The current validation is strong for routing and contracts, but it still mocks the backend boundary where the WebM file is produced.

[github-actions]

PR Preview Action v1.8.1
Preview removed because the pull request was closed.
2026-06-26 17:37 UTC