ci(e2e): reuse the Hermes production image by cjagwani · Pull Request #7508 · NVIDIA/NemoClaw

cjagwani · 2026-07-24T21:16:46Z

Summary

The sandbox image workflow now builds the Hermes production image once and reuses that exact image for its isolation probes. A dedicated producer performs the guarded local Buildx build and uploads one short-lived artifact; consumers load the artifact without rebuilding, authenticating to Docker Hub, or publishing it.

Related Issue

Part of #7451

Changes

Build the Hermes production image in a 30-minute producer using canonical full-SHA-pinned Buildx actions, local loading, and an OS/architecture-scoped GitHub Actions cache.
Preserve the bounded export swap, guarded build arguments, completed-image node-tar scan, installed-file checks, and Docker authentication cleanup.
Save and upload one one-day hermes-isolation-image artifact.
Load that artifact in a separate 90-minute secret-boundary/root-entrypoint consumer and the existing state-directory metadata consumer.
Require exactly one producer setup/build/save/upload, the canonical artifact download action and mapping, and no consumer registry authentication or rebuild.
Document the producer/consumer execution boundary in the internal E2E operator guide.

Type of Change

Code change (feature, bug fix, or refactor)
Code change with doc updates
Doc only (prose changes, no code sample modifications)
Doc only (includes code sample changes)

Quality Gates

Tests added or updated for changed behavior
Existing tests cover changed behavior — justification:
Tests not applicable — justification:
Docs updated for user-facing behavior changes
Docs not applicable — justification: runtime behavior is unchanged; the internal E2E operator guide was updated for the CI execution shape.
Sensitive paths changed (security, policy, credentials, preflight, onboarding, inference, runner, sandbox, or messaging)
Sensitive-path review completed or maintainer-approved waiver recorded — exact-diff nine-category review confirmed Docker Hub credentials remain producer-only; consumers cannot authenticate or rebuild; canonical Buildx and download actions are exact-SHA pinned; the Buildx action remains load: true and fail-closed on any push value other than false; and cache, artifact, cardinality, secret-scope, and no-registry-write invariants have independent negative tests.
Non-success, skipped, or missing CI check accepted by maintainer — check name, approval link, and follow-up issue:

Documentation Writer Review

Documentation writer subagent reviewed the completed changes
Result: docs-updated
Evidence: test/e2e/README.md documents the single Hermes image producer, runner-scoped Buildx cache, local-only build, artifact reuse by both consumers, and retained probe budgets. Reviewed against WRITING.md and docs/CONTRIBUTING.md; npm run docs passed at 06261fd27.
Agent: Codex Desktop

DGX Station Hardware Evidence

Tested on DGX Station
Tested commit:
Station profile/scenario:
Result:
Supporting evidence:

Verification

PR description includes a Signed-off-by: line and every published commit appears as Verified in GitHub — both contributor commits are Verified; the signed maintainer refresh and repair commits will be checked immediately after the single normal push.
Normal pre-commit and commit-msg hooks passed; npm run check:diff reproduced the diff-scoped pre-commit, commit-message, and pre-push gates on exact local head 06261fd27.
Targeted behavior tests pass for the current change set — two focused E2E-support files passed 21/21; npm run test:changed -- --coverage=false passed the same 21/21 affected tests after the main refresh.
Applicable broad gate passed — exact-head GitHub CI, the sandbox-image branch workflow, and selected E2E evidence remain required before approval.
Quality Gates section completed with required justifications or waivers
No secrets, API keys, or credentials committed
npm run docs builds without warnings (doc changes only) — command passed with 0 errors and two Fern warnings.
Doc pages follow the style guide (doc changes only)
New doc pages include SPDX header and frontmatter (new pages only)

Signed-off-by: Charan Jagwani cjagwani@nvidia.com

Summary by CodeRabbit

CI Improvements
- Shortened Hermes sandbox image build timeout and initialized Docker Buildx to speed up builds.
- Switched Hermes production image building to a Buildx-based flow with cache support, local-only loading, and stricter build-argument validation.
- Added save/upload of the Hermes isolation image and improved reuse in downstream tests, with updated build/test resource recording and cleanup.
Bug Fixes
- Tightened E2E workflow boundary validation for Hermes to prevent unintended registry writes, enforce correct secret scoping, and align producer/consumer expectations.
Documentation
- Updated the E2E README with the new CI execution shape and revised timeout budgets.

