Skip to content

refactor(runtime)!: enforce durable protocol v3 boundaries #586

Description

@WH-2099

Problem

The latest Driver, Codex app-server, ACP, Claude Agent SDK, and Cloud Agent boundaries changed payloads, lifecycle behavior, generated types, process ownership, and release requirements.

The Mosoo Draft currently pins an older Driver checkpoint and does not yet validate the latest strict protocol version 3 contract.

Goal

Integrate protocol version 3 as a schema-first durable boundary across Driver ingress, runtime state, persistence, artifacts, GraphQL, AG-UI, reconnect hydration, Web UI, and deployment safety.

Current status

Acceptance status

  • Driver publishes a strict protocol version 3 contract.
  • Driver latest-SDK lifecycle, cleanup, and generated bindings pass locally.
  • Rebase the Mosoo Draft onto current main.
  • Pin the latest durable Driver commit.
  • Adapt and revalidate every Mosoo protocol version 3 boundary.
  • Cloudflare Sandbox provides an atomic writer-freeze or forbidden-path backup guarantee.
  • A real-content race test proves transient credentials cannot enter a backup.
  • Final Mosoo CI is green before the Draft is removed.

Release constraint

Do not deploy or merge the Mosoo implementation while the Driver pin is stale or Cloudflare Sandbox cannot atomically exclude transient credential paths from backup capture.

Related work

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions