[build-tools] Stream web-preview session logs in the existing step

[gwdp]

Why

Users and developers would benefit of serve-sim stdout/stderr visibility into the existing web-preview session step

How

• Reuse the step logger without an extra preview phase.
• Bound retained output, redact credentials, and drain shutdown output before cleanup
• This is the shared foundation; agent-device, Appium and Argent logging follow in separate PRs on this stack

Test Plan

• CI passed on the current head.
• Tested the full stack locally with Gabe: EAS CLI, Universe API/workflow worker, build-tools and serve-sim 0.6.3 on an iPhone 17 Simulator. The website preview, remote Settings navigation and log ingestion worked.

Earlier and automated validation

Codex ran the focused checks: 174 focused tests, typecheck, lint and formatting passed. Claude found no correctness defect and independently ran the build-tools unit suite (1,882 passed, 8 skipped). Its follow-up coverage suggestion for failed/stalled tunnel closes is included and passes.

Earlier launch E2E covered Universe-generated steps through build-tools download/install/start to serve-sim on a real iOS Simulator, checking one app start, launch arguments and the deep link. Those runs used loopback cloud tunnel/reporting adapters and a pinned local build/device. The local website session used real ngrok tunnels; hosted EAS execution was not tested.

Screenshots

Authorship and LLM use

Gabe wrote the initial implementation, directed the iterations and requested the split once he was happy with the result. Codex made fixes, split the PRs and updated this description; Claude and Devin reviewed. The reviews led to redaction and shutdown refinements. Gabe reviewed the final code through #4601 and tested the local website flow for these logging changes.

[gwdp]

Codex implemented the logging split, credential-redaction and shutdown fixes, plus the recorder test correction, under Gabe's direction. Gabe reviewed the final code through #4601 and tested the local website flow. Current-head CI is green; the description preserves screenshots and distinguishes local from hosted evidence.

— Codex

[douglowder]

eas-cli now uses changesets for changelogs (#4580). The required "Check for a changeset" check fails on PRs that edit CHANGELOG.md.

To update this PR:

1. Revert the changes to CHANGELOG.md.
2. Run yarn changeset, select the changed packages and the bump type, and write the summary.
3. Commit the new file in .changeset/.

The release adds the PR link and the author to the entry. If this PR needs no changelog entry, revert the CHANGELOG.md changes and add the "no changelog" label.

[gwdp]

Rebased this layer onto main and moved its release note from CHANGELOG.md into its own changeset. Current-main behavior was preserved.

Validation: focused build-tools tests, changeset validation, changed-file lint/format and build-tools typecheck passed. No new native or hosted acceptance was run for this restack.

Published head: cec2a8004fc94ea3d1dd78bfe2faa5fe4c049f28.

— Codex

[github-actions]

✅ Thank you for adding a changeset!