Skip to content

refactor(runtime): retire historical resource adoption - #242

Merged
SaladDay merged 1 commit into
mainfrom
codex/retire-legacy-runtime
Sep 29, 2026
Merged

SaladDay merged 1 commit into
mainfrom
codex/retire-legacy-runtime

Conversation

@SaladDay

@SaladDay SaladDay commented Sep 29, 2026 •

Copy link
Copy Markdown
Collaborator

Change

Remove historical Runtime resource adoption and pre-specification node compatibility. Startup no longer verifies old receipts to manufacture placements or bind allocations to a local node. Incompatible saved node specifications reject before the owner epoch changes. Daemon bootstrap always advertises the configured public address; the embedded-node address resolver is removed.

Current reconnect, placement, maintenance, cancellation and uncertain cleanup ownership remain. Released history is preserved. Historical installations must keep their original Core responsible for compute, snapshots and unresolved operations; install this release separately. No deployed services or existing resources were changed.

Removed the ownership callback/verifier/adoption plan, four adoption SQL queries and generated methods, unspecified-deployment bypasses, and the bootstrap resolver. Canonical operator/contributor docs describe the support boundary. Safety tests use current placement and add refusal/unchanged-receipt coverage.

Validation

  • Linux PostgreSQL: 52 deployment/node/idle/recovery tests and all 91 execution tests passed, including the retirement state/pending-work matrix.
  • Server/bootstrap/gateway tests, make check-sqlc, make check-runtime-contract, and OpenAPI regeneration passed (no API schema delta).
  • Rebased onto refactor: consolidate runtime and provider integration contracts #241 without conflicts; a fresh independent blind review of the complete diff against c47b3cdb: no actionable findings.
  • Full make check, daemon build and official-client acceptance passed on required CI for ec34ee0d. Linux/macOS native checks passed. Windows rerun started after merge; the earlier identical retirement diff passed Windows on run 36601831009 (git range-diff confirms f8ba964c = ec34ee0d). Earlier manual full-gate attempts were blocked by macOS-specific behavior and the separate Linux host's root/socket permissions; those did not require source changes.
  • No new live-model or deployment qualification claimed.

@SaladDay
SaladDay force-pushed the codex/retire-legacy-runtime branch from f8ba964 to ec34ee0 Compare September 29, 2026 17:13
@SaladDay
SaladDay marked this pull request as ready for review September 29, 2026 17:29
@SaladDay
SaladDay merged commit 2344663 into main Sep 29, 2026
6 checks passed
@SaladDay
SaladDay deleted the codex/retire-legacy-runtime branch October 7, 2026 06:38
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