Repository navigation
Conversation
…-264-combined-candidate
…-264-combined-candidate
Android Publisher API read at 2026-10-12T14:27:41Z for io.hexawallet.bitcoinkeeper: production 2.6.3 (626), highest uploaded bundle 626 across all listed tracks. A temporary edit was deleted without commit. iOS evidence remains stale and release preflight still fails for iOS.
…ration and cleanup
Fixed Android metadata readout — terminal resultReader head: Both source guards passed for the exact reader head/tree. Official target source/workflow/job/artifact admission, original ZIP size/digest/layout and startup-shape selection completed before the pinned privacy validation rejected the projection. No sanitized observation payload was released. The owned private-file cleanup returned without an error; no raw artifact, UI or log text was logged. A source-only comparison against the previously retained safe startup facts reproduced one finite admission mismatch: the old public-vocabulary policy does not include the fixed Create a passcode assertion failure receipt. This explains a reader rejection boundary; it does not identify the app startup cause, prove that this is the only rejection in the complete retained observer, or justify relaxing the privacy policy. Original Android source |
The Android-only diagnostic at exact
3f4e8127e3698accd3760a4a039448964a5285a4built successfully but failed the initial Create a passcode assertion before reaching the Skip-target experiment. This isolated Linux reader inspects the existing artifact's separate typed Metro startup observations; it makes no app change and does not rerun native work.The reviewed incremental change is exactly six added
.github/and documentation paths over reader source718fa96e9e5d4949ddf51dbb9502e95481395182. This draft targetssprintfor durable review; inherited unmerged ancestry is not a claim of a six-file total sprint diff.The fixed target is run 40085793409 / attempt 1 / job 120848340201, workflow
f83a9a8b182dd8276a732ee2b6338fb6f845640a, artifact 12557603923, 6,451 bytes, SHA-256f3553f9632eff7bd25f2315c8fb0e5429132455ea0af7d5293d4e4c7cfd8fd40. Exact official source/workflow/job/attempt/artifact joins are checked before and after decoding. The original canonical ZIP, digest, pinned privacy kernel/policy and exclusive private-file cleanup remain enforced. Output omits commands, toolchains and hierarchy; only fixed startup facts are projected.Validation: 33 Python controls and 24 Node controls PASS, including new 9+9 controls; independent peer and coordinator reviews CLEAR; actionlint 1.7.12 and whitespace/source fences PASS (shellcheck/pyflakes unavailable). Actual target artifact bytes have not yet been read; the push-triggered readout will record its own result. No native label is requested.
Codex local handoff
State: NEEDS_LOCAL
PR: this draft
Base: sprint
Head branch: codex/r5-7158-android-startup-readout-20261024
Head commit: a9c540b
Goal and acceptance criteria: Read only the fixed completed Android metadata artifact under exact source and privacy constraints. Preserve original startup failure and unknown cause.
Changes made: Six added reader/workflow/test/documentation paths over exact reader718fa96; no production app, native, dependency, canonical worker or acceptance changes.
Cloud checks: 33 Python /24 Node PASS; actionlint and source/whitespace checks PASS; peer/coordinator review CLEAR. Fixed Linux metadata readout selected by this push; result pending. Native app execution NOT RUN by this proposal.
Required local checks: IOS, ANDROID, HARDWARE
Local checks requested: NONE for these incremental metadata-reader paths. Inherited app/platform/device obligations remain explicitly unsatisfied by this readout and must stay separate.
Risks / known gaps: Original #7158 startup FAIL; persistence/workers/product and Skip experiment NOT RUN. Cause UNDETERMINED. Outer HTTP status and reporter/process observations do not establish UI readiness or full multipart bundle success. Capped/missing rows do not prove absence. No trusted native acceptance, merge, signing, upload, distribution, deployment or release approval.