# Native evidence attempt — 19570 / 24583

Outcome: prerequisite build failed; no native evidence captured. No conclusion about the PR's runtime correctness.

Repository: [replacement #24583](https://github.com/pingdotgg/t3code/pull/24583), [original #19570](https://git.cafe/pingdotgg/t3code/pulls/19570).

Workspace used: `/home/ubuntu/wt/pr-19570` only. Fresh scratch: `/tmp/ev-19570/native`. Linux x86_64, head `e810a33cf8114e5c4e76eeffe8ea299ef8466b71`, base `3cc31ed27c8956b36cee35a50509fb7c6869592b`. No source edits, commits, pushes, PR comments, edits, or watch calls. No fleet/environment links. No live userdata reads or writes.

## Actual prerequisite attempt

EAS availability was successful: `{"available":true,"accountName":"pingdotgg"}`. Absence of local adb/android-emulator/eas/agent-device executables was not treated as cloud unavailability. CLI run through npx.

From `apps/mobile`:

```sh
npx --yes eas-cli@latest fingerprint:generate --platform android --non-interactive --json
npx --yes eas-cli@latest build --platform android --profile preview --non-interactive --no-wait --message 'Thread sync recovery 19570 e810a33cf8 native evidence'
```

Unprofiled local fingerprint: `0e32279a0cc1c96d42dd70a58b003df4151f50cf`; this is not the preview build fingerprint. Recent finished preview:dev builds had different fingerprints and older source commits; they were not installed or used as final evidence. Recent production artifacts were store builds, not chosen for simulator proof. A prior base preview build had also failed in Configure expo-updates.

215 MB current-head archive uploaded. Metadata upload emitted `Failed to upload metadata to EAS Build`, `Request failed: 400 (Bad Request)`, but a build was created, so this warning was not incorrectly treated as fatal.

[Fresh current-head Android preview build](https://expo.dev/accounts/pingdotgg/projects/t3-code/builds/ea71f0f5-e390-4bb7-868e-e20052ead7f3) reached prebuild then ERRORED in CONFIGURE_EXPO_UPDATES. Build metadata gitCommitHash equals requested head. Actual failure:

```text
Runtime version mismatch:
- Runtime version calculated on local machine: 0f68ef9bc1d2cb2ee19157b26c09d03a54607448
- Runtime version calculated on EAS: 72d762c4dc8d8b1b1f6871ed0f259e123a4c88d2

This would cause any updates published on the local machine to not be compatible with this build.
```

No APK produced. No cloud simulator session started, so none needs stopping. No Metro started. Own scratch server was started on port 60281 with `--base-dir /tmp/ev-19570/native/home`, PID captured at spawn, then stopped by that captured PID. Other servers were untouched. No .env.eas-simulator was created. The failed build is terminal, not pending; no active build needs cancellation. Private EAS responses/logs remain local and are excluded from this public audit.

## Coverage

Captured M1 rows: **none**. Cached messages plus sync error, failed pill without button semantics, foreground recovery, new-session recovery, genuine connection-error button, and creation/content/connection precedence controls are **unverified on Android and iOS**. No native screenshots, temporal recordings, base/head pair, or pixel diffs exist from this attempt. Web evidence was not reused. Source hashes in provenance.json describe local checkout files, not a loaded native bundle.

## FRICTION

Cloud access works. The concrete blocker is the current preview build's local/cloud runtime fingerprint mismatch, not local simulator tooling or the disabled Device panel. Resolving the build configuration/environment mismatch is needed before a fresh installable native artifact and M1 capture. The attempt stopped after this concrete build failure rather than idling through the full 35-minute budget. No modifications to source or build policy were made to bypass it.