Track remaining downstream runtime contracts for distribution convergence

[ChatGateAI]

Problem

Downstream production runtimes need several behavior contracts that are not provided together by the current official Eve release (0.27.12). ChatGate currently isolates these source deltas in one digest-qualified Eve distribution, but each delta needs an upstream convergence owner so the downstream patch can be removed capability by capability.

#1315 already tracks the related durable child invocation, parked continuation identity, and proxied input-response authorization family. This issue is the umbrella tracker for the remaining independently removable capability families.

Capability families still requiring upstream convergence

• Session token-limit policy — authored input/output session budgets, including an explicit uncapped value, are compiled and enforced at the runtime boundary. Related direction: Uncapped sessions by default: remove session token limits, add caller-scoped run budgets #551.
• Framework Sandbox policy and public resolution — authored runtime contexts expose a fail-loud Sandbox capability with stable resolved identity/summary; absence is distinguishable from backend failure.
• Nested Sandbox retry and template recovery — nested/subagent execution can recover from missing or expired template/snapshot state without changing session ownership, while ambiguous cleanup fails loud.
• Sandbox lifecycle reconciliation and release — release-tagged template/session resources have an observable lifecycle, reconciliation retains exactly the live generations, and terminal/active handles are untracked and released without leaking or deleting ambiguous resources.
• Typed turn completion — terminal completion has one typed result contract and cannot be confused with a parked/waiting turn.
• Stream supersession — reconnecting or replacing a stream has explicit ownership and abort semantics; an older stream cannot continue consuming the same session silently.
• Existing-session continuation identity — a continuation token is admitted only for its expected existing session; delivery cannot silently start a new session when existing-session ownership is required.
• Billing terminal and retry identity — terminal usage and retries preserve a stable billing identity so replay/retry cannot duplicate or lose settlement.
• Standard Schema tool conversion — static and dynamic tool schemas accept Standard Schema inputs through the same formal conversion path as JSON Schema.
• Source-backed compaction model resolution — authored compaction models retain source/routing identity and fail compilation when context-window metadata cannot be resolved.
• Non-serializable live step state — step-local tool/runtime state remains live for the active step and is not silently JSON-coerced into an incomplete durable representation.

Desired upstream outcome

Each checkbox may land as its own focused PR and release. For every family, the upstream contract should include public behavior tests and a release note or exported API/runtime contract sufficient for downstream verification. Once an official Eve release satisfies a family, ChatGate will delete that isolated delta and its focused verifier assertions atomically—without aliases, fallback branches, dual runtimes, or session migration.

Would the maintainers accept this as the canonical umbrella tracker while we open focused PRs/issues for the individual families they want split further?

[ChatGateAI]

ChatGate forward-fix update: chatgate-next/apps#2511 / PR #2514 landed in production at merge SHA 08b3dc914313ce7dc224a92858fcc5c16f7f6ead.

The downstream patch is now managed as one immutable, digest-addressed ChatGate Eve distribution with per-capability upstream tracking and fail-closed installed-artifact verification. Child-session authorization was removed from the downstream delta because ChatGate now consumes Eve's public HookContext parent lineage through explicit root/Browser/Memory authorization hooks. The private session.started.invocation extension and its guard/test were deleted rather than kept as a compatibility path.

The other independently listed capability families in this issue remain active convergence targets. ChatGate will remove each delta atomically when an upstream release provides equivalent source and behavior tests.