Skip to content

docs: reconcile R4 submissions, acceptance and R5 source baseline - #7092

Draft
antuz123 wants to merge 5 commits into
sprintfrom
docs/r4-completion-evidence-20261022
Draft

antuz123 wants to merge 5 commits into
sprintfrom
docs/r4-completion-evidence-20261022

Conversation

@antuz123

@antuz123 antuz123 commented Oct 22, 2026 •

Copy link
Copy Markdown
Collaborator

Current publication — 24 October 2026

Branch: docs/r4-completion-evidence-20261022
Commit: 3692edc94a2d3ccae26116048e88e2c262c707dd

The 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.

  • Adopt already-published #7151/private #191: submitted R4 runtime with only two proof files and a map added, 20/20 caller proofs +14/14 controls PASS, zero skips, run40066799617. Remaining275 obligations are engineering coverage backlog, not a new blanket release gate, per owner6380553077. R5-derived32/20-case receipts are not transferred.
  • Desktop original QA Actions artifact11615331902 now returns404 after expiry. The existing private retained archive remains available;24October metadata confirms20,064,440bytes/owner-only access. Its prior full byte/hash verification remains dated22October. Unchanged#104 cannot download the expired Actions input if rerun.
  • Native#7149 is coordinated separately: no new native build, acceptance attempt or workflow rerun was started by this resume. No merge, deployment, signing, store action or public release.
  • Store readback/original signed mobile files, public-v2/CodeQL findings, separate Sonar server-connect timeout, Desktop QR/distribution and SigningServer rule/runtime evidence remain unresolved. Deferred recovery/Delete/C8/navigation/physical scope is unchanged. docs: qualify submitted R4 source baseline in R5 integration #7090 retains its fixed historical review base; do not blindly apply it to moving R5.

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.

Copy link
Copy Markdown
Collaborator Author

Submitted-R4 caller proof completed — 24 October 2026

App #7151, exact 93489d8a8eeb5d99f85ff8aaf74fb447795a56a5, adds only two proof files and one map to submitted R4 1d8a86a7462d935cbd0e28b857934b5718c152fc. The private controller verifies that ancestry and exactly those three additive paths; existing runtime/native/dependency/configuration/fixture files are unchanged.

Private Relay #191, control fe45a8c895c0ab9579ec6e55b0549e708da0e1d1, selected current Relay29597 through the unchanged reviewed #161 admission preload. Run40066799617, job120791660796, completed SUCCESS:

  • 20/20 genuine wallet/label caller cases PASS, zero failures/skips/cancellations/todo.
  • 14/14 raw-source/cleanup negative controls PASS.
  • All three raw source/strict R4 purity checks, frozen dependencies/six patches, actual encrypted native Realm, transactional loopback Mongo and verified owned cleanup PASS.

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.

Copy link
Copy Markdown
Collaborator Author

R4 closeout readback — 24 October 2026

Frozen submitted app source remains 1d8a86a7462d935cbd0e28b857934b5718c152fc / #7045, still draft/open/unmerged. The current R5 cloud-testing failures do not create a new R4 native prerequisite.

The mobile closeout still needs:

  1. Fresh authenticated Apple/Play status reconciled with the existing build620/627 submission receipts and the owner's report of an App Store update to2.6.4. The latest posted authenticated console receipt remains21October; it is historical rather than current provider status. A bounded official-notification email check recovered no newer evidence and does not establish current store state.
  2. Read-only access to the existing signed IPA/AAB/APK and PGP files in approved private cloud storage, checked against the established receipt. Exact file references/access are missing. Do not rebuild, re-sign, resubmit or allocate counters to recover these files.
  3. Recorded owner disposition of the existing public-release hold and any intended final closure/publication/merge action. Backend acceptance supplies none of those approvals.

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.

Copy link
Copy Markdown
Collaborator Author

Public R4 availability readback — 24 October 2026

Apple'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.

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