Repository navigation
Conversation
Enable the release branch test trigger and repair the inert recovery provenance fixture exposed by that run. No production app code changes.
(cherry picked from commit f225c19)
This was referenced Oct 22, 2026
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
R5 setup/deletion worker regressions currently use modeled storage boundaries. This separate CI-only package extracts the current candidate's unchanged production workers and runs their guards over the actual Realm schemas, native Realm and MMKV in a disposable six-process probe.
Refs #7059, #7061, #7065. Native state: NOT RUN / NOT VERIFIED. No release-readiness claim.
Source and bounded review
984e01eed674be30672012e3a0ca380b64225969.c1c4b803039b61b940373c4dc9d08473cf25e042from fix: protected-backup follow-up and accurate Version History #7067; includes core R5: safe key deletion and startup fixes on submitted 2.6.4 source (draft) #705877b72da29ac5f2cdf3f51c9a0e9f3fd1c2af7238and released R41d8a86a7462d935cbd0e28b857934b5718c152fc..github/files, approximately 7.5k changed code/test tokens; two related worker scenario areas. Producer branches and dependency/native/release inputs remain intact. Integrate with the separately reviewable hosted runner package before executing this probe.Behavior and limits
Native-job scheduling correction
A separate minimal guard commit reserves the inherited standalone Android diagnostic for explicit workflow dispatch and sets
cancel-in-progress: false. The first PR-open event had already started Android diagnostic run 39732888592 on the former head486810052f90550d55dd6ddd541ff53ebd875caabefore the scheduling hazard was identified. That run is preserved; it is not acceptance for this new head. No run was cancelled. The coordinator will schedule the combined native candidate after existing work finishes.Actual checks on this head
node --test .github/tests/r5_features.test.cjs: 6 PASS, zero failures/skips; host-only extraction/schema/session/phase/scope contracts.git diff --check: PASS.Cloud native handoff
State: NEEDS_HOSTED
Head branch: codex/r5-native-feature-probe
Head commit: 984e01e
Required native checks: IOS, ANDROID
Next action: incorporate this bounded patch into the isolated R5 integration candidate with the reconciled hosted runner, regenerate the selected workers from that exact checkout, execute both hosted platforms sequentially, validate safe JSON plus unchanged artifact identity and retain raw evidence. Root coordinator schedules native jobs; this PR does not dispatch them. Latest owner cloud-first instructions supersede the old personal-Mac route; no personal Mac is requested.
No merge, shared-branch promotion, release signing, upload, distribution, deployment or publication is authorized or performed.