feat(fleet): durable movement foundations and bounded reconciler - #37
Merged
Merged
Conversation
Add journal-backed fleet operations, retained intents and enrollment contracts, resource-backed receiver preparation, finite host actions, fresh actor inspections, and a caller-driven movement controller. Include the local SQLite journal example, focused evidence, CI model coverage, and the full remaining fleet implementation plan.
Share the leased-node admission-pressure scenario between the executable and tests. Move a bounded journal-backed batch to two receivers, reopen the controller client, verify original outcomes and restored state, fence old source handles, and join all runtimes and journal jobs. Preserve incomplete production role coverage and remaining plan scope. Fix the owner-loss fixture to inspect the retained original fencing source and require empty resource ledgers.
…s-foundations # Conflicts: # scripts/check-web-rust-examples.py
…lan (#42) * docs(fleet): add self-contained control plane implementation plan * docs(fleet): close control plane production design gaps
This was referenced Oct 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Latest published checkpoint —
911009585f731eintegratesmainat4c1c982and resolves the three reported conflicts. The actor retains fleet admission kinds alongside main's optional request permits. Both LTX documentation contracts are preserved. PR mergeability was confirmed after both pushes./Users/haipingfu/Workspace/crabbuild-target/cellule-smoke-f0a15a6/evidence./Users/haipingfu/Workspace/crabbuild-target/cellule-pr37-merge-4c1c982/evidence.f0a15a6fails Compose balance, a minion follower-observation roster deadline, leased forwarded-command/c1 throughput (88.40% versus the unchanged 90% gate), and the routing aggregate. Object-only routing passes (minimum gated throughput 94.21%). The unchanged comparator reproduces both original 178-file campaigns. The hosted smoke artifact lacks an attempt trace; the new regression isolates the retry defect without establishing which transient refusal occurred there. The separate follower deadline and performance causes remain open.The complete W1–W10 goal remains unfinished. Highest priorities remain current-head CI, source/failed-owner reader and follower succession with durable process/accepted-work evidence, SettleRoles/Finalize, receiver-session recovery and minion maintenance/receiver-loss commands, then W9/W10 campaigns and exercised runbooks.
SourceSuccessorblocks and SettleRoles/Finalize remain refused. See the current progress record.Previous final-root checkpoint
Current checkpoint: exact final reader root
Canonical executable:
crates/cellule-host/minion; Cargo targetfleet_operations.ReaderEnrollmentRetirement; retain it after peer clone joining and shutdown. Native reader inventory fingerprint v2 binds every root field. Prior ephemeral continuations refuse their normal topology check; persisted enrollment/evidence bytes and signed peer contracts remain unchanged.Verification
All 13 fresh Rust commands and nine static gates pass on the isolated Rust 1.99 snapshot with its mounted target. All 1,117 committed Rust/Cargo paths match the qualified manifest.
Manifest SHA256:
42c25e30a926cabb324f48d3f9ea632b1ce47ffb1ab9418e634843b6949dd104.Preliminary failures correct a test-only position construction, an invalid idle-transfer assumption after the new command, and insufficient fixture memory for the newly exercised origin verifier. The exact busy handle now joins/releases through ordinary drain; the receiver is provisioned for the verifier's existing metadata envelope. No idle grace, production admission, profile, gate or expected evidence was weakened. Original failed logs/source remain retained.
Exact source archives/manifests, commands, original preliminary failures, negative sources/logs and restored qualification are retained under
/Users/haipingfu/Workspace/crabbuild-target/cellule-reader-final-root-bd381d6/evidence.CI and remaining delivery
Published parent
bd381d6remains MERGEABLE; all checks are terminal: 32 successes, two failures and three documented skips. Workspace, follower/object capacity, MSRV, contracts, cookbook quality/scenarios, Compose smoke, model, website and fuzz checks pass.Parent CI does not qualify this new source. Fresh current-head CI is required. The earlier overload endpoint failure's cause remains open despite the passing subsequent focused/full/hosted runs; preserved diagnostics do not independently establish a fix.
The full W1–W10 goal remains active and unfinished.
SourceSuccessorremains blocking; SettleRoles/Finalize remain refused. Exact root identity and native joining supply no complete current replacement policy, accepted external-work joining, durable process retention or physical maintenance completion.See the full plan, execution evidence, and exact reader contract.