Skip to content

ci(e2e): isolate long-running scenario lanes#7448

Merged
cv merged 8 commits into
mainfrom
codex/e2e-long-lane-isolation
Jul 23, 2026
Merged

ci(e2e): isolate long-running scenario lanes#7448
cv merged 8 commits into
mainfrom
codex/e2e-long-lane-isolation

Conversation

@apurvvkumaria

@apurvvkumaria apurvvkumaria commented Jul 23, 2026

Copy link
Copy Markdown
Collaborator

Summary

Reduces the resource lifetime and failure blast radius of long-running network-policy and common-egress coverage, while removing one duplicate CLI build from security-posture setup. This is a draft for measuring the additional runner fan-out; it complements runner-loss handling but does not claim that sharding fixes hosted-runner disappearance.

Related Issue

Part of #7146. Parent epic: #7140.

Changes

  • Skip the duplicate CLI build in security-posture jobs.
  • Keep sandbox cleanup registered before installer execution and guard that ordering so a partially failed install cannot leak state into later runs.
  • Split network-policy coverage into independent live-probes and zero-presets scenarios with distinct sandboxes, artifact roots, and shard identities.
  • Split common-egress coverage into three agent/policy scenarios with distinct artifacts and cap matrix concurrency at two.
  • Keep each test deadline below its job deadline so every shard retains at least 20 minutes for cleanup and artifact finalization.
  • Protect scenario counts, selectors, concurrency, runner routing, artifact isolation, and teardown order with workflow-boundary tests.
  • Document the common-egress shards and concrete telemetry execution count in test/e2e/README.md.

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:
  • 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: Independent focused review verified bounded matrix concurrency, isolated artifact/sandbox identities, unchanged larger-runner routing, selector cardinality, and cleanup reserve. The PR remains draft until CI supplies fan-out measurements.
  • 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 accurately documents the updated 15-execution telemetry contract and the three common-egress scenario shards; the remaining changes affect only CI workflows, E2E isolation, and internal tests, so no canonical docs/ page is needed.
  • Agent: Codex Desktop

DGX Station Hardware Evidence

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

Verification

  • PR description includes a Signed-off-by: line and every commit appears as Verified in GitHub
  • Normal pre-commit, commit-msg, and pre-push hooks passed, or npm run check:diff passed when hooks were skipped or unavailable
  • Targeted behavior tests pass for the current change set, or tests are marked not applicable above — The original 6 focused workflow suites passed 93 tests; the latest cleanup/workflow rerun passed 61 tests across 3 suites; all five selectors resolve exactly one intended live test; semantic validation passed 123 tests across 82 files; the current-head selector-count regression test passed 1/1; CLI build/typecheck, commit hooks, pre-push checks, and the full diff-scoped hook set passed.
  • Applicable broad gate passed — npm test for broad runtime/test-harness changes; npm run check for repo-wide validation/coverage changes — command/result: Targeted workflow, selector, semantic, type, Markdown, and diff-scoped gates passed; GitHub CI is authoritative for the repository-wide gate.
  • 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)
  • Doc pages follow the style guide (doc changes only)
  • New doc pages include SPDX header and frontmatter (new pages only)

Signed-off-by: Apurv Kumaria akumaria@nvidia.com

Summary by CodeRabbit

  • CI / E2E Improvements

    • Expanded live end-to-end coverage with isolated scenario runs for network policy and egress agent testing.
    • Improved scenario-specific test selection, artifact storage, naming, and parallel execution.
    • Updated security posture setup to use the no-build workflow.
  • Validation & Reliability

    • Added checks for workflow isolation, cleanup ordering, artifact contracts, and scenario configuration.
    • Updated E2E telemetry documentation and shard expectations to reflect the expanded coverage.

Signed-off-by: Apurv Kumaria <akumaria@nvidia.com>
Signed-off-by: Apurv Kumaria <akumaria@nvidia.com>
Signed-off-by: Apurv Kumaria <akumaria@nvidia.com>
Signed-off-by: Apurv Kumaria <akumaria@nvidia.com>
@apurvvkumaria apurvvkumaria added area: ci CI workflows, checks, release automation, or GitHub Actions area: e2e End-to-end tests, nightly failures, or validation infrastructure area: performance Latency, throughput, resource use, benchmarks, or scaling v0.0.93 labels Jul 23, 2026
@apurvvkumaria apurvvkumaria self-assigned this Jul 23, 2026
@copy-pr-bot

