Repository navigation
Conversation
Submitted-R4 caller proof completed — 24 October 2026App #7151, exact Private Relay #191, control
The earlier #7150/#19020-case receipt is R5-derived via #7091/b572/#7082. It remains separately scoped and is not R4 acceptance. No R5 product code was backported into this submitted-R4 proof. This closes the bounded20-case software batch. The original public2PASS/293FAIL result remains unchanged;275 original obligations still need their scoped mapping/disposition and are coverage backlog, not a new blanket release condition or reopening of owner-deferred scenarios. Prior submitted-R443+3 and production14-request acceptance remain separate. Existing signed artifacts were not rebuilt/resigned/resubmitted. Public release holds, store/artifact access, recorded native/physical qualifications and owner decisions remain unchanged. No merge, production operation, signing, store action or public publication occurred. |
R4 closeout readback — 24 October 2026Frozen submitted app source remains The mobile closeout still needs:
Completed evidence remains closed with its source scope: signed submissions, selected native subset/qualified carry-forward, Relay29597 production acceptance and14 checks, submitted-R443+3 paired proof, and the separate20-caller/14-control batch. Existing owner physical/recovery/Delete/C8/navigation deferrals remain intact; remaining275 coverage obligations are backlog rather than a new blanket release gate. Separate recorded follow-ups remain public CI/scanner disposition, backend Sonar configured-server connectivity (latest actual attempt still CONNECT_TIMEOUT), Desktop QR/distribution, SigningServer rules/runtime, and scoped installed-device acceptance. No release operation, shared-branch change or new native run was performed by this readback. |
Public R4 availability readback — 24 October 2026Apple's public US App Store listing now shows version2.6.4 available, corroborating the owner's existing App Store-updated iPhone report. This closes the uncertainty about public iOS version availability; it does not independently identify build620 or prove the signed artifact/source mapping. The displayed relative release date is not promoted into an authenticated release timestamp. The public Google Play listing shows an October7 update and the Desktop-pairing release note; it does not establish publication of submitted R4 build627. Current authenticated Android/store-build readback remains pending. Existing signed-file cloud access and final source/release closure disposition remain separate; no rebuild/resign/resubmission is requested. This was a read-only storefront check. No signing, upload, submission, publication, merge or release state change was performed. Current R5 test-infrastructure work is not a new R4 prerequisite. |
Current publication — 24 October 2026
Branch:
docs/r4-completion-evidence-20261022Commit:
3692edc94a2d3ccae26116048e88e2c262c707ddThe existing ledger is refreshed and pushed; no duplicate implementation or PR was created. Latest GitHub heads, comments, reviews, owner decisions and checks were read before editing. Original mobile/Desktop/SigningServer heads and approvals remain intact; R5 continues on its current source.
Validation on the published documentation update: whitespace and one-Markdown-file scope checks PASS; independent evidence/scope review PASS; local/remote branch identity verified and worktree clean. Previous5d6ab0ab had all five exact-head checks PASS. New3692edc94 has its own automatically scheduled checks; no old status is transferred and no manual rerun is requested.
Preserved 22 October publication evidence and source-qualified results
R4 records mixed submitted mobile builds, completed Relay/website deployment and unrun device acceptance. This documentation-only ledger reconciles mobile #7045, Desktop #100/#102 and SigningServer #6 against current source, comments, checks, artifacts and owner decisions. It keeps deferred recovery/Delete/C8/navigation cases explicit and preserves all running R5 work.
Completed cloud follow-ups
Exact remaining limits
iOS620/Android627 were already submitted; no rebuild, counter allocation or resubmission. Fresh authenticated Apple/Play status is blocked by absent cloud access. Latest posted console receipt is21October; the owner-reported installed iPhone2.6.4 is retained separately. Existing signed mobile bytes/PGP files are unavailable in workspace/GitHub/current CI/connected Drive. Relay deployment/hosted acceptance and website8/8 HTTP acceptance are completed; installed links/device/phone/signer checks retain their actual scopes. SigningServer#6 source/CI is complete, but admin approval-rule settings and deployed-service/compatibility evidence remain separate.
Validation: git diff --check PASS; documentation-only/existing producer-head preservation verified; independent evidence/scope review. Native tests are not required for this documentation-only PR. Initial documentation checkpoint5c18f31c full Tests/Lint/CodeQL/local-gate checks PASS; later documentation-only updates have their own current checks and receive no transferred exact-head status claim. No app/native/dependency/version/backend/CI gate inputs changed.
No merge, deployment, signing, store upload/resubmission, release distribution or public publication. Private QA retention and sanitized CI evidence are the only artifact copies created.