Signed-off-by: Charan Jagwani <cjagwani@nvidia.com>

coderabbitai · 2026-07-24T21:17:10Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 43be0ca5-2da6-4542-8e73-9f5f26c35b54

📥 Commits

Reviewing files that changed from the base of the PR and between c2031f8 and 06261fd.

📒 Files selected for processing (2)

test/e2e/README.md
test/e2e/support/sandbox-images-workflow-boundary.test.ts

📝 Walkthrough

Walkthrough

Hermes CI now uses a validated, cached Docker Buildx production build, transfers the resulting isolation image between jobs, and runs downstream probes with updated time budgets and secret-scope assertions. Documentation and workflow-boundary tests describe and enforce the revised execution model.

Changes

Hermes build and test workflow

Layer / File(s)	Summary
Validated Buildx production build `.github/workflows/...`, `tools/e2e/sandbox-images-workflow-boundary.mts`, `test/e2e/support/sandbox-images-workflow-boundary.test.ts`	Hermes validates production build arguments, initializes Buildx, builds with GHA caching and local loading, and rejects registry writes or invalid Buildx configuration.
Isolation artifact reuse and probe validation `.github/workflows/...`, `tools/e2e/sandbox-images-workflow-boundary.mts`, `test/e2e/support/hermes`, `test/e2e/README.md`	The producer uploads the isolation image, the consumer downloads and loads it, and Hermes probes enforce updated timeouts, dependency placement, ordering, and secret scopes.

Estimated code review effort: 4 (Complex) | ~45 minutes

Possibly related PRs

NVIDIA/NemoClaw#6242: Updates the same Hermes sandbox image boundary contracts, workflow, and image reuse behavior.

Suggested labels: integration: hermes, area: ci, area: e2e, platform: container, area: performance

Suggested reviewers: cv, prekshivyas, apurvvkumaria

Sequence Diagram(s)

sequenceDiagram
  participant ProducerJob
  participant Buildx
  participant ArtifactStore
  participant ConsumerJob
  participant HermesProbes
  ProducerJob->>Buildx: Validate and build local Hermes image
  Buildx-->>ProducerJob: Load Hermes image
  ProducerJob->>ArtifactStore: Upload isolation image tarball
  ConsumerJob->>ArtifactStore: Download isolation image
  ConsumerJob->>ConsumerJob: Load isolation image
  ConsumerJob->>HermesProbes: Run Hermes boundary probes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly reflects the main change: building the Hermes production image once and reusing it in E2E.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.

✨ Finishing Touches

📝 Generate docstrings

Create stacked PR
Commit on current branch

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch codex/7451-hermes-image-reuse

_{Comment @coderabbitai help to get the list of available commands.}

github-code-quality · 2026-07-24T21:17:31Z

Code Coverage Overview

Languages: TypeScript

TypeScript / code-coverage/plugin

The overall coverage in commit 06261fd in the codex/7451-hermes-im... branch remains at 96%, unchanged from commit 3e54a83 in the main branch.

_{Updated July 26, 2026 01:20 UTC}

github-actions · 2026-07-24T21:25:42Z

PR Review Advisor — No blocking findings reported

Advisor assessment: No blocking advisor findings reported
Next action: No advisor follow-up needed.
Findings: 0 blockers · 0 warnings · 0 suggestions

Model lanes

GPT-5.6 Terra (primary): Completed · high confidence · 0 blockers · 0 warnings · 0 suggestions
Nemotron 3 Ultra (second opinion): Completed · high confidence · 0 blockers · 2 warnings · 0 suggestions
Model comparison: normalized findings differ; normalized E2E selections differ; Nemotron reported the same number of blockers, 2 more warnings, the same number of suggestions.

Nemotron output stays in workflow artifacts and does not change the assessment above.

E2E guidance

Advisory only. E2E / PR Gate selects and runs jobs independently.

Recommended E2E: cloud-onboard, credential-sanitization, security-posture

Workflow run details

This automated review informs maintainers. Warnings and suggestions do not require a response. A maintainer decides whether to merge.

coderabbitai

Actionable comments posted: 1

🧹 Nitpick comments (2)

tools/e2e/sandbox-images-workflow-boundary.mts (2)
812-928: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

validateHermesImageReuse has grown into a large, multi-concern function.

This function now covers producer/consumer timeout budgets, Node-install exclusivity, probe ordering/budgets, artifact download/load contents, and producer save/upload/cleanup ordering — all in one function, matching the flagged high-complexity ranges. Splitting it into smaller helpers (e.g. one for budgets/Node exclusivity, one for probe ordering, one for artifact save/upload/download) would keep each piece easier to reason about and test in isolation.

As per coding guidelines, "Keep function complexity low; tracked complexity hotspots should not be expanded unnecessarily."
🤖 Prompt for 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.

In `@tools/e2e/sandbox-images-workflow-boundary.mts` around lines 812 - 928, Split
validateHermesImageReuse into focused helper functions for timeout and
Node-install rules, probe ordering and configuration, and artifact
download/load/save/upload validation. Keep validateHermesImageReuse as the
coordinating entry point, passing the shared errors and workflow/job data to
each helper while preserving all existing validation behavior and messages.
Source: Coding guidelines

392-425: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Complexity hotspot expanded with a large Hermes-specific branch.

This adds a substantial Hermes-only branch (validate-run equality check, Buildx pin check, and a 9-condition local-load contract check) directly inside the shared validateGuardedProductionBuild, which the line-range metadata already flags as high complexity. Consider extracting this into a dedicated validateHermesGuardedProductionBuild(errors, job, contract) helper so the shared function stays focused on the generic guarded-build contract.

As per coding guidelines, "Keep function complexity low; tracked complexity hotspots should not be expanded unnecessarily."
🤖 Prompt for 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.

In `@tools/e2e/sandbox-images-workflow-boundary.mts` around lines 392 - 425, The
shared validateGuardedProductionBuild flow has an oversized Hermes-specific
branch that increases its complexity. Extract the entire
build-hermes-sandbox-image validation, including validation-run, Buildx pinning,
and production-image action checks, into a dedicated
validateHermesGuardedProductionBuild(errors, job, contract) helper, then invoke
that helper from the shared function while preserving all existing validations
and error messages.
Source: Coding guidelines

🤖 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 `@tools/e2e/sandbox-images-workflow-boundary.mts`:
- Around line 355-358: Update the buildActionWritesRegistry condition in the
step-processing logic to require record(step.with).push === true, so omitted or
false push values are treated as non-writing while only explicit pushes count as
registry writes.

---

Nitpick comments:
In `@tools/e2e/sandbox-images-workflow-boundary.mts`:
- Around line 812-928: Split validateHermesImageReuse into focused helper
functions for timeout and Node-install rules, probe ordering and configuration,
and artifact download/load/save/upload validation. Keep validateHermesImageReuse
as the coordinating entry point, passing the shared errors and workflow/job data
to each helper while preserving all existing validation behavior and messages.
- Around line 392-425: The shared validateGuardedProductionBuild flow has an
oversized Hermes-specific branch that increases its complexity. Extract the
entire build-hermes-sandbox-image validation, including validation-run, Buildx
pinning, and production-image action checks, into a dedicated
validateHermesGuardedProductionBuild(errors, job, contract) helper, then invoke
that helper from the shared function while preserving all existing validations
and error messages.

🪄 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: CHILL

Plan: Enterprise

Run ID: 469bf321-5e6f-4c64-a52c-a6db8ce7a1cb

📥 Commits

Reviewing files that changed from the base of the PR and between 3a94d96 and c0ac9df.

📒 Files selected for processing (5)

.github/workflows/sandbox-images-and-e2e.yaml
test/e2e/README.md
test/e2e/support/hermes-secret-boundary-workflow.test.ts
test/e2e/support/sandbox-images-workflow-boundary.test.ts
tools/e2e/sandbox-images-workflow-boundary.mts