copy-pr-bot Bot commented Jul 23, 2026

Copy link
Copy Markdown

Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

@coderabbitai

coderabbitai Bot commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

E2E workflows now run network-policy and common-egress-agent through scenario matrices with selector-based execution and isolated artifacts. Workflow validators and regression tests enforce the new contracts, while security-posture uses no-build preparation.

Changes

E2E scenario execution and validation

Layer / File(s) Summary
Scenario matrix workflow execution
.github/workflows/e2e.yaml, test/e2e/README.md
Adds scenario-specific execution, selectors, environment bindings, artifact paths, upload names, and updated telemetry documentation.
Workflow boundary contracts
tools/e2e/workflow-boundary.mts, tools/e2e/upload-e2e-artifacts-workflow-boundary.mts, tools/e2e/prepare-e2e-workflow-boundary.mts
Enforces scenario matrices, timeouts, concurrency, selector commands, explicit artifact contracts, and no-build preparation for security-posture.
Boundary and cleanup regression coverage
test/e2e/support/*, test/pr-e2e-gate-signal-shards.test.ts
Adds validation tests for scenario isolation, artifact contracts, no-build behavior, cleanup ordering, and updated shard counts.

Estimated code review effort: 3 (Moderate) | ~25 minutes

Sequence Diagram(s)

sequenceDiagram
  participant GitHubActions
  participant Vitest
  participant ArtifactUpload
  GitHubActions->>Vitest: Run matrix.selector for each scenario
  Vitest->>ArtifactUpload: Produce scenario-scoped output
  GitHubActions->>ArtifactUpload: Upload scenario-named artifacts
Loading

Possibly related PRs

  • NVIDIA/NemoClaw#7399: Both update tools/e2e/workflow-boundary.mts within the E2E workflow validation flow.
  • NVIDIA/NemoClaw#7444: Both update security-posture workflow validation around shared workflow steps.

Suggested labels: chore, v0.0.93

Suggested reviewers: cv, cjagwani, jyaunches

🚥 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 Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly matches the main change: isolating long-running E2E scenario lanes in CI.
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/e2e-long-lane-isolation

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

@github-code-quality

github-code-quality Bot commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

Code Coverage Overview

Languages: TypeScript

TypeScript / code-coverage/plugin

The overall coverage in commit a409fcc in the codex/e2e-long-lane-... branch remains at 96%, unchanged from commit 0670d20 in the main branch.

TypeScript / code-coverage/cli

The overall coverage in commit a409fcc in the codex/e2e-long-lane-... branch remains at 80%, unchanged from commit 0670d20 in the main branch.

Show a code coverage summary of the most impacted files.
File main 0670d20 codex/e2e-long-lane-... a409fcc +/-
src/lib/platform.ts 89% 84% -5%
src/lib/adapter...shell/client.ts 90% 88% -2%
src/lib/messagi...nnels/policy.ts 100% 100% 0%
src/lib/sandbox...rce-identity.ts 87% 87% 0%
src/lib/securit...ntial-filter.ts 93% 93% 0%
src/lib/trace.ts 94% 94% 0%
src/lib/tunnel/services.ts 73% 73% 0%
src/lib/domain/.../connect-env.ts 89% 97% +8%

Updated July 23, 2026 23:28 UTC

@github-actions

github-actions Bot commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

PR Review Advisor — Informational

Advisor assessment: Informational / high confidence
Next action: No advisor follow-up needed.
Findings: 0 blockers · 0 warnings · 0 suggestions
Status: No actionable findings remain in the canonical review ledger.

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 · 0 warnings · 0 suggestions
  • Model comparison: normalized findings match; normalized E2E selections differ; severity counts match.

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

2 optional E2E recommendations
  • network-policy
  • common-egress-agent

Workflow run details

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

Signed-off-by: Apurv Kumaria <akumaria@nvidia.com>
Signed-off-by: Apurv Kumaria <akumaria@nvidia.com>
@cv cv added v0.0.94 and removed v0.0.95 labels Jul 23, 2026
Signed-off-by: Apurv Kumaria <akumaria@nvidia.com>
Signed-off-by: Apurv Kumaria <akumaria@nvidia.com>
@apurvvkumaria
apurvvkumaria marked this pull request as ready for review July 23, 2026 23:20
@apurvvkumaria
apurvvkumaria requested a review from cv July 23, 2026 23:29

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🧹 Nitpick comments (1)
test/e2e/support/e2e-cleanup-resources.test.ts (1)

112-129: 📐 Maintainability & Code Quality | 🔵 Trivial | 🏗️ Heavy lift

Replace source-text assertions with behavioral contract tests.

The indexOf comparison can pair unrelated occurrences, while the timeout checks lock in private constant spelling rather than proving cleanup reserve behavior.

  • test/e2e/support/e2e-cleanup-resources.test.ts#L112-L129: use a fake host/installer boundary and assert cleanup is registered before an installer failure.
  • test/e2e/support/e2e-workflow.test.ts#L81-L82: assert the network-policy timing budget through an explicit, validated contract rather than file text.
  • test/e2e/support/e2e-workflow.test.ts#L127-L128: assert the common-egress timing budget through the same public contract.

As per path instructions, “Prefer observable outcomes through the public boundary over source-text, private-shape, or mock-call assertions.”

🤖 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 `@test/e2e/support/e2e-cleanup-resources.test.ts` around lines 112 - 129,
Replace the source-text ordering test in
test/e2e/support/e2e-cleanup-resources.test.ts:112-129 with a fake
host/installer boundary that verifies cleanup registration occurs before an
installer failure. In test/e2e/support/e2e-workflow.test.ts:81-82 and :127-128,
replace timeout/source-text checks with explicit validated assertions through
the public timing contract for the network-policy and common-egress reserve
budgets, respectively; update each site as requested and avoid private constant
names or mock-call assertions.

Source: Path instructions

🤖 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.

Nitpick comments:
In `@test/e2e/support/e2e-cleanup-resources.test.ts`:
- Around line 112-129: Replace the source-text ordering test in
test/e2e/support/e2e-cleanup-resources.test.ts:112-129 with a fake
host/installer boundary that verifies cleanup registration occurs before an
installer failure. In test/e2e/support/e2e-workflow.test.ts:81-82 and :127-128,
replace timeout/source-text checks with explicit validated assertions through
the public timing contract for the network-policy and common-egress reserve
budgets, respectively; update each site as requested and avoid private constant
names or mock-call assertions.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 42c41052-00ec-458e-a209-9567a54c6974

📥 Commits

Reviewing files that changed from the base of the PR and between 0670d20 and a409fcc.

📒 Files selected for processing (10)
  • .github/workflows/e2e.yaml
  • test/e2e/README.md
  • test/e2e/support/e2e-cleanup-resources.test.ts
  • test/e2e/support/e2e-workflow.test.ts
  • test/e2e/support/prepare-e2e-workflow-boundary.test.ts
  • test/e2e/support/upload-e2e-artifacts-workflow-boundary.test.ts
  • test/pr-e2e-gate-signal-shards.test.ts
  • tools/e2e/prepare-e2e-workflow-boundary.mts
  • tools/e2e/upload-e2e-artifacts-workflow-boundary.mts
  • tools/e2e/workflow-boundary.mts

@cv
cv merged commit e84f5ee into main Jul 23, 2026
89 of 96 checks passed
@cv
cv deleted the codex/e2e-long-lane-isolation branch July 23, 2026 23:38
apurvvkumaria added a commit that referenced this pull request Jul 24, 2026
<!-- markdownlint-disable MD041 -->
## Summary
This adds bounded periodic and phase-aware resource telemetry to the
canonical runner-comparison ledger for trusted heavy E2E executions. It
reuses the existing progress pulse and records only numeric or
fixed-enum evidence, improving runner-pressure diagnosis without
changing failure classification or retry policy.

## Related Issue
Related to #7145 and #7146 (parent epic: #7140).

## Changes
- Extend the canonical runner-comparison artifact to a bounded v2
lifecycle with private `0600` files, a reserved final sample, v1 read
compatibility, and deterministic summaries.
- Capture bounded host, cgroup, PSI, filesystem, Docker, container, and
coarse process-class evidence at endpoints, phase boundaries, and an
approximately 60-second cadence.
- Reuse the existing progress timer with fixed deadlines, no catch-up
bursts, per-scenario attribution boundaries, and a permanent fallback to
the existing bounded collector if canonical sampling fails.
- Add focused privacy, compatibility, timing, fallback, aggregation,
summary, and workflow-boundary coverage, including the three-shard
`common-egress-agent` topology merged in #7448.
- Document the telemetry lifecycle, probe budgets, privacy limits,
compatibility behavior, and the separation from classification and
retry. This builds on the merged progress/timing work from #7100 and
#7213 and extends the canonical ledger from #7399 rather than creating
parallel infrastructure.

## Type of Change

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

## Quality Gates
<!-- Check one tests line and one docs line. Check other lines when
applicable. Add every requested justification or approval reference. -->
- [x] Tests added or updated for changed behavior
- [ ] Existing tests cover changed behavior — justification:
- [ ] Tests not applicable — justification:
- [x] Docs updated for user-facing behavior changes
- [ ] Docs not applicable — justification:
- [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: Independent exact-head
privacy, schema, classifier, retry, and compatibility review at
`419182d89` found no actionable issues.
- [ ] Non-success, skipped, or missing CI check accepted by maintainer —
check name, approval link, and follow-up issue:

## Documentation Writer Review
<!-- Required for code and documentation changes after the changes and
applicable validation are complete. Keep one review checkbox and one
instance of each visible or hidden field. For Evidence, list changed
documentation paths. For documentation-only changes, also state that the
writing rules and documentation style were reviewed. For other results,
explain why no documentation change is needed or why the review is
blocked. For Agent, use a consistent product and surface name, such as
Codex Desktop, Codex CLI, Claude Code, or Cursor. After committing all
review changes, put `git rev-parse --short HEAD` and `git rev-parse
--short HEAD:AGENTS.md` in the hidden metadata below. Rerun the review
and refresh that metadata after any new commit. This receipt is advisory
during the data-collection pilot. -->
- [x] Documentation writer subagent reviewed the completed changes
- Result: `docs-updated`
- Evidence: `test/e2e/README.md`
- Agent: Codex Desktop
<!-- docs-review-head-sha: e06653c -->
<!-- docs-review-agents-blob-sha:
9c9b36d -->

## DGX Station Hardware Evidence
<!-- Required only when scripts/prepare-dgx-station-host.sh changes.
Maintainers must review the linked evidence before approving or merging.
This is human-reviewed evidence, not authenticated hardware provenance.
Exceptional bypasses use existing repository governance and must be
documented on the PR. -->
- [ ] Tested on DGX Station
- Tested commit:
- Station profile/scenario:
- Result:
- Supporting evidence:

## Verification
<!-- Check each applicable item only when supported by the requested
evidence. Run targeted tests once per relevant change set and rerun
after later edits or hook autofixes that can affect the tested behavior.
Do not rerun hook-covered checks. -->
- [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 — command/result or justification:
Exact-head serialized telemetry/progress/workflow suite passed 225/225
tests across 15 files; after the linear-test guardrail repair, the
primary focused suite passed 165/165 across 9 files, Vitest membership
was exact across 1,764 files, CLI typecheck passed, and `npm run
check:diff` passed.
- [ ] Applicable broad gate passed — `npm test` for broad
runtime/test-harness changes; `npm run check` for repo-wide
validation/coverage changes — command/result: A broad E2E-support run
exposed only parallel-load timeouts and one macOS lifecycle failure
reproduced unchanged on `origin/main`; scoped exact-head gates are
listed above.
- [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)
- [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)

---
<!-- DCO sign-off is required in this PR description, and every commit
must appear as Verified in GitHub. Run: git config user.name && git
config user.email -->
Signed-off-by: Apurv Kumaria <akumaria@nvidia.com>


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

* **New Features**
* Added runner-comparison schema v2 telemetry as a bounded, ordered
ledger with periodic, scenario-start, phase, and finalize samples.
* Enabled live E2E runner-comparison sampling and added conditional
periodic sampling in the E2E progress harness.
* Introduced pulse-based progress resource sampling with configurable
interval and best-effort phase/scenario capture.

* **Bug Fixes / Improvements**
* Switched memory diagnostics to available-memory reporting (with
free-memory fallback labeling).
* Hardened telemetry parsing/validation, evidence sanitization, and
expanded runner-pressure/resource diagnostics.

* **Documentation**
* Documented v2 ordering/cadence, privacy/size limits, and
diagnostic-only summary guidance.

* **Tests**
* Added/expanded E2E tests for v2 schema validation, timing/cadence,
fallback behavior, and updated expected outputs.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Signed-off-by: Apurv Kumaria <akumaria@nvidia.com>
Signed-off-by: Prekshi Vyas <prekshiv@nvidia.com>
Co-authored-by: Prekshi Vyas <prekshiv@nvidia.com>
@prekshivyas prekshivyas mentioned this pull request Jul 24, 2026
23 tasks
prekshivyas added a commit that referenced this pull request Jul 24, 2026
<!-- markdownlint-disable MD041 -->
## Summary

This PR adds the canonical dated release entry for NemoClaw v0.0.94
before the tag is cut.
The entry reconciles all 26 commits since v0.0.93 and links each
user-visible change to its owning documentation.

## Changes

- Add `docs/changelog/2026-07-24.mdx` with the exact `## v0.0.94`
heading, parser-safe SPDX comment, release summary, and detailed
bullets.
- Record sandbox restore and update behavior, onboarding and inference
changes, network policy behavior, security evidence, Hermes build
performance, DGX Station guidance, and E2E validation changes.
- Preserve `docs/` as the source of truth without changing the AI-agent
documentation routing skill.
- Use [E2E run
30075443016](https://github.com/NVIDIA/NemoClaw/actions/runs/30075443016)
for release QA evidence at exact tested SHA
`04e6dfa883071dda9df429c66e73168e1a995cba`.

### Source summary

- [#7461](#7461) ->
`docs/changelog/2026-07-24.mdx`: Record the ownership-preserving Hermes
image layer reduction and hosted timing comparison.
- [#7460](#7460) ->
`docs/changelog/2026-07-24.mdx`: Record removal of candidate Hermes swap
setup from E2E validation.
- [#7458](#7458) ->
`docs/security/fern-5.80.1-dependency-review.md`,
`docs/changelog/2026-07-24.mdx`: Record the reviewed Fern CLI update.
- [#7457](#7457) ->
`docs/changelog/2026-07-24.mdx`: Record periodic runner-pressure
telemetry.
- [#7455](#7455) ->
`docs/changelog/2026-07-24.mdx`: Record non-blocking absent Fern
previews.
- [#7450](#7450) ->
`docs/changelog/2026-07-24.mdx`: Record stable cancellation handling for
live-test child processes.
- [#7449](#7449) ->
`docs/changelog/2026-07-24.mdx`: Record parallel plugin EXDEV coverage.
- [#7448](#7448) ->
`docs/changelog/2026-07-24.mdx`: Record isolated long-running E2E lanes.
- [#7444](#7444) ->
`docs/changelog/2026-07-24.mdx`: Record exact-head Hermes swap
validation.
- [#7437](#7437) ->
`docs/manage-sandboxes/backup-restore.mdx`,
`docs/changelog/2026-07-24.mdx`: Record gateway pairing and
authenticated verification after cross-sandbox restore.
- [#7436](#7436) ->
`docs/manage-sandboxes/backup-restore.mdx`,
`docs/reference/commands.mdx`, `docs/changelog/2026-07-24.mdx`: Record
selected stale-state cleanup and Hermes virtual-environment access
repair.
- [#7385](#7385) ->
`docs/network-policy/customize-network-policy.mdx`,
`docs/changelog/2026-07-24.mdx`: Record the read-only agent-variant
route check.
- [#7371](#7371) ->
`docs/changelog/2026-07-24.mdx`: Record host-artifact verification for
session exports.
- [#7359](#7359) ->
`docs/changelog/2026-07-24.mdx`: Record platform validation for managed
vLLM model overrides.
- [#7356](#7356) ->
`docs/changelog/2026-07-24.mdx`: Record token-shaped value redaction for
`sandbox doctor --json`.
- [#7354](#7354) ->
`docs/security/advisory-early-warning.md`,
`docs/changelog/2026-07-24.mdx`: Record advisory correlation and
retained audit provenance.
- [#7352](#7352) ->
`docs/network-policy/customize-network-policy.mdx`,
`docs/network-policy/integration-policy-examples.mdx`,
`docs/reference/commands.mdx`, `docs/changelog/2026-07-24.mdx`: Record
preset reapplication and bounded `tls: skip` guidance.
- [#7345](#7345) ->
`docs/security/openclaw-2026.6.10-dependency-review.md`,
`docs/security/openclaw-2026.7.1-dependency-review.md`,
`docs/changelog/2026-07-24.mdx`: Record reviewed npm audit exception
enforcement.
- [#7340](#7340) ->
`docs/network-policy/customize-network-policy.mdx`,
`docs/changelog/2026-07-24.mdx`: Record the repaired CLI-reference
route.
- [#7334](#7334) ->
`docs/get-started/dgx-station-preparation.mdx`,
`docs/changelog/2026-07-24.mdx`: Record the qualified OTA metadata
fallback and narrowed override wording.
- [#7322](#7322) ->
`docs/changelog/2026-07-24.mdx`: Reconcile the gateway source tag added
to plugin registration banners.
- [#7284](#7284) ->
`docs/manage-sandboxes/update-sandboxes.mdx`,
`docs/changelog/2026-07-24.mdx`: Record read-only `upgrade-sandboxes
--check` behavior and recorded-gateway selection.
- [#7277](#7277) ->
`docs/changelog/2026-07-24.mdx`: Reconcile deterministic gateway TCP
refusal coverage.
- [#7234](#7234) ->
`docs/reference/troubleshooting.mdx`, `docs/changelog/2026-07-24.mdx`:
Record preserved DGX Spark managed vLLM Express intent on resume.
- [#7185](#7185) ->
`docs/reference/troubleshooting.mdx`, `docs/changelog/2026-07-24.mdx`:
Record IPv4 fallback DNS selection and exact resolver probing.
- [#6820](#6820) ->
`docs/reference/commands.mdx`, `docs/changelog/2026-07-24.mdx`: Record
the versioned, redacted `--events=jsonl` onboarding stream.

## 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: `npx vitest
run test/changelog-docs.test.ts` passed 6/6 tests.
- [ ] 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: `docs/changelog/2026-07-24.mdx`; the writing rules,
documentation style, exact release range, skip terms, published routes,
and product scope were reviewed; the changelog test passed 6/6; `npm run
docs` passed with route checking OK, zero errors, and two existing
warnings.
- Agent: Codex Desktop
<!-- docs-review-head-sha: 65368f9 -->
<!-- docs-review-agents-blob-sha: 9c9b36d -->

## DGX Station Hardware Evidence

- [ ] Tested on DGX Station
- Tested commit: Not applicable
- Station profile/scenario: Not applicable
- Result: Not applicable
- Supporting evidence: Not applicable. This PR does not change
`scripts/prepare-dgx-station-host.sh`.

## 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` passed 6/6 tests.
- [ ] 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 the
dated 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 zero errors and two existing Fern warnings.
- [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 dated changelog entries use the required parser-safe MDX
SPDX comment and no frontmatter.

---
Signed-off-by: Prekshi Vyas <prekshiv@nvidia.com>


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

## Summary by CodeRabbit

* **Documentation**
  * Added the v0.0.94 release changelog.
  * Documented improvements to sandbox snapshot and restore behavior.
* Added updates for gateway selection, policy comparisons, onboarding
event output, and DGX recovery workflows.
* Documented enhanced diagnostics redaction, npm audit provenance, image
assembly performance, and validation stability improvements.


<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Signed-off-by: Prekshi Vyas <prekshiv@nvidia.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: ci CI workflows, checks, release automation, or GitHub Actions area: e2e End-to-end tests, nightly failures, or validation infrastructure area: performance Latency, throughput, resource use, benchmarks, or scaling

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants