Skip to content

Bootstrap hosted native validation with private diagnostics and draft guards - #7063

Draft
antuz123 wants to merge 1 commit into
sprintfrom
codex/cloud-bootstrap-privacy
Draft

antuz123 wants to merge 1 commit into
sprintfrom
codex/cloud-bootstrap-privacy

Conversation

@antuz123

Copy link
Copy Markdown
Collaborator

This separates the hosted-native infrastructure from #7060's app/dependency changes and closes the diagnostic leak reproduced in failure_details(). Exported failures now use fixed categories, with synthetic adversarial privacy regressions and a verified immutable Android emulator action pin.

Keep this PR in draft. Marking it ready enables native jobs and requires separate authorization. This PR does not install a trusted baseline or grant native/release acceptance.

Scope and source

  • Base sprint: def0d6a90c80287edb4f58ae272cbfc340f00d73.
  • Head codex/cloud-bootstrap-privacy: 0984c5b97e7e8326d6856ba662274ecf325e5e0f.
  • Infrastructure source ci: hosted native validation and exact-head evidence gate (#7059) #7060: d865ca9c4f91532a1524443cc6da42d8d7b07e1a. Its gate implementation is unchanged; original gate contracts remain, with added skipped-draft/latest-attempt coverage.
  • package.json, yarn.lock, ios/Podfile.lock and ios/hexa_keeper/AppDelegate.mm remain byte-identical to sprint. No R4 or app scenario matrix work is included.
  • Emulator action pin: 1dcd0090116d15e7c562f8db72807de5e036a4ed, verified against the upstream tag's peeled commit.
  • Reviewed full-index patch SHA-256: 3452e2674eadea6822cd88eb7608f480a00b62b16d974904ee7f9890c0a42bed. Committed diff matches it exactly.

Draft behavior

Both hosted iOS and Android jobs require a pull-request event with an explicitly false draft value, before runner allocation. Draft, missing and malformed values skip the entire jobs, including caches and artifact uploads. There are no reusable or manual native entry points in this bootstrap.

Opening, reopening or updating a draft retains CodeQL, CI Lint/Tests, host contracts and the existing trusted local-validation gate. The draft Tests install uses yarn install --frozen-lockfile --ignore-scripts so root prepare cannot invoke CocoaPods; install/test failures still fail Tests. Ready/non-PR installs keep their prior behavior, and ready_for_review reruns normal CI. Lint's existing script-disabled install remains.

converted_to_draft requests cancellation via the native workflow's existing PR concurrency group and starts a skipped run; cancellation is best effort and cannot undo work already started while ready. Skipped native jobs never supply native/hardware evidence or reuse an older passing attempt. The existing documentation/.github exemption is not native acceptance.

Validation and independent review

  • PASS: node --test .github/tests/*.test.cjs — 53 tests.
  • PASS: python3 -B -m unittest discover -s .github/tests -p 'test_*.py' — 35 tests.
  • PASS: JavaScript/Python syntax, changed YAML syntax, whitespace/scope checks and clean patch application to the base.
  • Privacy negative control: all five adversarial tests detect the original ci: hosted native validation and exact-head evidence gate (#7059) #7060 exports (168 assertion/subcase failures; zero execution errors).
  • Independent review: no remaining findings after fixing the YAML action-pin parser bypass; the final draft-policy review independently passed 46 focused gate/policy tests.
  • NOT RUN: workflow semantic lint (actionlint unavailable), app dependency installation/app tests locally, native compilation, simulators/emulators, physical devices/signers, and live ready-to-draft cancellation.
  • Environment setup's frozen app dependency installation failed and remains unresolved. Host tests use synthetic fixtures/mocked native commands; they do not validate app/native behavior. No dependency repair, non-frozen local installation or native lifecycle execution was used.

Publication-time cost and trigger check

The repository is public. Draft-triggered checked-in jobs use standard ubuntu-latest or ubuntu-24.04 runners, covered by GitHub's free public-repository standard-runner policy. No new paid service or active artifact/cache expansion is introduced for draft publication: the added explicit cache/upload steps are inside skipped native jobs; active setup-node steps specify no cache and the app manifest has no packageManager/devEngines activation. Existing CodeQL remains unchanged. The release-only RAG workflow is not triggered. A push to this head branch without a PR matches no checked-in push workflow. This check does not treat every GitHub service as free.

Adoption order and boundaries

  1. Review this bootstrap; only separately approved installation on protected sprint can establish the trusted workflow/harness baseline. Candidate infrastructure cannot authorize itself.
  2. Reconcile the excluded app/dependency baseline separately without bypassing frozen installation or trust/failure/hardware gates.
  3. Separately restack ci: reusable cloud release acceptance foundation (Phase A, #7061) #7062's Phase A delta (59c821ce195a5c063d99045fd97b5ac605433f62) after adoption. Do not merge its existing ci: hosted native validation and exact-head evidence gate (#7059) #7060 ancestry wholesale. Preserve privacy categories/regressions and pins, and add the draft guard at both keeper-release-acceptance.yml caller jobs and keeper-native-platform.yml worker while retaining provenance/R4 checks. Those future paths are outside this patch.
  4. Obtain separate authorization for actual native validation after baseline reconciliation. Exact-source provenance, explicit failures and hardware requirements remain binding.

No merge/auto-merge, workflow trust approval, #7062 restack, manual Actions dispatch, native run, paid resource, signing/distribution, deployment or release publication is requested by this draft. R4 and the owner's Mac remain untouched; Phase B is outside scope.

See bootstrap preparation and adoption notes and hosted-native validation.

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