Skip to content

ci: validate preserved Desktop QA artifact on cloud macOS - #104

Draft
antuz123 wants to merge 6 commits into
codex/r3-desktop-pairingfrom
codex/r4-desktop-cloud-smoke-20261022
Draft

antuz123 wants to merge 6 commits into
codex/r3-desktop-pairingfrom
codex/r4-desktop-cloud-smoke-20261022

Conversation

@antuz123

@antuz123 antuz123 commented Oct 22, 2026 •

Copy link
Copy Markdown

The existing approved Desktop QA artifact now has cloud macOS source/hash/code-signature and native launch evidence without rebuilding or using a personal Mac. Native launch and live-channel welcome readiness PASS. QR navigation/channel packet smoke remains BLOCKED in hosted GUI automation; the cause is unproved.

Stacked on unchanged #100 source ef050663d33be51f25fb10310d5a0549b111e273; current tooling head 72c56adcb07fbe020094bee3625d899dd0ba8460. Only three new cloud acceptance tooling files are added. Original #100/#102 heads, #100's exact-source approval, runtime and QA artifact bytes are preserved. The distinct workflow runs only on this isolated branch, has contents/actions read permission, and cannot activate the legacy PGP release/dev-release trigger. No signing secret, build, re-sign, deployment, release upload or publication path is included.

Exact tested artifact: 11615331902 / run 37928395053, QA 0.2.6-qa.1, separate identity com.keeper.desktop.r3qa. Outer ZIP SHA-256 2a3ca33dd9a539323f41639d98fb36ab8d2cdc670f1b17b20f861b3528eaeea5; enclosed ZIP 9ae0c39eefafd85a9234bf7a599f75e3b13a481ab0ad7f9418eee66990c34a69; executable 13e252b7a7f339d24e327d8d14d7956946f21b929c037970edffa9e6e90fcb70. Source/version/identity/live-endpoint checks and strict deep code signature passed before native launch. The original QA archive also has private durable retention with complete byte readback/hash comparison verified; its private location is omitted here. QA is ad hoc signed and is not a production notarized/distribution artifact.

Final cloud run 39834105821 / job 120017732757 on tooling 72c56ad: artifact verification/codesign, Swift/sender preparation, native process launch and live-channel Get Started welcome PASS. Hosted macOS 26.6.2 / build 25G83 arm64, image macos-26-arm64 20261013.0424.1. Native event posting, accessibility and screen capture permissions were all TRUE; exact app PID activation returned TRUE. Fresh settled OCR bounds and one welcome-only button retry still left Get Started visible, ScanMe absent and QR count 0. State BLOCKED_OR_FAILED, fixed label QR readiness/click unavailable. No fresh QR was obtained and ZERO test packets were sent. No app defect or pairing pass is inferred. Sanitized artifact 12450860782 expires 21 November 2026.

Preserved earlier harness results:

  • 39832690264, tooling 49927b13: artifact/codesign and native process launch PASS; screen-reader/tool failed with the VM scaler unavailable. No QR or packets. Sanitized artifact 12449926096.
  • 39833213888, tooling cd36015f: CPU-only Vision correction; artifact/codesign, launch and live welcome PASS; QR readiness/click unavailable. No packets. Artifact 12450201120.
  • 39833708602, tooling ed2220bf: same PASS subset; read-only diagnostics established all permissions TRUE while welcome persisted, ScanMe absent and QR0. No packets. Artifact 12448519823.

An independent existing cloud agent reviewed the original three files and privacy/provenance followups before execution. A different existing cloud agent independently reviewed each narrow CPU-only, fixed-diagnostic and exact-PID/fresh-button followup before its push; no blocking source/safety finding. Node syntax, YAML parse and diff checks PASS; final Node syntax/diff checks were independently rerun. Swift compilation and sender setup passed on the actual hosted Mac. This is cloud-agent source peer evidence, not a provider review or formal GitHub approval. No paid provider review request was made.

Next action: use interactive cloud QA or a demonstrated harness correction to drive Get Started and complete exact-source QR/channel smoke. The configured packet tests would cover disposable TESTNET altered tag/plaintext/authenticated-malformed/valid ADD_DEVICE/LEDGER, stopping before Continue; they have NOT RUN. No raw screenshots, QR keys/rooms or app logs are uploaded. Only fixed labels, booleans/counts and sanitized outcome/provenance files are retained 30 days.

Paired current-mobile iOS/Android camera scanning, reconnect/cancel/retry/duplicate/rotation matrix, physical signer/address/policy checks and PSBT round trip remain NOT RUN. Owner-deferred mobile cases remain explicit and are not reopened or passed. Production source/version/platform selection, signed/notarized packages, PGP checksum/assets/archive and explicit operation-specific authorization remain separate: the current inventory has no release/draft bound to ef05066 and no 0.2.6 production release; published 0.2.5 is historical. No merge, production signing or distribution is authorized by this smoke.

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