479beecb6f
The per-PR OTA job published a bundle for every same-repo PR, including PRs that change the native surface. An OTA only carries JS, so on those PRs the published bundle does not represent the PR - it pairs the PR's JS with whatever native code the installed client already has. Those PRs need a native build, not an OTA. Gate publish-pr-ota on the fingerprint-native job's includes-changes output, and drop the sticky install-link comment when the fingerprint changes so a link from an earlier fingerprint-clean commit on the same PR does not linger. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019CbYttjV9ZCD4R9BHiqHFC