Skip to content

fix: address outstanding sonar issues#104

Merged
rapids-bot[bot] merged 1 commit into
NVIDIA:release/0.2from
willkill07:wkk_fix-sonar-release-0.2
May 14, 2026
Merged

fix: address outstanding sonar issues#104
rapids-bot[bot] merged 1 commit into
NVIDIA:release/0.2from
willkill07:wkk_fix-sonar-release-0.2

Conversation

@willkill07
Copy link
Copy Markdown
Member

@willkill07 willkill07 commented May 14, 2026

Overview

Addresses the open Sonar maintainability findings reported on release/0.2 by reducing Rust cognitive complexity and replacing duplicated Go test literals.

  • I confirm this contribution is my own work, or I have the right to submit it under this project's license.
  • I searched existing issues and open pull requests, and this does not duplicate existing work.

Details

  • Split observability doctor and plugin editor control-flow into smaller helper functions.
  • Split OpenAI Responses request encoding overlays into focused helper functions.
  • Added constants for duplicated Go observability test literals.

Where should the reviewer start?

Start with crates/core/src/codec/openai_responses.rs, then review the smaller CLI refactors in crates/cli/src/doctor.rs and crates/cli/src/plugins.rs.

Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)

  • Relates to: none

Summary by CodeRabbit

  • Refactor

    • Enhanced code organization in observability component checking, plugin configuration editing, and OpenAI response encoding for improved internal structure and maintainability.
  • Tests

    • Standardized error message formatting in observability plugin tests for improved consistency and clearer diagnostic output during test failures.

Review Change Stack

Signed-off-by: Will Killian <wkillian@nvidia.com>
@willkill07 willkill07 requested a review from a team as a code owner May 14, 2026 12:30
@github-actions github-actions Bot added size:M PR is medium Bug issue describes bug; PR fixes bug lang:go PR changes/introduces Go code lang:rust PR changes/introduces Rust code labels May 14, 2026
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 14, 2026

Walkthrough

This PR refactors four independent modules: CLI doctor observability checks, CLI plugins editor, core OpenAI Responses codec, and observability test infrastructure. Each extracts duplicated or monolithic logic into smaller, focused helper functions while preserving all existing behavior and public API signatures.

Changes

CLI Observability Checks Refactoring

Layer / File(s) Summary
Main checks builder refactoring
crates/cli/src/doctor.rs
Main collect_observability_component_checks function simplified to iterate over sections and call delegated helpers, replacing inline section_enabled/section_output_directory and section_endpoint/probe_http_named logic.
File exporter directory check helper
crates/cli/src/doctor.rs
New observability_file_exporter_check validates configured output directory for ATOF/ATIF sections and returns appropriate pass/warning/error checks, or informational default-output check when no override exists.
HTTP exporter endpoint probe helper
crates/cli/src/doctor.rs
New observability_http_exporter_check probes configured endpoints for OpenTelemetry/OpenInference sections, or returns informational default-endpoint check when no override exists.

CLI Plugins Editor Refactoring

Layer / File(s) Summary
Main section editor refactoring
crates/cli/src/plugins.rs
Main edit_section function rewritten to fetch menu entries from section_menu_items, delegate reset handling to reset_selected_item, and map selections to edit/toggle/reset actions via edit_selected_section_item.
Menu construction helpers
crates/cli/src/plugins.rs
New section_menu_items generates complete per-section menu (toggle/fields/reset/back); new section_field_menu_item formats field rows with configured/default labels and current values.
Selection index helpers
crates/cli/src/plugins.rs
New selected_field_index adjusts for optional enabled toggle row; new reset_section_index computes reset-row position after fields, supporting menu selection mapping.
Selection handling and action dispatch
crates/cli/src/plugins.rs
New reset_selected_item encapsulates reset behavior (field-level or section-level); new edit_selected_section_item maps menu selections to enable/disable, field edit, or section reset actions.

Core Codec OpenAI Responses Refactoring

Layer / File(s) Summary
Encoding helper functions
crates/core/src/codec/openai_responses.rs
New helpers for: encoding instructions/input with system vs user message splitting and unparsed passthrough support; encoding tools/tool_choice; overlaying modeled fields (model, truncation/reasoning/include/metadata, scalar groups); merging annotated.extra while excluding internal passthrough key.
Main encode method refactoring
crates/core/src/codec/openai_responses.rs
Main OpenAIResponsesCodec::encode delegates to new helpers for input encoding, generation-parameter overlay, tools encoding, modeled-field overlay, and extra-field merging, replacing monolithic inline implementation.

