Skip to content

Unify Runtime preparation and execution across environments - #195

Merged
SaladDay merged 22 commits into
codex/qualified-release-promotion-20260928from
codex/runtime-capability-unification-20260928
Sep 28, 2026
Merged

SaladDay merged 22 commits into
codex/qualified-release-promotion-20260928from
codex/runtime-capability-unification-20260928

Conversation

@SaladDay

@SaladDay SaladDay commented Sep 28, 2026 •

Copy link
Copy Markdown
Collaborator

Managed initialization previously executed through sandbox providers while self-hosted capabilities used a separate preparation path. Route initial files, configuration, package/setup operations and Skill/Plugin preparation through the same authenticated daemon protocol, then load the resulting frozen capability snapshot through the common execution flow.

Providers retain placement, capacity, daemon bootstrap and Environment reclamation. Runtime owns local installation and execution; closing an executor preserves the Environment, workspace and capability snapshot. Native adapter differences stay behind the shared contract. Public managed bundles and self-hosted local directories retain their input semantics and resolve through one parser and installed.json.

This change implements Linux and keeps the protocol independent of host paths and operating-system executables. It introduces no historical upgrade compatibility.

Stack: targets the existing PR191 integration branch. Includes the validated Session-executor dependency from PR193. Merging this PR does not itself merge the earlier installation/release stack into main or publish a release.

Validation:

  • Protocol, gateway, Runtime preparation and snapshot race tests; Core/API initialization tests with a dedicated PostgreSQL database.
  • Real Codex managed and self-hosted acceptance: 4 Sessions / 8 Turns, initial-file/bundle/setup ordering, warm executor reuse, reconnect snapshot reuse, new-Session snapshot refresh, write protection and retained Environment/workspace.
  • Independent blind review found two P2 mount-visibility issues. Both received narrow fixes and real isolated read/write/permission regression checks; no outstanding review findings.
  • The full server gate and CI remain running on the final test-fixture commit. The user explicitly authorized merging without waiting for this repeat. Prior full attempts failed only on obsolete preparation/node initialization fixtures; corrected Codex full-package race and related PostgreSQL race tests passed. The remaining Claude/MiniMax/Rust/Web checks passed separately. Browser fixtures are left to CI because the server lacks Chrome. No full historical release/E2E matrix is claimed.

The live model acceptance used candidate 108513b. Later changes are the name-guard declarations and two mount-visibility corrections, checked separately with targeted real isolation probes.

SaladDay and others added 21 commits September 28, 2026 15:01
…ntime-capability-unification-20260928

# Conflicts:
#	apps/parsar-daemon/internal/agent/claudesdk/session.go
#	apps/parsar-daemon/internal/agent/codex/session.go
#	packages/claude-sdk-adapter/src/adapter.ts
#	services/agents-api/internal/execution/dispatcher.go
# Conflicts:
#	packages/claude-sdk-adapter/tests/executor.test.mjs
@SaladDay
SaladDay merged commit 19943a3 into codex/qualified-release-promotion-20260928 Sep 28, 2026
3 checks passed
@SaladDay
SaladDay deleted the codex/runtime-capability-unification-20260928 branch October 10, 2026 05:05
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