Skip to content

Observe bounded Android onboarding boundaries (C1) - #7140

Draft
antuz123 wants to merge 1 commit into
codex/r5-android-observer-fixed-review-base-20261022from
codex/r5-android-observer-marker-20261022
Draft

antuz123 wants to merge 1 commit into
codex/r5-android-observer-fixed-review-base-20261022from
codex/r5-android-observer-marker-20261022

Conversation

@antuz123

@antuz123 antuz123 commented Oct 22, 2026 •

Copy link
Copy Markdown
Collaborator

The completed1bc Android window passed startup/persistence/workers but failed the first full-product Start New assertion after a host Skip acknowledgement. The retained snapshot does not prove tap delivery or the cause. C1 adds fixed development-only observations at the existing onboarding effect, Skip handler, original synchronous reset return/throw and NewKeeper effect.

Exact head 69f64b16afc5bcfb98b6d14c2ff63db0eb9474b9, tree b5e37c1d31d758a8b28b3ef6a4643cf1b0c479c1. Nine files relative to fixed source-review join 8940d8601d65245ffbd1d42ad0095e8426579978. That join has parents B/#7139 and external #7131/044e, but exactly the frozen B tree; it is not a native/release candidate. Producer work and full ancestry are preserved. Source changes from044e are exposed across this C1 and successor C2, not silently attributed to A/B.

C1 has32,306 changed code/test characters, approximately8.1k tokens (chars/4). C2 separately exposes the failed-assertion snapshot/geometry capability; C1+C2 total65,402 characters/approximately16.35k tokens. All thirteen external source/control paths and adaptations remain reviewable in these two bounded packages.

The original reset receiver/arguments, one call, immediate return/error and existing listener/timer cleanup remain. Markers contain only fixed stages, capped four per stage/twenty per JS process; release/iOS calls emit nothing. The pure parser uses the already collected current owned-PID inventory and unchanged four-query E/F payload. It exports no PID, tag, timestamp, arbitrary message, route, account or error. Missing stages stay null/UNKNOWN, partial/foreign/malformed/capped input stays explicit and guest-clock freshness remains UNVERIFIED. Reserved message-start diagnostic frames are separate from runtime error counts; ordinary errors mentioning a marker later remain errors.

Exact source checks:53 Jest,428 Node and302 Python PASS, zero failures/skips. New helper strict TypeScript5.0.4/ESLint/format PASS. Existing screen lint15errors/4warnings matches baseline ordered rules/severity/messages; existing NewKeeper formatting failure is retained and baseline-equivalent. All2418 tracked regular blobs/modes clean after checks. Existing108 native command-call ASTs and74 timeout/error_details keyword AST values match frozen B. No new query/process, selector, flow, deadline, dependency, acceptance predicate or app-cause correction.

The historical1bc failed product sample still has zero complete samples and24of25 cells unrun; five worker helper pairs are not product timings. External044e native run39873063291 is a separate preserved window and supplies no pass to this head. Marker transport/actual cause are unverified. No native window is queued by this package.

Codex local handoff

State: NEEDS_LOCAL
PR: #7140
Base: codex/r5-android-observer-fixed-review-base-20261022
Head branch: codex/r5-android-observer-marker-20261022
Head commit: 69f64b1
Goal and acceptance criteria: Observe original Android boundaries safely, retain genuine failures and complete the exact combined-source feature matrix.
Changes made: Fixed Android development marker, bounded owned-PID parser, existing-query adapter and controls; unchanged navigation/UI behavior.
Cloud checks: Exact53Jest/428Node/302Python PASS, helper checks/raw2418clean; inherited lint/format failures retained. Native marker transport IOS/ANDROID NOT RUN on this head.
Required local checks: IOS, ANDROID, HARDWARE
Local checks requested: Coordinated hosted macOS/Android combined-source feature run after successor/source/capacity review; no owner's personal Mac requirement.
Risks / known gaps: Cause unknown, positive markers do not prove route/tap/visibility, guest-clock freshness unverified; full-product/Retry/key-PIN/companion matrix incomplete. Physical devices/signers NOT RUN, no owner deferral. No protected-base acceptance or release readiness/signing/upload/merge/deployment.

Independent full nine-file C1 source review CLEAR on exact69f64b1; additional actual-TS/privacy and parser controls pass. This does not transfer review/native evidence to a later source. Successor C2 completed separate pinned-Maestro contract/source review and is published as #7141; native visibility remains UNVERIFIED.

Fixed patch-only review diff: https://github.com/KeeperCommunity/bitcoin-keeper/pull/7140/files . Neither fixed base nor producer branches advance.

Successor snapshot package now separately published: #7141, exact65ecac52d2fc0107f4ebcc0e9f1e9f6c33de813c. Full source review is complete; native visibility remains UNVERIFIED.

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.

2 participants