fix(android): retain foreground close fence evidence
TH
3h ago+246+246+012345678901234567890123456789-13-13-01234567890123456789
Summary
Retain bounded Android foreground-close probe observations and timings in request diagnostics, including when a probe throws. Document the JSON fields and request diagnostic in close help and troubleshooting. Five files changed. The two-second fence, deadline, queries, polling, and launch/stop decisions remain unchanged. Android smoke run 43968647877, job 133654642455, associated with #4615, timed out at this fence; its cause remains unproven.
Validation
- Base
31fc8dfb079d7eac164651a98262fc9b5ba1c6fa; heada13f5f6ee6f3a722ad695a7376216c3357fb22bc. Exact affected: 11 passed, 8 skipped, 1 deduplicated; exact commit, unchanged checkout. Coverage and device lanes remain GitHub-owned; provider integration was deduplicated. - Full format, quick checks, and rendered close help passed. Earlier runtime head
ad488cc1passed 29 focused tests and independent source review; the documentation follow-up was authored and cold-checked by the coordinator, without a fresh independent all-range review. - Probe and daemon artifact boundaries were tested separately; upload path was traced in source. End-to-end composition and live-device results remain unverified. Changed-head CI is pending.
![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.