Signed-off-by: Charan Jagwani <cjagwani@nvidia.com>

Signed-off-by: Carlos Villela <cvillela@nvidia.com>

## Summary Harden the merged Hermes image-reuse workflow validator so action inputs and shell continuations cannot bypass credential, registry-write, build-cardinality, or artifact-handoff safeguards. Production workflow behavior is unchanged. ## Related Issue Part of #7451. Follow-up to #7508. ## Changes - Scan action `with` inputs for protected secrets and reject `docker/login-action` outside the canonical producer authentication step. - Normalize shell continuations and recognize `docker buildx build` so multiline pushes and duplicate CLI builds fail closed. - Require the reviewed artifact action pins and download-before-load ordering on every Hermes artifact leg. - Add five adversarial regression tests for the reproduced bypasses. ## Type of Change - [x] Code change (feature, bug fix, or refactor) - [ ] Code change with doc updates - [ ] Doc only (prose changes, no code sample modifications) - [ ] Doc only (includes code sample changes) ## Quality Gates - [x] Tests added or updated for changed behavior - [ ] Existing tests cover changed behavior — justification: - [ ] Tests not applicable — justification: - [ ] Docs updated for user-facing behavior changes - [x] Docs not applicable — justification: this hardens an internal workflow validator and its support tests; the production workflow and documented operator contract are unchanged. - [x] Sensitive paths changed (security, policy, credentials, preflight, onboarding, inference, runner, sandbox, or messaging) - [x] Sensitive-path review completed or maintainer-approved waiver recorded — reviewer/approval link/justification: an independent exact-diff maintainer/security review reproduced five fail-open mutations before the patch and verified the five guarded cases after the patch. - [ ] Non-success, skipped, or missing CI check accepted by maintainer — check name, approval link, and follow-up issue: ## Documentation Writer Review - [x] Documentation writer subagent reviewed the completed changes - Result: `no-docs-needed` - Evidence: At reviewed head `a6e864323`, the only changes are internal E2E workflow-boundary validator hardening and adversarial support tests. The production workflow remains unchanged. Existing `test/e2e/README.md` already documents the Hermes producer/consumer artifact flow, exact action pins, local image loading, and disabled registry writes. The explicit affected suite passed 26/26 and `npm run check:diff` passed. - Agent: Codex Desktop   ## DGX Station Hardware Evidence - [ ] Tested on DGX Station - Tested commit: - Station profile/scenario: - Result: - Supporting evidence: ## Verification - [x] PR description includes a `Signed-off-by:` line and every commit appears as `Verified` in GitHub - [x] Normal `pre-commit`, `commit-msg`, and `pre-push` hooks passed; `npm run check:diff` also passed on exact refreshed head `a6e864323`. - [x] Targeted behavior tests pass for the current change set — explicit E2E-support suite passed 26/26 on exact refreshed head. Before the main refresh, `npm run test:changed -- --coverage=false` also passed 26/26; after the merge-topology refresh it selected no tests, so the affected files were run explicitly. - [x] Applicable broad gate passed — not applicable to this narrow validator/test-only delta; exact focused tests and the complete diff gate passed, and GitHub CI remains required before approval. - [x] Quality Gates section completed with required justifications or waivers - [x] No secrets, API keys, or credentials committed - [ ] `npm run docs` builds without warnings (doc changes only) - [ ] Doc pages follow the style guide (doc changes only) - [ ] New doc pages include SPDX header and frontmatter (new pages only) --- Signed-off-by: Carlos Villela <cvillela@nvidia.com>  ## Summary by CodeRabbit * **Bug Fixes** * Strengthened workflow validation for Hermes image consumers and producers. * Blocked unauthorized Docker authentication and secret propagation in consumer jobs. * Added validation against duplicate production builds, registry writes, and unsafe multiline commands. * Enforced correct artifact upload/download actions, image loading, and step ordering. * Improved detection of Docker Buildx commands and authentication methods across workflow formats.  Signed-off-by: Carlos Villela <cvillela@nvidia.com>

