Repository navigation
Conversation
…-264-combined-candidate
…-264-combined-candidate
…ration and cleanup
Exact ec237 current-protocol host resultState: HOST_PASSED All five actual Node Realm/current-protocol cases passed: saved opt-out without re-enrollment; a newer choice during a held committed ACK; reentrant completion choice; encrypted Realm A→B→A; and lost ACK/tombstone inspection followed by the same consumed receipt through the actual queue. The last case completed no-confirmation/no-extra-CAS/no-enrollment/success=false and local-image/older-copy/account/subscription preservation assertions. Raw host case timings, in that order: 3149.154518 /1570.517512 /1330.530905 /1196.53884 /1078.32624ms; raw Node total 8933.812434ms. These timings describe host case execution; native startup/performance remains unverified. All four source receipts PASS, binding exact ec237/82f/29597/run/attempt, app tree Detailed durable receipt. GitHub-connector decoded UTF-8 job log75807bytes SHA256 The original bccf/control4755 run39851267317 4PASS/1FAIL remains preserved with its raw evidence. Its second fresh explicit worker assertion overreached the replay contract. The corrected source observes/delegates the original submission and retries the same consumed receipt; it changes no production behavior and waives no replay/preservation requirement. This supplies exact-source disposable host evidence for this package. A newer combined SHA needs its own affected checks. Native app UI/PIN/biometric/physical acceptance, full old295 compatibility, unknown5.2 integration and release readiness remain unestablished. No Mac, new native job, production/provider operation, merge/shared promotion, signing, upload/distribution, deployment or publication was used or authorized. |
Protected-copy Delete must preserve a newer consent choice or account session after its backend commit. This separate host-proof package adds five genuine boundary cases for saved opt-out, held ACK/new choice, reentrant completion, encrypted Realm A→B→A, and lost ACK/tombstone/no replay. It changes no product source, dependency, fixture, retired matrix or release behavior.
Exact source:
ec23775226ea8ded18858103a110ef61881bcf91, branchcodex/r5-protected-delete-completion-20261022, basesprint. Patch-only review after c8c4. Two additive files, ~4k code/test tokens, separate from the ~35k core/5.1 packages.Source syntax/whitespace and three unchanged original guard controls PASS. Independent review at8f33 identified held-worker disposal on an assertion failure and precise preservation wording; bccf releases/drains started workers while preserving the primary failure, checks backend account subscription separately, and says no re-enrollment after genuine setup. Coverage and limits.
First genuine hosted run failed at prior app bccf70d / private control4755c9da08fa6d04fdb11a24cd67f7861d177827: 39851267317, attempt1/job120077779383: 4 PASS /1 FAIL /0 skipped/cancelled/todo. All four exact-source checks, frozen inputs, real Realm and writable owned Mongo startup/verified removal PASS. Decoded raw SHA2569629211dfa5799720553d8208bf0758acfa8c8868fb0b0df7998615816485965. The lost-ACK test incorrectly started a new explicitly authorized Delete operation and treated it as consumed-receipt replay; no production defect was established. Subsequent assertions were not reached and are not credited.
Current ec237 captures the actual production receipt through a read-only delegating observer and submits that same consumed receipt to the genuine queue. It preserves all one-CAS/no-enrollment/no-success/account/local-data assertions and adds receipt provenance assertions. Independent full correction review, Node22 syntax/whitespace and three unchanged original guards PASS. Corrected genuine execution PASS:5 tests/5PASS/0FAIL/0SKIP/0CANCEL/0TODO, 39853694295, attempt1/job120086244943, exact app ec237/private control82fbd8dcc3793fc0d77b69e5a19f7ba308ff5866. All four raw source receipts and owned writable/removal/absence PASS; artifacts0. Detailed current receipt. Backend remains29597b27eeeb299205bf7d0555db0a90c38cc4be; prior failure remains immutable. Earlier local Realm NAPI preflight was unavailable; the hosted run installed the actual NAPI binding, with no mock or bypass.
These cases use actual Node Realm/production declarations/store/queue/crypto/HTTP/transactional backend with disposable public recovery material. Host storage is not native MMKV/process-relaunch/UI or physical-device evidence. Original2PASS/293FAIL and all earlier exact-source receipts stay unchanged; no combined-candidate pass transfer. Ordinary Delete success is already in the43-case proof; this is no all-copy purge, storage redesign or5.2 identification.
Codex local handoff
State: NEEDS_LOCAL
PR: #7111
Base: sprint
Head branch: codex/r5-protected-delete-completion-20261022
Head commit: ec23775
Goal and acceptance criteria: Five genuine current-protocol Delete completion cases with exact app/backend/control identities and honest owned cleanup.
Changes made: Two additive host proof/coverage files; no app/native changes.
Cloud checks: Node syntax/whitespace/3existing guardsPASS; independent source review/correction reviewPASS. Corrected exact ec237/82f/29597 host run39853694295 attempt1 actual5PASS/0FAIL/0SKIP/0CANCEL/0TODO, four raw-source checksPASS, owned Mongo writable/removal/absencePASS, artifacts0. Initial genuine4PASS/1FAIL at prior bccf/4755 retained. This supplies no native or newer-combined-SHA credit.
Required local checks: IOS, ANDROID
Local checks requested: No additional native build for this unchanged-app host-proof package; R5 native app acceptance remains tracked on#7068/#7107 using hosted macOS/Android. Genuine host backend proof completed only for exact ec237/82f/29597.
Risks / known gaps: Newer combined SHA requires affected checks; initial4PASS/1FAIL preserved; no native/physical/release credit, no5.2 handoff. No personal Mac dependency.
Release readiness: NOT READY. No merge/shared promotion/release signing/upload/distribution/deployment/publication.