feat(streaming): complete graph-first firehose controls - #443
Merged
Conversation
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.
Summary
Design boundaries
Validation
cargo check --workspace --lockedcargo test -p omnigraph-cli --test system_local -- --nocapture(28 passed, 1 network-dependent test ignored)scripts/check-agents-md.shgit diff --checkGreptile Summary
This PR exposes selector-free, graph-wide stream resume and sealed maintenance through the engine, HTTP API, CLI, and cluster control surfaces while retaining the existing recovery protocols.
Confidence Score: 5/5
The PR appears safe to merge.
No blocking failure remains.
Important Files Changed
Sequence Diagram
sequenceDiagram participant Operator participant CLI participant Server participant Engine participant Recovery participant Lance Operator->>CLI: stream resume / maintenance CLI->>Server: Graph-scoped HTTP request Server->>Server: Authenticate and authorize stream_manage Server->>Engine: Graph-wide control operation Engine->>Engine: Preflight enrolled declarations Engine->>Recovery: Compose existing v15/v16/v17 owner Recovery->>Lance: Apply productive physical effects Recovery->>Engine: Atomically publish manifest state Engine-->>Server: Graph-logical result Server-->>CLI: Shared response DTO CLI-->>Operator: Human or JSON outputReviews (2): Last reviewed commit: "test(server): cover graph stream control..." | Re-trigger Greptile
Context used (4)
omnigraph-cluster)