## Summary Close the remaining Hermes image-consumer validator bypasses identified after #7551 merged. Shell continuations are normalized before the no-rebuild check, and assigned Buildx push values are evaluated case-insensitively. Literal `false` remains non-writing; true, empty, mixed-case, and dynamic or otherwise nonliteral values are rejected so the consumer cannot hide a rebuild or registry write. ## Related Issue Part of #7451. Follow-up to #7508 and #7551. ## Changes - Normalize Hermes consumer shell continuations before checking for Docker and Buildx builds. - Detect assigned, mixed-case, and dynamic Buildx registry-push values in the consumer guard. - Preserve literal `--push=false` as non-writing. - Add adversarial regressions for multiline rebuilds and assigned push values. ## Type of Change - [x] Code change (feature, bug fix, or refactor) - [ ] Code change with doc updates - [ ] Doc only (prose changes, no code sample modifications) - [ ] Doc only (includes code sample changes) ## Quality Gates - [x] Tests added or updated for changed behavior - [ ] Existing tests cover changed behavior — justification: - [ ] Tests not applicable — justification: - [ ] Docs updated for user-facing behavior changes - [x] Docs not applicable — justification: the production workflow and documented no-rebuild contract are unchanged; this makes the internal validator enforce that existing contract for continued commands. - [x] Sensitive paths changed (security, policy, credentials, preflight, onboarding, inference, runner, sandbox, or messaging) - [x] Sensitive-path review completed or maintainer-approved waiver recorded — reviewer/approval link/justification: CodeRabbit reproduced the bypass on #7551; the exact mutation is now an adversarial test and passes only with normalization at the consumer guard. - [ ] Non-success, skipped, or missing CI check accepted by maintainer — check name, approval link, and follow-up issue: ## Documentation Writer Review - [x] Documentation writer subagent reviewed the completed changes - Result: `no-docs-needed` - Evidence: At PR SHA `2cef897b4fcba8033d115d94f2dd4c2ae12d86ed`, the change only strengthens the repository-internal Hermes image-consumer validator for multiline rebuilds and assigned, mixed-case, or dynamic Buildx push values. Literal `--push=false` remains non-writing. `test/e2e/README.md` already documents the no-rebuild/no-registry-write contract. The focused E2E-support suite passed 29/29, the PR workflow-contract suite passed 22/22, and `npm run build:cli` plus `npm run check:diff` passed. - Agent: Codex Desktop   ## DGX Station Hardware Evidence - [ ] Tested on DGX Station - Tested commit: - Station profile/scenario: - Result: - Supporting evidence: ## Verification - [x] PR description includes a `Signed-off-by:` line and every commit appears as `Verified` in GitHub - [x] Normal `pre-commit`, `commit-msg`, and `pre-push` hooks passed; `npm run build:cli` and `npm run check:diff` also passed on exact head `2cef897b4fcba8033d115d94f2dd4c2ae12d86ed`. - [x] Targeted behavior tests pass for the current change set — E2E-support passed 29/29 and the PR workflow-contract suite passed 22/22. - [x] Applicable broad gate passed — not applicable to this validator/test-only delta; the exact affected suites, CLI build, and complete diff gate passed, and GitHub CI remains required before approval. - [x] Quality Gates section completed with required justifications or waivers - [x] No secrets, API keys, or credentials committed - [ ] `npm run docs` builds without warnings (doc changes only) - [ ] Doc pages follow the style guide (doc changes only) - [ ] New doc pages include SPDX header and frontmatter (new pages only) --- Signed-off-by: Carlos Villela <cvillela@nvidia.com>  ## Summary by CodeRabbit * **Bug Fixes** * Improved sandbox image workflow validation to more precisely detect `docker buildx build ... --push` commands, including shell line continuations and `--push` casing/formatting. * Strengthened Hermes prebuilt-image reuse checks by normalizing command formatting before validating consumer steps. * **Tests** * Added new end-to-end negative cases covering consumer attempts to rebuild the prebuilt Hermes production image. * Added coverage to ensure consumers attempting registry writes via `--push` are rejected, while explicitly using `--push=false` is allowed.  --------- Signed-off-by: Carlos Villela <cvillela@nvidia.com> Signed-off-by: Apurv Kumaria <akumaria@nvidia.com> Signed-off-by: Charan Jagwani <cjagwani@nvidia.com> Co-authored-by: Apurv Kumaria <akumaria@nvidia.com> Co-authored-by: Charan Jagwani <cjagwani@nvidia.com>

