Skip to content

Measure native V2 interruption settlement ordering - #810

Merged
dmoliveira merged 1 commit into
mainfrom
test/v2-native-settlement
Nov 15, 2026
Merged

dmoliveira merged 1 commit into
mainfrom
test/v2-native-settlement

Conversation

@dmoliveira

Copy link
Copy Markdown
Owner

Summary

  • Add a retained-fixture probe for two accepted native 2.2.5 interruptions and native session.wait calls across successive executions. The fixture injects tool-error events and intentionally delays delivery of the first completed wait result.
  • Require a fresh native wait, six directly invoked quarantine guards to remain closed while its result is held, and a separate peer session to reach the authenticated localhost provider with a synthetic marker.
  • Reuse the auxiliary probe's bounded authenticated runtime and strengthen its cleanup reporting. Reject unexpected or ambiguous plugin inventories. Run the new probe in the 2.2.5 CI job; other versions are not qualified.
  • Do not enable the gateway or infer naturally occurring scheduling, settlement of independent processes, or security protection.

Validation

  • 148 focused native-settlement, auxiliary, profile, boundary and direct-shell probe tests; Ruff; Python compilation; Make runtime contract; documentation/reachability checks; static pre-commit hooks. Full make validate is deferred to isolated CI because local tests share a fixed-name configuration-lock registry.
  • Restricted macOS tmux runs of the selected OpenCode 2.2.5 executable (SHA-256 abe4d88594bffb12b364375b8a6732d2d1f7a977195ed1a35c5c76f8e89c9e0e) observed both native interruption acceptances and both native waits. The reusable script and documented Make target passed, with checked teardown and all case/version roots retained.
  • A separate retained baseline control using the pre-fix adapter from c52a883 observed guard reopening after the delayed first native wait with only one wait; the fixed adapter stayed closed until a second wait was delivered. The error events and wait delay were injected; guard checks were direct callback invocations.
  • Independently tested OS policy denied outside and symlink-target writes, non-loopback connections and external signals, while allowing owned fixture writes and loopback. This is bounded evidence, not complete containment or proof that no process escaped the checked group.

@dmoliveira
dmoliveira merged commit 428f897 into main Nov 15, 2026
6 checks passed
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.

1 participant