Skip to content

ci: continuously check Desktop release handoff guard fixtures - #103

Draft
antuz123 wants to merge 1 commit into
codex/r4-desktop-pgp-handoff-20261022from
codex/r4-desktop-guard-ci-20261022
Draft

antuz123 wants to merge 1 commit into
codex/r4-desktop-pgp-handoff-20261022from
codex/r4-desktop-guard-ci-20261022

Conversation

@antuz123

@antuz123 antuz123 commented Oct 22, 2026 •

Copy link
Copy Markdown

The Desktop PGP handoff guard added by #102 currently runs its 12 fixtures only in the manual preflight. Run the same read-only fixtures during ordinary CI so future changes cannot silently remove its QA-run, source, packaging and asset protections.

This is a two-line CI addition on isolated branch codex/r4-desktop-guard-ci-20261022, stacked on unchanged #102 head 06233e6a576ae1c9d0a49a34c253b3e9354b9efc. Current source 23284ec1dd02b305355525290f2f8aa42cca54d0. The guard implementation, production release workflows, native code and original #100/#102 heads are unchanged. Integrate #102 first, then refresh this follow-up onto the integrated source and rerun checks. No merge, signing, deployment or release operation is requested by this PR.

Validation: Python unittest 12/12 PASS; git diff --check PASS. An independent existing cloud agent reviewed the exact two-line delta and guard test entrypoint, reran all12 fixtures, and found no blocking source issue. This is cloud-agent peer review, not a provider review or formal GitHub approval. No paid provider request was made. Native acceptance is unnecessary for this workflow-only change; original Desktop native/phone/hardware gates remain open.

Hosted CI39831840277/job120009709386 PASS:12 guard fixtures, ESLint, Prettier, Rust formatting and Clippy. It ran on source 23284ec1dd02b305355525290f2f8aa42cca54d0 when this draft initially targeted main 627c92a8d7b260047b5566b447685e9cfa7e0e15, with synthetic merge a6882cf28e8b2f9eac67633e9c32107881cd6891. The draft now targets #102's branch codex/r4-desktop-pgp-handoff-20261022, exposing only this two-line follow-up. Retargeting provides no new base-specific check; rerun after integration/rebase. The workflow has no pull_request trigger for arbitrary stacked bases. No original approval or source was replaced; no release/signing workflow ran.

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