## Summary Add the canonical `docs/changelog/2026-07-25.mdx` release entry with the exact `## v0.0.96` heading. The entry reconciles all 90 first-parent commits since v0.0.95 with all 92 merged PRs in the live `v0.0.96` label ledger and groups the user-visible changes by operator journey. ## Changes - Add the parser-safe dated MDX changelog entry for v0.0.96 with root-absolute links to the focused user guides. - Source summary: - [#7194](#7194) -> `docs/changelog/2026-07-25.mdx`: Document persistent baseline network policy exclusions and their inspection, rebuild, and snapshot behavior. - [#7188](#7188), [#7427](#7427), and [#7546](#7546) -> `docs/changelog/2026-07-25.mdx`: Document DNS-backed HTTPS inference routing, keyless loopback endpoints, and provider-marker isolation. - [#7238](#7238) -> `docs/changelog/2026-07-25.mdx`: Document blueprint sandbox and provider identifier validation before state writes or OpenShell calls, with bounded terminal-safe rejection previews. - [#7319](#7319), [#7274](#7274), [#7528](#7528), [#7353](#7353), and [#7560](#7560) -> `docs/changelog/2026-07-25.mdx`: Document the managed default gateway service, onboarding readiness, and container-runtime identity safeguards. - [#7349](#7349), [#7498](#7498), [#7406](#7406), [#7196](#7196), [#7559](#7559), [#7421](#7421), [#7510](#7510), [#7295](#7295), and [#7565](#7565) -> `docs/changelog/2026-07-25.mdx`: Document gateway-scoped status, lifecycle diagnostics, managed MCP recovery, delete-edge safeguards, and fail-closed CLI prompt and command output. - [#7591](#7591) -> `docs/changelog/2026-07-25.mdx`: Document opt-in authenticated MCP tool-name discovery, its bounded and names-only contract, probe interaction, and rebuild requirement. - [#7305](#7305), [#7480](#7480), [#7471](#7471), [#7365](#7365), and [#7541](#7541) -> `docs/changelog/2026-07-25.mdx`: Document installer version checks, version-tag reporting, license guidance, WSL Ollama selection, and DGX Station vLLM detection. - [#7482](#7482), [#7466](#7466), [#7208](#7208), [#7434](#7434), and [#7586](#7586) -> `docs/changelog/2026-07-25.mdx`: Document Ollama resource details, reasoning precedence, Hermes onboarding behavior, and preserved managed Hermes BuildKit failures. - [#6830](#6830), [#7492](#7492), [#7563](#7563), and [#7582](#7582) -> `docs/changelog/2026-07-25.mdx`: Document the authoritative OpenClaw production lock, fixed managed-image dependencies, immutable Hermes base adoption, and Hermes image-size reduction. - [#7505](#7505), [#7530](#7530), [#7547](#7547), [#7508](#7508), [#7548](#7548), [#7549](#7549), [#7537](#7537), [#7534](#7534), [#7515](#7515), [#7511](#7511), [#7551](#7551), [#7562](#7562), [#7575](#7575), [#7496](#7496), [#7594](#7594), [#7595](#7595), and [#7599](#7599) -> `docs/changelog/2026-07-25.mdx`: Summarize release validation, transient and bounded dispatch reconciliation, exact pre-tag qualification, identity revalidation, npm-audit retry, sharding, image reuse, timeout, telemetry, and workflow-hardening changes. - Reconciled without separate changelog prose: - [#7539](#7539), [#7526](#7526), [#7507](#7507), [#7506](#7506), [#7519](#7519), [#7516](#7516), [#7396](#7396), [#7254](#7254), [#7583](#7583), [#7596](#7596), and [#7598](#7598): Test-harness or fixture-only changes. - [#7403](#7403), [#7161](#7161), [#6877](#6877), [#7531](#7531), [#7525](#7525), [#7522](#7522), [#7536](#7536), [#7552](#7552), [#7566](#7566), [#7553](#7553), [#7561](#7561), [#7577](#7577), [#7569](#7569), [#7585](#7585), [#7584](#7584), [#7592](#7592), [#7580](#7580), [#7571](#7571), [#7517](#7517), [#7589](#7589), [#7402](#7402), [#7558](#7558), [#7544](#7544), and [#7601](#7601): Dependency, internal recovery, validation, contributor-workflow, E2E optimization, telemetry, or CI trust changes with no separate user-facing release claim. - [#7556](#7556), [#7573](#7573), [#7576](#7576), and [#7578](#7578): Experimental repository-maintainer conflict automation with no canonical user documentation surface. ## Type of Change - [ ] Code change (feature, bug fix, or refactor) - [ ] Code change with doc updates - [x] Doc only (prose changes, no code sample modifications) - [ ] Doc only (includes code sample changes) ## Quality Gates - [ ] Tests added or updated for changed behavior - [x] Existing tests cover changed behavior — justification: `test/changelog-docs.test.ts` validates dated changelog structure, version headings, and published links. - [ ] Tests not applicable — justification: - [x] Docs updated for user-facing behavior changes - [ ] Docs not applicable — justification: - [ ] Sensitive paths changed (security, policy, credentials, preflight, onboarding, inference, runner, sandbox, or messaging) - [ ] Sensitive-path review completed or maintainer-approved waiver recorded — reviewer/approval link/justification: - [ ] Non-success, skipped, or missing CI check accepted by maintainer — check name, approval link, and follow-up issue: ## Documentation Writer Review - [x] Documentation writer subagent reviewed the completed changes - Result: `docs-updated` - Evidence: Reviewed `docs/changelog/2026-07-25.mdx` at exact head `0f5dedb47` against 90 first-parent release commits and 92 merged PRs labeled `v0.0.96`. Verified parser-safe MDX SPDX, the exact version heading, literal CLI names, writing style, skip terms, all 20 root-absolute published links, and the accepted #7591 opt-in authenticated discovery bounds. #7544, #7599, and #7601 remain internal or CI-only release-ledger entries. Changelog tests passed 6/6, the docs build passed with 0 errors and two pre-existing Fern warnings, and `npm run check:diff` plus the final diff check passed. - Agent: Codex Desktop documentation-writer subagent   ## DGX Station Hardware Evidence - [ ] Tested on DGX Station - Tested commit: - Station profile/scenario: - Result: - Supporting evidence: ## Verification - [x] PR description includes a `Signed-off-by:` line and every commit appears as `Verified` in GitHub - [x] Normal `pre-commit`, `commit-msg`, and `pre-push` hooks passed, or `npm run check:diff` passed when hooks were skipped or unavailable - [x] Targeted behavior tests pass for the current change set, or tests are marked not applicable above — `npx vitest run test/changelog-docs.test.ts`: 6/6 passed. - [ ] Applicable broad gate passed — `npm test` for broad runtime/test-harness changes; `npm run check` for repo-wide validation/coverage changes — command/result: Not applicable to this prose-only changelog entry. - [x] Quality Gates section completed with required justifications or waivers - [x] No secrets, API keys, or credentials committed - [ ] `npm run docs` builds without warnings (doc changes only) — the build passed with 0 errors and 2 existing Fern warnings; the published-route check passed. - [x] Doc pages follow the [style guide](https://github.com/NVIDIA/NemoClaw/blob/main/docs/CONTRIBUTING.md) (doc changes only) - [ ] New doc pages include SPDX header and frontmatter (new pages only) — native changelog files use the required parser-safe MDX SPDX comment and no frontmatter. --- Signed-off-by: Carlos Villela <cvillela@nvidia.com>  ## Summary by CodeRabbit * **New Features** * Persistent network policy exclusions with consistent restore/exclusion reporting across rebuilds/snapshots. * Opt-in MCP tool discovery via `mcp status --tools` with bounded, redacted authenticated traffic. * Improved HTTPS inference switching for custom endpoints and refreshed onboarding/model menu details. * Refined OpenShell gateway defaults for port `8080`, including more reliable readiness checks. * **Bug Fixes** * Prevent incorrect provider/model restoration after compatible-provider update failures. * Preserve managed MCP state after exec loss and tighten gateway/doctor status scoping. * **Tests** * Stronger, fail-closed release validation with hardened evidence/artifact handoff and bounded timeouts/retries.  --------- Signed-off-by: Prekshi Vyas <prekshiv@nvidia.com> Co-authored-by: Prekshi Vyas <prekshiv@nvidia.com>

