Implement API-first runtime evidence and fail-closed OpenCLI adapters - #58
Conversation
[gstack-context]
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
|
⏳ Repowise has not indexed this repository yet No analysis on this PR because there is no index to compare against. Indexing usually runs automatically after install; if this persists, start it from the dashboard. |
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (22)
📝 WalkthroughSummary by CodeRabbit
WalkthroughThe PR adds review-only workflow agent tools, API discovery metadata, isolated-source validation, demand keyword improvements, OpenCLI readiness controls, legacy catalog normalization, source preset compilation, and bounded dispatch results. ChangesWorkflow agent and source execution
Estimated code review effort: 4 (Complex) | ~45 minutes Sequence Diagram(s)sequenceDiagram
participant Agent
participant MCPServer
participant WorkflowAPI
Agent->>MCPServer: Inspect workflow capabilities
MCPServer->>WorkflowAPI: Retrieve capabilities
WorkflowAPI-->>MCPServer: Return readiness and contracts
Agent->>MCPServer: Draft or preview changes
MCPServer->>WorkflowAPI: Submit draft or patch preview
WorkflowAPI-->>MCPServer: Return validation result
Agent->>MCPServer: Compile draft
MCPServer->>WorkflowAPI: Compile without persistence or execution
WorkflowAPI-->>MCPServer: Return compile result
Suggested reviewers: Poem
✨ Finishing Touches📝 Generate docstrings
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
What changed
Why
Agents need a governed API-first path that distinguishes catalog availability, compile previews, real dispatch, and resulting trace evidence. The previous working changes also treated some unverified OpenCLI commands as runnable and used a preview-only Twitter fixture for required-parameter materialization tests.
Impact
The control plane exposes clearer agent-facing workflow operations and fails closed when an OpenCLI dependency has not been verified. Runnable adapters continue to materialize required positional and named parameters correctly.
Root cause of the regression fixed during integration
The new availability boundary correctly classified browser/cookie adapters as
preview_only, but two older integration tests still used the Twitter cookie adapter to validate required-parameter handling. Those tests now use a runnable non-browser fixture, preserving both contracts.Validation
git diff --check: passedCode Intel's broader doctor stage still reports existing manifest reconciliation debt; native evidence and Sentrux completed successfully.