Skip to content

test(deploy): native auto-update apply/rollback execution proof — pending upstream denoland/deno#36150 #859

Description

@rickylabs

Part of #840 · successor to the execution-proof scope of #457 (Option-A rescope, owner-ratified 2026-07-18).

The beta.11 wave shipped the complete native-first thin-client stack (#452 generator, #841 SDK update seam, #842 bindings, #456 packaging + release server, #843 components) and the honest deploy-e2e suite (#457): install from native formats, HTTPS signed-manifest fetch, staged-detection UX, and remote-services discovery are all proven. The apply/rollback execution proof cannot run on any platform because Deno 2.9.3's bootstrap deletes op_desktop_verify_ed25519 from the op table (keep-list omission in denoland/deno#33441 — upstream bug filed as denoland/deno#36150; one-line fix, needs a Deno release).

Scope of this issue:

Labels/milestone rationale: the work is a re-run + un-tolerating of existing gates once upstream ships.

Evidence trail: .llm/runs/beta11-cli--orchestrator/upstream-op-verify-decision.md + upstream-op-verify-history.md + the G6 investigation (slices/g6-456-packaging/op-verify-investigation.md).

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions