Skip to content

test(r5): isolated production-worker native storage witness - #7071

Draft
antuz123 wants to merge 239 commits into
sprintfrom
codex/r5-native-feature-probe
Draft

antuz123 wants to merge 239 commits into
sprintfrom
codex/r5-native-feature-probe

Conversation

@antuz123

@antuz123 antuz123 commented Oct 22, 2026 •

Copy link
Copy Markdown
Collaborator

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

Behavior and limits

  • Build-time AST extraction fails on missing/ambiguous selected definitions and records each containing source module's SHA-256.
  • Five disposable cases test setup offline/error/retry wallet-count preservation, deletion references including hidden/canary/archive records, native rollback on a missing later target, and stale A-to-B-to-A worker rejection. A sixth process reopens all files, checks counts and removes fixtures.
  • Explicit adapters control transport, generation, dispatch, database selection and the backup local-commit boundary. Invalid public sentinel records contain no valid seed/private key/address. No remote backend operation or Verified-backup assertion occurs.
  • JSON evidence contains fixed identifiers, source hashes/function names and five raw probe/worker timing pairs. Those timings are not full-product startup/first-wallet UX measurements; a separate product flow must supply those.
  • These scenarios do not prove product UI/navigation/privacy, PIN/biometrics, account login, cryptography, current protected-backup protocol compatibility, old-schema migration, physical devices or release readiness. Keep those acceptance rows open.

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 head 486810052f90550d55dd6ddd541ff53ebd875caa before 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.
  • Babel transformation of both native entry/core modules: PASS.
  • Prettier checks and git diff --check: PASS.
  • Native build, iOS Simulator, Android emulator, backend integration and physical device: NOT RUN for this package. No acceptance transfers from another SHA.

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.

antuz123 and others added 30 commits September 25, 2026 21:28
Enable the release branch test trigger and repair the inert recovery provenance fixture exposed by that run. No production app code changes.
redkeep-agents and others added 27 commits October 13, 2026 05:31

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants