fix(mobile): parse EAS fingerprint JSON

[juliusmarminge]

Problem

The production OTA workflow pipes eas fingerprint:generate --json directly into jq. EAS still writes a human-readable environment notice to stdout before the JSON document, so the workflow fails with a parse error before publishing an OTA.

Fix

Discard the stdout prefix before the JSON document, then require a non-empty string fingerprint hash before querying compatible production builds.

Impact

Production OTA runs can compute their environment-aware fingerprint and continue to compatibility checking and publication.

Validation

• Ran the exact EAS fingerprint-to-jq pipeline locally
• vp fmt --check .github/workflows/mobile-eas-production.yml
• vp lint --report-unused-disable-directives
• git diff --check

Implemented with Codex (GPT-5) in T3 Code.

Note

Fix EAS fingerprint JSON parsing in mobile EAS production workflow

The eas fingerprint:generate command sometimes emits non-JSON lines before the JSON object. The workflow now strips any leading non-JSON output via sed before piping to jq, and the jq filter is tightened to -er ".hash | select(type == \"string\" and length > 0)" so the step fails explicitly if no valid hash is extracted.

^{Macroscope summarized 0907fdf.}

---

Note

Low Risk
GitHub Actions-only change to shell parsing in the mobile EAS production workflow; no app runtime, auth, or data paths.

Overview
Fixes production fingerprint-gated OTA when eas fingerprint:generate --json prints a leading environment notice on stdout, which broke direct jq parsing and stopped OTAs from publishing.

The workflow now keeps only output from the first { (sed -n '/^{/,$p') before jq, and uses -er with a filter that requires a non-empty string .hash so the step fails clearly instead of continuing with a bad fingerprint.

^{Reviewed by Cursor Bugbot for commit 0907fdf. Bugbot is set up for automated code reviews on this repo. Configure here.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 553b8e12-19ff-4a0d-9920-7233162bb71d

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	11.3 KiB	11.3 KiB	+8 B (+0.1%)	15.1 KiB	✅
Codex	Thread snapshot wire	5.5 KiB	5.5 KiB	−4 B (−0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	5.9 KiB	5.9 KiB	+12 B (+0.2%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	49.7 KiB	49.7 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	16	16	0 (0.0%)	21	✅
Claude	Total thread wire	11.3 KiB	11.3 KiB	+6 B (+0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	5.5 KiB	5.5 KiB	+12 B (+0.2%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	5.9 KiB	5.9 KiB	−6 B (−0.1%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	50.6 KiB	50.6 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	16	16	0 (0.0%)	21	✅

Baseline: d440442 · PR result: 0907fdf · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 94.6 KiB
• Claude decoded thread snapshot: 95.4 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.