docs: add the feature coverage matrix mapping act+gitea and live-fleet layers#369
Merged
Conversation
…t layers A feature-by-feature map tracing every cascade capability to its hermetic act-plus-gitea scenario, its live-fleet probe and repo, and its unit coverage, with one line on what each layer proves and why both exist. Records the deliberate unit-and-CLI-only choices (simulate, graph, visualize) so they read as intentional, not gaps. Validated against a fully green ten-repo fleet run on v0.5.0-rc.10. Signed-off-by: Joshua Temple <joshua.temple@stablekernel.com>
joshua-temple
force-pushed
the
docs/coverage-matrix
branch
from
7c20b66 to
e264727
Compare
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.
What
A new docs page (
coverage-matrix.md, wired into the sidebar after "How it is tested") mapping every cascade feature to its hermetic act+gitea scenario, its live-fleet probe and repo, and its unit coverage, with one line on what each layer proves and why both layers exist. It records the deliberate unit-and-CLI-only choices (simulate, graph, visualize) so they read as intentional rather than gaps, and includes the concrete cases where the live fleet caught what the harness structurally masks (hotfix base from recorded state, no-change skip).Validation
Validated against a fully green ten-repo live-fleet run on
v0.5.0-rc.10: every probe passed and the fail-closed reconcile gate accounted for every run in each scenario window.Scope
Docs only: the new page plus its sidebar entry.