fix(android): require a nonzero chunk before a recorder counts as ready
Summary
Fixes #4550. A rollover chunk counted as ready as soon as its file existed. When the device refuses a second concurrent screenrecord, the new recorder exits and leaves a 0-byte file. The rotation committed that chunk, the sequential fallback never ran, and record stop failed with artifact is not stable.
waitForReady now needs a non-zero size, as the readiness check did before #1724 moved it onto exists. A dead recorder with an empty file now fails the start, so the existing concurrent-start recovery runs. A recorder that stays alive still counts as ready after the bounded wait, as before. If the sequential start also fails, the rotation gives today's typed error.
Partial-recording return and the close/claim path are unchanged.
2 files: chunks.ts and runtime.test.ts (one new case; the SIGINT case now counts calls after start). No scope expansion.
Validation
Base d78be6c88, head 5630ceb28.
pnpm exec vitest run --project unit-core packages/platform-android/src/recording/runtime.test.ts: base 1 failed, 16 passed; head 17 passed.
pnpm check:quick: passed. pnpm check:affected --run --base upstream/main --head 5630ceb28 (exactCommit: true): format, lint, typecheck, layering, fallow and build passed. vitest-related failed by 5 s timeouts across 67 provider files on a heavily loaded host. android-recording.test.ts alone times out on base (6 of 10) and head (7 of 10), with no assertion failure. CI owns these.
No device run: the defect needs a device that refuses a second recorder, and I had none.
![Autofix with [code]smith](https://pr-comments-assets.blacksmith.sh/codesmith/autofix-with-codesmith-dark-3x.png)
Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.