Repository navigation
Conversation
Keep saved USDT wallets, receive addresses, chain reads, history, and backup recovery. Make Send show a pause message and warn before new deposits. Reject retired GasFree and swap credentials in release inputs and direct Android builds.
…-cloud-integration-20261022
…-cloud-integration-20261022
…-cloud-integration-20261022
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.
This prepares the missing 5.1 native Version History acceptance as a separate bounded package. Controlled stale/empty history states keep the actual account/shared version current; normal
index.jslogin must append one current installation observation, preserve both old provenance dates, avoid fabricated upgrade rows, and retain the observation date on another cold login. The helper restores exact original history rows before the next companion.Base:
3eb92fc8a622a3e09926d49f47243c163e32d009(includes core #7058 and 5.1 #7067). Patch-only review: 3eb92fc...b8abebb . Root integration/execution remains #7068/#7082; producer branches are untouched. This is not 5.2 and does not identify, interrupt or duplicate that active work.Actual Keychain/MMKV/Realm primitives stay on the owned device. No key/credential leaves the device process. Fixed CI entrypoints touch only VersionHistory, verify existing current account/Realm and known disposable PIN ownership, reject missing storage, retain one wallet, back up original non-secret history only, and purge the backup after restoration. The normal product entrypoint is unchanged. First observations must fit a device-local seed-to-read clock window, and repeated login must retain the same date.
The new runner requires root-owned Metro/app switching after successful key/PIN/credential acceptance and before Vault/account-count changes. Every stage verifies actual installed byte identity, records fixed phase names/proofs only, rejects unexpected account creation, and purges private UI output. No native workflow was dispatched by this package.
Validation:
Approximately 9.7k changed code/test tokens (24 files, 815 inserted lines including documentation), one feature acceptance package. Details and callback interface: docs/r5-native-version-history-acceptance.md.
Codex local handoff
State: NEEDS_LOCAL
PR: this draft
Base: sprint
Head branch: codex/r5-native-version-history-ui
Head commit: b8abebb
Goal and acceptance criteria: Hosted native controlled stale/empty history observation, old-date preservation, no duplicate/fabricated migration, unchanged current account version and wallet, exact history restoration.
Changes made: CI-only fixture/runner/flows and boundary controls; production implementation unchanged.
Cloud checks: 115 Node / 98 Python PASS; 10 Babel / 2 YAML PASS; independent scoped review PASS; native NOT RUN.
Required local checks: IOS, ANDROID
Local checks requested: Root wires the fixed callback into the isolated combined candidate and schedules hosted iOS/Android acceptance. The owner's personal Mac is not required.
Risks / known gaps: Native runner wiring and device execution remain unverified. Controlled history fixture is not an authentic historical installation/recovery or version migration. Backend compatibility, physical devices/biometrics and unidentified active 5.2 remain separate obligations. 5.1 and 5.2 are not established as integrated or tested together. No merge/shared promotion/signing/upload/distribution/deployment/publication approval is granted.