ci(e2e): reuse the Hermes production image

c0ac9df

Signed-off-by: Charan Jagwani <cjagwani@nvidia.com>

cjagwani self-assigned this Jul 24, 2026

coderabbitai Bot reviewed Jul 24, 2026

View reviewed changes

Comment thread tools/e2e/sandbox-images-workflow-boundary.mts

coderabbitai Bot mentioned this pull request Jul 24, 2026

fix(security): update sandbox Perl runtime #7504

Merged

23 tasks

merge(main): resolve Hermes image workflow conflict

c2031f8

Signed-off-by: Charan Jagwani <cjagwani@nvidia.com>

cjagwani added the v0.0.96 label Jul 25, 2026

cv added 2 commits July 25, 2026 18:10

merge(main): refresh PR #7508

7ff3a7e

Signed-off-by: Carlos Villela <cvillela@nvidia.com>

test(e2e): harden Hermes image reuse contract

06261fd

Signed-off-by: Carlos Villela <cvillela@nvidia.com>

cv approved these changes Jul 26, 2026

View reviewed changes

cv merged commit baebfcb into main Jul 26, 2026
82 of 85 checks passed

cv deleted the codex/7451-hermes-image-reuse branch July 26, 2026 01:28

cv mentioned this pull request Jul 26, 2026

test(e2e): harden image reuse workflow validator #7551

Merged

23 tasks

cv mentioned this pull request Jul 26, 2026

test(e2e): reject continued Hermes consumer builds #7553

Merged

23 tasks

cjagwani mentioned this pull request Jul 26, 2026

ci: split E2E feedback-loop work into focused PRs #7451

Closed

9 tasks

cv mentioned this pull request Jul 26, 2026

docs: add v0.0.96 release entry #7564

Merged

23 tasks

wscurran added area: ci CI workflows, checks, release automation, or GitHub Actions area: e2e End-to-end tests, nightly failures, or validation infrastructure chore Build, CI, dependency, or tooling maintenance integration: hermes Hermes integration behavior labels Jul 29, 2026

apurvvkumaria mentioned this pull request Jul 30, 2026

Epic: reduce E2E wall time, runner cost, and failure surface #7912

Open

10 tasks

Navigation Menu

Uh oh!

ci(e2e): reuse the Hermes production image - #7508

ci(e2e): reuse the Hermes production image#7508
cv merged 4 commits into
mainfrom
codex/7451-hermes-image-reuse

cjagwani commented Jul 24, 2026 •

edited by coderabbitai Bot

Loading

Uh oh!

coderabbitai Bot commented Jul 24, 2026 •

edited

Loading

Walkthrough

Changes

Sequence Diagram(s)

Uh oh!

github-code-quality Bot commented Jul 24, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Jul 24, 2026 •

edited

Loading

Uh oh!

coderabbitai Bot left a comment

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

cjagwani commented Jul 24, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Related Issue

Changes

Type of Change

Quality Gates

Documentation Writer Review

DGX Station Hardware Evidence

Verification

Summary by CodeRabbit

Uh oh!

coderabbitai Bot commented Jul 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Sequence Diagram(s)

Uh oh!

github-code-quality Bot commented Jul 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Code Coverage Overview

TypeScript / code-coverage/plugin

Uh oh!

github-actions Bot commented Jul 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

PR Review Advisor — No blocking findings reported

Model lanes

E2E guidance

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

cjagwani commented Jul 24, 2026 •

edited by coderabbitai Bot

Loading

coderabbitai Bot commented Jul 24, 2026 •

edited

Loading

github-code-quality Bot commented Jul 24, 2026 •

edited

Loading

github-actions Bot commented Jul 24, 2026 •

edited

Loading