docs: document the cluster runtime with a benchmark and integration capstone#82
Merged
Conversation
…apstone Signed-off-by: Joshua Temple <joshua.temple@stablekernel.com>
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
1 participant
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.
Documents the cluster module ahead of its first tag. Expands the package doc with Supervision and Migration sections, adds a README mirroring the house style — remote actors, the supervision decision table, live migration, performance, status — and a CHANGELOG seeding [0.1.0]. Adds a delivery benchmark baseline (local pass-through vs remote over the in-memory transport) and a multi-node integration capstone that exercises the runtime end to end: node-a remote-spawns a supervised worker on node-b, drives it, the worker fails, node-b's supervisor restarts it within budget, node-a keeps driving the same opaque ref — plus a migration round-trip onto an additively-evolved machine. Docs and tests only; no production code change. This closes a complete, stdlib-only cluster v0.1.0 on the in-memory transport. Coverage: cluster 92 percent.