Test Error-Message Formatting Standardization

Layer / File(s) Summary
Format constants and standardized usage
go/nemo_flow/observability_plugin_test.go
New fatalErrorFormat and failedSuffix constants centralize error-message templates; t.Fatalf call sites and EmitAgentStart/EmitAgentEnd helpers updated to use shared constants, preserving all test logic and assertions.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

  • NVIDIA/NeMo-Flow#98: Introduces the observability/plugins functionality that is refactored in doctor.rs and plugins.rs in this PR.
  • NVIDIA/NeMo-Flow#91: Also refactors go/nemo_flow/observability_plugin_test.go and touches the same EmitAgentStart/EmitAgentEnd helper functions.
🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Description check ✅ Passed Description includes all required sections: Overview with confirmations, Details explaining changes, guidance for reviewers, and Related Issues section.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Title check ✅ Passed The title follows Conventional Commits format with type 'fix' in lowercase, a concise imperative summary, is 37 characters (under 72), and accurately reflects the refactoring changes across multiple files to address Sonar maintainability issues.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@go/nemo_flow/observability_plugin_test.go`:
- Around line 21-22: Rename the two package-level constants fatalErrorFormat and
failedSuffix to PascalCase (e.g., FatalErrorFormat and FailedSuffix) and update
all references to them in the test file and any helpers (look for usages within
observability_plugin_test.go such as formatting calls or string concatenations)
so the code compiles and follows the repository Go naming rule for
exported-style constants.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Enterprise

Run ID: 4d4c87e0-bc4e-4f93-9057-9d6b3ae3eed0

📥 Commits

Reviewing files that changed from the base of the PR and between 47e3414 and 11a9150.

📒 Files selected for processing (4)
  • crates/cli/src/doctor.rs
  • crates/cli/src/plugins.rs
  • crates/core/src/codec/openai_responses.rs
  • go/nemo_flow/observability_plugin_test.go
📜 Review details
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Check / Run
🧰 Additional context used
📓 Path-based instructions (21)
**/*.rs

📄 CodeRabbit inference engine (.agents/skills/test-ffi-surface/SKILL.md)

**/*.rs: Run cargo fmt --all for FFI work as it is Rust work
Run just test-rust for FFI validation
Run cargo clippy --workspace --all-targets -- -D warnings to enforce warnings-as-errors linting

**/*.rs: Run cargo fmt --all for Rust code formatting
Run cargo clippy --workspace --all-targets -- -D warnings to enforce Rust linting with no warnings
Run just test-rust as the shared-runtime build/test wrapper for Rust changes

Use Rust snake_case naming convention for Rust code

**/*.rs: Any Rust change must run just test-rust
Any Rust change must run cargo fmt --all
Any Rust change must run cargo clippy --workspace --all-targets -- -D warnings

**/*.rs: Run cargo fmt --all for Rust code formatting when Node changes touch Rust files
Run cargo clippy --workspace --all-targets -- -D warnings to enforce strict linting when Rust files changed as part of Node work

**/*.rs: Always run just test-rust when any Rust code changes
Always run cargo fmt --all when any Rust code changes
Always run cargo clippy --workspace --all-targets -- -D warnings when any Rust code changes

Files:

  • crates/core/src/codec/openai_responses.rs
  • crates/cli/src/doctor.rs
  • crates/cli/src/plugins.rs
**/*.{rs,go,js,ts,tsx}

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Include SPDX license headers in all Rust, Go, JavaScript, and TypeScript source files using C-style comment syntax

Files:

  • crates/core/src/codec/openai_responses.rs
  • crates/cli/src/doctor.rs
  • crates/cli/src/plugins.rs
  • go/nemo_flow/observability_plugin_test.go
**/*.{rs,py,go,js,ts,tsx}

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Use SONAR_IGNORE_START / SONAR_IGNORE_END markers only for documented false positives that cannot be resolved in code; keep ignored blocks small, add explanatory comments, and require reviewer sign-off

Files:

  • crates/core/src/codec/openai_responses.rs
  • crates/cli/src/doctor.rs
  • crates/cli/src/plugins.rs
  • go/nemo_flow/observability_plugin_test.go
**/*.{js,ts,tsx,jsx,py,rs,go,java,c,cpp,h,cc,cxx,cs,rb,php,swift,kt}

📄 CodeRabbit inference engine (.agents/skills/prepare-pr/SKILL.md)

Changed files must be formatted with the language-native formatter

Files:

  • crates/core/src/codec/openai_responses.rs
  • crates/cli/src/doctor.rs
  • crates/cli/src/plugins.rs
  • go/nemo_flow/observability_plugin_test.go
crates/{core,adaptive}/**

📄 CodeRabbit inference engine (.agents/skills/prepare-pr/SKILL.md)

Changes to crates/core or crates/adaptive must run the full language matrix

Files:

  • crates/core/src/codec/openai_responses.rs
{crates/core,crates/adaptive}/**/*.rs

📄 CodeRabbit inference engine (.agents/skills/test-wasm-binding/SKILL.md)

If the change touched shared runtime semantics in crates/core or crates/adaptive, also use validate-change

Files:

  • crates/core/src/codec/openai_responses.rs
crates/core/**/*.rs

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

When crates/core changes, run the full validation matrix across Rust, Python, Go, Node.js, and WebAssembly

crates/core/**/*.rs: Use Json = serde_json::Value in Rust-facing runtime APIs where the existing code expects JSON payloads.
Use Result<T> with FlowError in core runtime paths. Keep errors explicit and binding-appropriate at the wrapper layer.

Files:

  • crates/core/src/codec/openai_responses.rs
**/*.{py,js,ts,tsx,go,rs,md}

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

Format changed files with the language-native formatter before the final lint/test pass

Files:

  • crates/core/src/codec/openai_responses.rs
  • crates/cli/src/doctor.rs
  • crates/cli/src/plugins.rs
  • go/nemo_flow/observability_plugin_test.go
**/*.{rs,py,js,ts,tsx,go}

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

During iteration, prefer uv run pre-commit run --files <changed files...> for targeted validation

Files:

  • crates/core/src/codec/openai_responses.rs
  • crates/cli/src/doctor.rs
  • crates/cli/src/plugins.rs
  • go/nemo_flow/observability_plugin_test.go
crates/{core,adaptive}/**/*.rs

⚙️ CodeRabbit configuration file

crates/{core,adaptive}/**/*.rs: Review the Rust runtime for async correctness, scope isolation, middleware ordering, and event lifecycle regressions.
Pay close attention to task-local/thread-local scope propagation, callback lifetimes, stream finalization, and root_uuid isolation.
Public API changes should preserve existing behavior unless tests and docs show the intended migration path.

Files:

  • crates/core/src/codec/openai_responses.rs
go/nemo_flow/**/*.go

📄 CodeRabbit inference engine (.agents/skills/test-go-binding/SKILL.md)

Format changed Go packages with cd go/nemo_flow && go fmt ./...

Use PascalCase naming convention for Go API implementations

For Go binding changes, run go fmt ./... within the Go module to format all Go files

Files:

  • go/nemo_flow/observability_plugin_test.go
**/*.go

📄 CodeRabbit inference engine (CONTRIBUTING.md)

**/*.go: Use gofmt for Go code formatting
Use go vet ./... for Go static analysis
Use PascalCase naming convention for Go code

Files:

  • go/nemo_flow/observability_plugin_test.go
**/*.{md,markdown,py,sh,bash,js,ts,java,cpp,go,rust}

📄 CodeRabbit inference engine (.agents/skills/contribute-docs/SKILL.md)

Keep package names, repo references, and build commands current in documentation

Files:

  • go/nemo_flow/observability_plugin_test.go
{crates/adaptive/**,python/nemo_flow/{adaptive,plugin}.py,go/nemo_flow/{adaptive,**}/*.go,**/*.{ts,js,wasm}}

📄 CodeRabbit inference engine (.agents/skills/maintain-optimizer/SKILL.md)

Keep adaptive config schema, plugin lifecycle, and bindings in sync across crates/adaptive, core, bindings, Python (python/nemo_flow/adaptive.py and python/nemo_flow/plugin.py), Go (go/nemo_flow/adaptive and go/nemo_flow), and Node/WebAssembly helpers

Files:

  • go/nemo_flow/observability_plugin_test.go
{crates/adaptive/**/*.rs,python/nemo_flow/adaptive.py,python/nemo_flow/plugin.py,go/nemo_flow/**/*.go,**/{helper,constructor,builder}.{ts,tsx,js}}

📄 CodeRabbit inference engine (.agents/skills/maintain-optimizer/SKILL.md)

Ensure typed helper constructors map cleanly to the same config document without divergence

Files:

  • go/nemo_flow/observability_plugin_test.go
{crates/adaptive/**/*.rs,python/nemo_flow/plugin.py,go/nemo_flow/**/*.go,**/{plugin,lifecycle}.{ts,tsx,js}}

📄 CodeRabbit inference engine (.agents/skills/maintain-optimizer/SKILL.md)

Maintain consistent plugin lifecycle across all language bindings (Rust, Python, Go, Node/WebAssembly)

Files:

  • go/nemo_flow/observability_plugin_test.go
{crates/adaptive/**/*.rs,python/nemo_flow/plugin.py,go/nemo_flow/**/*.go,**/{context,plugin}.{ts,tsx,js,rs}}

📄 CodeRabbit inference engine (.agents/skills/maintain-optimizer/SKILL.md)

Keep plugin context surfaces aligned across all language implementations

Files:

  • go/nemo_flow/observability_plugin_test.go
{docs/**,examples/**,crates/adaptive/**,python/nemo_flow/**,go/nemo_flow/**,**/{example,component}.{ts,tsx,js,rs,py,go}}

📄 CodeRabbit inference engine (.agents/skills/maintain-optimizer/SKILL.md)

Any new adaptive component kind must have documentation, examples, and binding coverage across all supported languages

Files:

  • go/nemo_flow/observability_plugin_test.go
go/**/*.go

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

If Go language surface changed, always run Go test target even when Rust core did not change

Files:

  • go/nemo_flow/observability_plugin_test.go
go/nemo_flow/**/*

⚙️ CodeRabbit configuration file

go/nemo_flow/**/*: Review Go binding changes for cgo memory ownership, race safety, callback cleanup, idiomatic exported APIs, and parity with Rust/FFI behavior.
Any API change should include focused Go tests and consider race-test behavior.

Files:

  • go/nemo_flow/observability_plugin_test.go
{crates/**/tests/**,python/tests/**,go/nemo_flow/**/*_test.go}

⚙️ CodeRabbit configuration file

{crates/**/tests/**,python/tests/**,go/nemo_flow/**/*_test.go}: Tests should cover the behavior promised by the changed API surface, including error paths and cross-request isolation where relevant.
Prefer assertions on lifecycle events, scope stacks, middleware ordering, and binding parity over shallow smoke tests.

Files:

  • go/nemo_flow/observability_plugin_test.go
🔇 Additional comments (7)
go/nemo_flow/observability_plugin_test.go (1)

55-55: LGTM!

Also applies to: 85-85, 99-99, 188-188, 200-200, 207-207, 246-247, 253-253

crates/cli/src/doctor.rs (1)

528-535: LGTM!

Also applies to: 539-556, 558-575

crates/cli/src/plugins.rs (2)

466-467: LGTM!

Also applies to: 475-476, 491-493, 497-516, 518-536, 538-551, 553-574, 797-803, 805-807


455-807: Confirm that Rust validation commands were executed for this refactor.

Per coding guidelines, all Rust changes must run:

  • cargo fmt --all
  • cargo clippy --workspace --all-targets -- -D warnings
  • just test-rust

These validations are mandatory before this refactor can be approved.

crates/core/src/codec/openai_responses.rs (3)

298-408: LGTM!


625-643: LGTM!


298-643: Ensure Rust toolchain compliance before merge.

Per coding guidelines for crates/core changes, verify the following locally:

  • cargo fmt --all – no formatting violations
  • cargo clippy --workspace --all-targets -- -D warnings – no lint warnings
  • just test-rust – all tests pass

If this change touches shared runtime semantics in crates/core, also run the full validation matrix (validate-change or equivalent across Rust, Python, Go, Node.js, and WebAssembly).

Comment thread go/nemo_flow/observability_plugin_test.go
@willkill07 willkill07 changed the title fix: address release 0.2 sonar issues fix: address outstanding sonar issues May 14, 2026
@willkill07 willkill07 added this to the 0.2 milestone May 14, 2026
@willkill07 willkill07 self-assigned this May 14, 2026
Copy link
Copy Markdown
Contributor

@AjayThorve AjayThorve left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The refactors preserve the previous control flow and encode ordering as far as I could verify.

@willkill07
Copy link
Copy Markdown
Member Author

/merge

@rapids-bot rapids-bot Bot merged commit eeb01a3 into NVIDIA:release/0.2 May 14, 2026
66 of 68 checks passed
willkill07 added a commit that referenced this pull request May 15, 2026
* fix: address outstanding sonar issues (#104)

#### Overview

Addresses the open Sonar maintainability findings reported on `release/0.2` by reducing Rust cognitive complexity and replacing duplicated Go test literals.

- [x] I confirm this contribution is my own work, or I have the right to submit it under this project's license.
- [x] I searched existing issues and open pull requests, and this does not duplicate existing work.

#### Details

- Split observability doctor and plugin editor control-flow into smaller helper functions.
- Split OpenAI Responses request encoding overlays into focused helper functions.
- Added constants for duplicated Go observability test literals.

#### Where should the reviewer start?

Start with `crates/core/src/codec/openai_responses.rs`, then review the smaller CLI refactors in `crates/cli/src/doctor.rs` and `crates/cli/src/plugins.rs`.

#### Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)

- Relates to: none




## Summary by CodeRabbit

* **Refactor**
  * Enhanced code organization in observability component checking, plugin configuration editing, and OpenAI response encoding for improved internal structure and maintainability.

* **Tests**
  * Standardized error message formatting in observability plugin tests for improved consistency and clearer diagnostic output during test failures.



[![Review Change Stack](https://storage.googleapis.com/coderabbit_public_assets/review-stack-in-coderabbit-ui.svg)](https://app.coderabbit.ai/change-stack/NVIDIA/NeMo-Flow/pull/104)

Authors:
  - Will Killian (https://github.com/willkill07)

Approvers:
  - Ajay Thorve (https://github.com/AjayThorve)

URL: #104

* test: isolate CLI config override tests (#105)

#### Overview

Isolates CLI config override unit tests from developer-level NeMo Flow configuration discovered through the normal user config path.

- [x] I confirm this contribution is my own work, or I have the right to submit it under this project's license.
- [x] I searched existing issues and open pull requests, and this does not duplicate existing work.

#### Details

- Adds a temp-scoped explicit config path helper for config tests that require no implicit user or project config discovery.
- Updates the affected override tests to use that explicit path instead of relying on ambient process configuration.

#### Where should the reviewer start?

Start with `crates/cli/tests/coverage/config_tests.rs`, especially the tests around CLI plugin config overrides.

#### Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)

- Relates to: none




## Summary by CodeRabbit

* **Tests**
  * Enhanced test infrastructure for configuration resolution by improving test isolation and setup processes.



[![Review Change Stack](https://storage.googleapis.com/coderabbit_public_assets/review-stack-in-coderabbit-ui.svg)](https://app.coderabbit.ai/change-stack/NVIDIA/NeMo-Flow/pull/105)

Authors:
  - Will Killian (https://github.com/willkill07)

Approvers:
  - Ajay Thorve (https://github.com/AjayThorve)

URL: #105

* chore: keep OpenClaw dependency in lockstep (#107)

#### Overview

Keep the OpenClaw plugin package dependency on `nemo-flow-node` aligned with the package version emitted by repository versioning and packaging workflows.

- [x] I confirm this contribution is my own work, or I have the right to submit it under this project's license.
- [x] I searched existing issues and open pull requests, and this does not duplicate existing work.

#### Details

- Change `nemo-flow-openclaw` to depend on the exact checked-in `nemo-flow-node` version.
- Add a `justfile` helper that updates package dependency versions in both `package.json` and `package-lock.json`.
- Wire the dependency update into `set-version`, `package-node`, and `package-openclaw` so prerelease package builds keep the Node and OpenClaw versions together.
- Align OpenClaw non-tag CI package version suffixing with the Node package workflow.

Validation run:

- `just set-version 0.2.0-alpha.20260514`, verified OpenClaw's `nemo-flow-node` dependency updated without dependency success logs, then restored with `just set-version 0.2.0`.
- `npm install --workspace=nemo-flow-node --ignore-scripts`
- `npm install --workspace=nemo-flow-openclaw --ignore-scripts`
- `npm run typecheck --workspace=nemo-flow-openclaw`
- `npm run pack:check --workspace=nemo-flow-openclaw`
- `just --list`
- `git diff --check`
- Commit-time pre-commit hooks passed for the staged files.

#### Where should the reviewer start?

Start with `justfile`, especially the new package dependency version helper and its calls from `set_node_package_versions`, `package-node`, and `package-openclaw`.

#### Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)

- Relates to: none




## Summary by CodeRabbit

## Release Notes

* **Chores**
  * Refined OpenClaw package versioning format for improved clarity
  * Pinned nemo-flow-node dependency to a stable version for enhanced reliability
  * Improved build and packaging tooling to ensure consistent dependency alignment



[![Review Change Stack](https://storage.googleapis.com/coderabbit_public_assets/review-stack-in-coderabbit-ui.svg)](https://app.coderabbit.ai/change-stack/NVIDIA/NeMo-Flow/pull/107)

Authors:
  - Will Killian (https://github.com/willkill07)

Approvers:
  - https://github.com/Salonijain27

URL: #107

* refactor: improve CLI coverage structure (#108)

#### Overview

Refactors the CLI coverage-heavy interactive setup/plugin editors so testable logic lives in focused helper modules, then adds coverage around the extracted behavior and related CLI paths.

- [x] I confirm this contribution is my own work, or I have the right to submit it under this project's license.
- [x] I searched existing issues and open pull requests, and this does not duplicate existing work.

#### Details

- Split plugin config file handling and Observability editor state helpers out of `plugins.rs` into testable modules.
- Split setup config/model/file helper logic out of `setup.rs` into `setup/model.rs`.
- Added focused coverage for CLI setup, plugin editing models, doctor formatting/check helpers, completion install helpers, server gateway forwarding paths, and CLI smoke behavior.
- Updated Codecov component reporting from Gateway Runtime to CLI, set the CLI target to 88%, and excluded only the remaining TTY prompt shells.
- Added module guidance so future testable logic does not go back into the interactive prompt files.

#### Where should the reviewer start?

Start with `crates/cli/src/plugins.rs` and `crates/cli/src/setup.rs` to see the orchestration-only boundary, then review `crates/cli/src/plugins/editor_model.rs`, `crates/cli/src/plugins/config_io.rs`, and `crates/cli/src/setup/model.rs` for the extracted testable logic.

Validation run locally:

- `cargo fmt --all`
- `cargo test -p nemo-flow-cli` with isolated `XDG_CONFIG_HOME`
- `cargo clippy --workspace --all-targets -- -D warnings`
- `just test-rust` with isolated `XDG_CONFIG_HOME`
- `cargo llvm-cov --package nemo-flow-cli --summary-only ...`
- commit hook pre-commit checks, including cargo fmt, cargo clippy, and cargo check

#### Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)

- Relates to: none


## Summary by CodeRabbit

* **New Features**
  * Plugin config preview, validation, and safer save/merge behavior; clearer scope selection and Hermes hook handling in setup.

* **Chores / Refactor**
  * Reorganized CLI internals into smaller, testable modules to make interactive editors and the setup wizard more reliable.

* **Tests**
  * Added extensive CLI unit and integration tests covering agents, doctor, completions, plugin editor TTY behavior, setup flows, and gateway/server forwarding.

* **Chores**
  * Updated Codecov to include CLI coverage and exclude interactive prompt loops.

Signed-off-by: Will Killian <wkillian@nvidia.com>

* ci: fold OpenClaw checks into Node workflow (#106)

#### Overview

Fold OpenClaw validation into the existing Node.js CI workflow as a conditional step, and make `just test-openclaw` run the live smoke coverage path.

- [x] I confirm this contribution is my own work, or I have the right to submit it under this project's license.
- [x] I searched existing issues and open pull requests, and this does not duplicate existing work.

#### Details

- Add a `run_openclaw` input to the reusable Node.js workflow.
- Run OpenClaw integration checks as a conditional step across the full Node test matrix.
- Remove the separate OpenClaw workflow call and workflow file.
- Keep OpenClaw package artifact creation inside the existing Node package job while leaving Node package steps gated by `run_package`.
- Add the live smoke test path to `just test-openclaw` and document the target in contributor testing guidance.

#### Where should the reviewer start?

Start with `.github/workflows/ci_node.yml`, especially the conditional OpenClaw test step in the Node test job and the package-job gating.

#### Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)

- Relates to: none


<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
## Summary by CodeRabbit

* **Tests**
  * Added live-run OpenClaw smoke tests and a helper script to run them.
  * OpenClaw integration checks now run conditionally inside the Node.js test flow.
  * Test suites updated to use compiled test artifacts and adjusted import paths.

* **Chores**
  * Removed standalone OpenClaw CI job; its checks and optional packaging were folded into the Node.js workflow and gated by inputs.
  * OpenClaw packaging and artifact upload are now conditional.

* **Documentation**
  * Testing guide and integration README updated with live-test target and artifact locations.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

* feat: update OpenClaw patch to use new config shape (#111)

#### Overview

This PR updates the OpenClaw patch to be aligned with `main`

- [x] I confirm this contribution is my own work, or I have the right to submit it under this project's license.
- [x] I searched existing issues and open pull requests, and this does not duplicate existing work.

#### Details

<!-- Describe the changes made in this PR. -->

#### Where should the reviewer start?

<!-- Point to the most important file, test, or design decision. -->

#### Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)

- Closes #

* feat: Add Deep Agents integration (#90)

#### Overview
* Primary entry point for end-users is the `add_nemo_flow_integration` method, which adds NeMo Flow middleware to the agent and subagents (if any).
* Emit a mark when skills are loaded and HITL events
* `langgraph` is promoted from a transitive dep to a direct-dep in the `langchain` extra since `python/nemo_flow/integrations/langchain/_serialization.py` now imports from `langgraph`
* Adds work-around for installing OpenSSL on Windows-Arm CI runners

- [x] I confirm this contribution is my own work, or I have the right to submit it under this project's license.
- [x] I searched existing issues and open pull requests, and this does not duplicate existing work.

#### Details



#### Where should the reviewer start?



#### Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)

- Closes #



## Summary by CodeRabbit

* **New Features**
  * Deep Agents integration: observability for agent runs, tool calls, filesystem/sandbox operations, human-in-the-loop events, backend instrumentation, and middleware marks.

* **Documentation**
  * Added Deep Agents integration README with setup, usage, and observed-event examples.

* **Tests**
  * New integration and end-to-end tests covering middleware, backend instrumentation, sandbox behavior, and HITL flows; added shared test fixture.

* **Chores**
  * Added optional Deep Agents dependency group and regenerated third‑party attributions/licenses.

* **CI**
  * Updated CI and dev sync steps to include Deep Agents extras and platform-specific setup.



[![Review Change Stack](https://storage.googleapis.com/coderabbit_public_assets/review-stack-in-coderabbit-ui.svg)](https://app.coderabbit.ai/change-stack/NVIDIA/NeMo-Flow/pull/90)

Authors:
  - David Gardner (https://github.com/dagardner-nv)

Approvers:
  - Will Killian (https://github.com/willkill07)
  - https://github.com/Salonijain27

URL: #90

* chore: refresh dependency locks (#112)

#### Overview

Refresh dependency locks and runtime compatibility wiring for the `release/0.2` branch.

- [x] I confirm this contribution is my own work, or I have the right to submit it under this project license.
- [x] I searched existing issues and open pull requests, and this does not duplicate existing work.

#### Details

- Updates Python optional integration constraints and lockfile entries for the release branch.
- Updates OpenClaw peer compatibility to `2026.5.12` and syncs the local hook type mirror with the current session end reasons.
- Adjusts Rust reqwest/rustls provider configuration and OTLP HTTP client selection so TLS and exporter initialization remain stable while unused optional transport packages stay out of the lockfile.
- Makes Node attribution generation lockfile-driven so platform-gated optional packages are listed consistently across CI and local machines.
- Pulls Node license text from integrity-checked locked npm artifacts when packages are not installed on the current platform.
- Regenerates Python and Node attribution files from the refreshed lockfiles.

Validation run:
- `cargo test -p nemo-flow-cli`
- `cargo check -p nemo-flow --features otel`
- `cargo check -p nemo-flow --features otel,openinference`
- `cargo test -p nemo-flow http_config_exports_scope_push_pop_and_marks_without_tokio_runtime -- --nocapture`
- `npm test --workspace integrations/openclaw`
- `uv run --extra langgraph --extra langchain-nvidia pytest python/tests/integrations/langchain python/tests/integrations/langgraph third_party/langgraph_tests`
- `npm audit --ignore-scripts`
- `cargo fmt --all --check`
- `pre-commit run --files scripts/licensing/attributions_lockfile_md.py ATTRIBUTIONS-Node.md package-lock.json`
- signed commit pre-commit suite

#### Where should the reviewer start?

Start with `scripts/licensing/attributions_lockfile_md.py`, `crates/cli/src/tls.rs`, `crates/core/Cargo.toml`, and `integrations/openclaw/package.json` to review the generator, runtime, and integration compatibility changes before the regenerated lockfile and attribution diffs.

#### Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)

- Relates to: none


## Summary by CodeRabbit

* **Dependencies**
  * Bumped several Python packages (langchain, langchain-core, langgraph, langgraph-*, urllib3) and raised OpenClaw compatibility to 2026.5.12.
* **New Features**
  * Added "shutdown" and "restart" as session termination reasons.
* **Chores**
  * Ensure TLS/crypto provider is initialized before network operations across CLI and services.
* **Documentation**
  * Refreshed third‑party attributions and improved license extraction for Node/Python packages.



[![Review Change Stack](https://storage.googleapis.com/coderabbit_public_assets/review-stack-in-coderabbit-ui.svg)](https://app.coderabbit.ai/change-stack/NVIDIA/NeMo-Flow/pull/112)

Authors:
  - Will Killian (https://github.com/willkill07)

Approvers:
  - David Gardner (https://github.com/dagardner-nv)
  - https://github.com/Salonijain27

URL: #112

* fix: support Cursor CLI hook config (#109)

#### Overview

Fix Cursor CLI hook configuration so current `cursor-agent` builds can execute NeMo Flow hook commands, and document the remaining Cursor CLI hook coverage limits.

- [x] I confirm this contribution is my own work, or I have the right to submit it under this project's license.
- [x] I searched existing issues and open pull requests, and this does not duplicate existing work.

#### Details

- Generate Cursor `.cursor/hooks.json` entries as direct command entries with top-level `"version": 1`.
- Preserve that Cursor-compatible shape when `nemo-flow run -- cursor-agent` temporarily patches project hooks.
- Update `nemo-flow doctor cursor` to reject nested Cursor hook groups and missing or non-`1` top-level version fields.
- Trim nullable fields from Cursor permission responses.
- Update Cursor integration docs and packaged hooks to state the CLI limitation plainly: current Cursor CLI hook coverage is narrower than Cursor IDE hook coverage.

#### Where should the reviewer start?

Start with `crates/cli/src/installer.rs` for the hook-shape change, then `crates/cli/src/doctor.rs` for validation of user-managed Cursor hook files.

#### Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)

- Closes https://linear.app/nvidia/issue/NMF-122/fix-cursor-cli-hook-config-and-document-stream-json-limitation



## Summary by CodeRabbit

* **Refactor**
  * Standardized Cursor hook JSON to require a top-level version (1) and direct command entries; merged/generated hook files now enforce this shape.

* **New Features**
  * Added stricter validation for Cursor hook files with clear, actionable status messages and test coverage.

* **Bug Fixes**
  * Cursor hook responses/endpoints no longer include legacy message fields.

* **Documentation**
  * Expanded Cursor integration and troubleshooting guidance, plus CLI verification steps.



[![Review Change Stack](https://storage.googleapis.com/coderabbit_public_assets/review-stack-in-coderabbit-ui.svg)](https://app.coderabbit.ai/change-stack/NVIDIA/NeMo-Flow/pull/109)

Authors:
  - Ajay Thorve (https://github.com/AjayThorve)

Approvers:
  - Will Killian (https://github.com/willkill07)

URL: #109

---------

Signed-off-by: Will Killian <wkillian@nvidia.com>
Co-authored-by: Will Killian <2007799+willkill07@users.noreply.github.com>
Co-authored-by: David Gardner <96306125+dagardner-nv@users.noreply.github.com>
Co-authored-by: Ajay Thorve <AjayThorve@users.noreply.github.com>
@willkill07 willkill07 deleted the wkk_fix-sonar-release-0.2 branch May 21, 2026 12:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Bug issue describes bug; PR fixes bug lang:go PR changes/introduces Go code lang:rust PR changes/introduces Rust code size:M PR is medium

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants