fix(onboard): print created sandbox readiness receipt by HOYALIM · Pull Request #6620 · NVIDIA/NemoClaw

HOYALIM · 2026-07-10T00:36:25Z

Summary

Refs #3344. This is a narrow diagnostics slice for the created-but-not-ready onboard path; it does not change timeout budgets, cleanup behavior, or sandbox lifecycle semantics.

add a stable sandbox lifecycle receipt when a created sandbox never reaches Ready
include the sandbox name, readiness gate/reason, create-stream status, timeout, and terminal cleanup resolution
make the successful cleanup line name the exact sandbox target so retry-safety is evidenced instead of implied

Validation

npx vitest run --project cli src/lib/onboard/created-sandbox-failure.test.ts src/lib/onboard/sandbox-readiness-tracing.test.ts
npm run build:cli
npm run typecheck
npx prek run --files src/lib/onboard/created-sandbox-failure.ts src/lib/onboard/created-sandbox-failure.test.ts --stage pre-commit
npm run check:diff

DCO verification

Signed-off-by: Ho Lim subhoya@gmail.com

Summary by CodeRabbit

Bug Fixes
- Improved day-0 onboarding failure reporting for “created but not ready” sandboxes with consistent lifecycle receipt output.
- Standardized lifecycle receipt details, including readiness gate and terminal-resolution across GPU patch, timed-out deleted/retained, and terminal failure outcomes.
- Enhanced retry/cleanup guidance when sandbox deletion succeeds or requires manual intervention.
Tests
- Strengthened validations to assert the exact, ordered “Sandbox lifecycle receipt” lines for multiple terminal scenarios and failurePhase variations.

copy-pr-bot · 2026-07-10T00:36:28Z

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

Copilot

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

coderabbitai · 2026-07-10T00:36:46Z

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: 031e974d-67fd-43fd-a745-3cd77f101299

📥 Commits

Reviewing files that changed from the base of the PR and between 78642ca and d098cdc.

📒 Files selected for processing (2)

src/lib/onboard/created-sandbox-failure.test.ts
src/lib/onboard/created-sandbox-failure.ts

🚧 Files skipped from review as they are similar to previous changes (2)

src/lib/onboard/created-sandbox-failure.test.ts
src/lib/onboard/created-sandbox-failure.ts

📝 Walkthrough

Walkthrough

Adds stable “created-but-not-ready” sandbox lifecycle receipts and integrates them into readiness-failure reporting for deferred cleanup, deleted sandboxes, retained sandboxes, and terminal readiness failures. Tests verify receipt contents and terminal-resolution output.

Changes

Sandbox readiness failure receipts

Layer / File(s)	Summary
Readiness receipt formatting `src/lib/onboard/created-sandbox-failure.ts`	Adds terminal-resolution mappings and formats sandbox state, readiness details, create status, timeout, and terminal resolution into stable receipt lines.
Failure reporting integration and coverage `src/lib/onboard/created-sandbox-failure.ts`, `src/lib/onboard/created-sandbox-failure.test.ts`	Emits receipts for deferred, deleted, retained, timed-out, and terminal-phase outcomes, with exact ordered assertions for each path.

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

Suggested labels: bug-fix, area: onboarding, area: sandbox

Suggested reviewers: cv

🚥 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 matches the main change: printing a created sandbox readiness receipt for onboard failures.
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 unit tests (beta)

Create PR with unit tests

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

coderabbitai

Actionable comments posted: 2

🤖 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 `@src/lib/onboard/created-sandbox-failure.test.ts`:
- Around line 213-222: Extend the integration tests around
reportSandboxReadinessFailure to assert the complete emitted receipt, including
its header/state and branch-specific gate and reason lines, for delete,
retained, GPU-deferred, and terminal-phase scenarios. Add coverage for null and
empty terminal-phase fallbacks, asserting literal emitted lines directly rather
than invoking the production formatter, while preserving tests through the
public entrypoint and verifying observable behavior.

In `@src/lib/onboard/created-sandbox-failure.ts`:
- Around line 108-114: Update readinessGate to treat an empty failurePhase the
same as null or undefined, returning the stable "terminal_failure" fallback
instead of an empty gate suffix; adjust the failurePhase fallback logic in
readinessGate while preserving the existing terminal and timeout gate values.

🪄 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: ad27bb27-bcbb-4548-8c65-266159fefe89

📥 Commits

Reviewing files that changed from the base of the PR and between ad518b3 and a69567b.

📒 Files selected for processing (2)

src/lib/onboard/created-sandbox-failure.test.ts
src/lib/onboard/created-sandbox-failure.ts

coderabbitai

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 `@src/lib/onboard/created-sandbox-failure.test.ts`:
- Around line 268-291: Add a public-boundary test alongside the existing
terminal-failure readiness tests using deleteSandbox: vi.fn(() => ({ status: 1
})) in the readiness dependencies, then invoke reportSandboxReadinessFailure and
assert the lifecycle receipt contains terminal_resolution:
terminal_failure_retained. Keep the existing successful-deletion coverage for
terminal_failure_deleted.

🪄 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: fc19e813-55f6-4bb4-aced-976887c890b2

📥 Commits

Reviewing files that changed from the base of the PR and between a69567b and 78642ca.

📒 Files selected for processing (2)

src/lib/onboard/created-sandbox-failure.test.ts
src/lib/onboard/created-sandbox-failure.ts

🚧 Files skipped from review as they are similar to previous changes (1)

src/lib/onboard/created-sandbox-failure.ts

Signed-off-by: Ho Lim <subhoya@gmail.com>

HOYALIM · 2026-07-10T00:51:38Z

@coderabbitai review

coderabbitai · 2026-07-10T00:51:55Z

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

prekshivyas · 2026-07-11T07:00:18Z

E2E Advisor Recommendation

Required E2E: onboard-repair, onboard-resume, cloud-onboard
Optional E2E: None

Dispatch hint: onboard-repair,onboard-resume

Workflow run

Full advisor summary

E2E Recommendation Advisor

Base: target/main
Head: HEAD
Confidence: high

Required E2E

onboard-repair: Required by the deterministic risk plan for lifecycle-state changes. The changed readiness-failure cleanup/receipt logic can affect repair convergence after partially created or retained sandboxes.
onboard-resume: Required by the deterministic risk plan for lifecycle-state changes. The changed created-but-not-ready handling can affect retry/resume behavior after a sandbox exists but onboarding did not reach Ready.
cloud-onboard (high): Changed onboard, trace timing, scorecard, or E2E workflow code can affect cloud onboard wall-clock behavior and should refresh the trusted cloud-onboard trace timing signal.

Optional E2E

None.

New E2E recommendations

created-sandbox-readiness-failure (medium): The PR adds a stable lifecycle receipt for created-but-not-ready failures, including readiness gate, cleanup result, and terminal resolution. Existing required resume/repair jobs validate convergence, but a focused live failure-path E2E would directly assert the receipt contract and cleanup behavior when readiness polling times out or reaches a terminal phase.
- Suggested test: Add a live E2E scenario that forces a created sandbox to fail readiness, asserts the Sandbox lifecycle receipt fields, and verifies delete-vs-retain behavior before retry.

Dispatch hint

Workflow: .github/workflows/e2e.yaml
jobs input: onboard-repair,onboard-resume

prekshivyas · 2026-07-11T07:00:19Z

E2E Target Recommendation

Required E2E targets: onboard-repair, onboard-resume
Optional E2E targets: None

Dispatch required E2E targets:

gh workflow run e2e.yaml --ref <pr-head-ref> --field jobs=onboard-repair
gh workflow run e2e.yaml --ref <pr-head-ref> --field jobs=onboard-resume

Workflow run

Full E2E target advisor summary

E2E Target Advisor

Base: target/main
Head: HEAD
Confidence: high

Required E2E targets

onboard-repair: Onboarding and sandbox state must converge across persisted metadata, reported status, and the live runtime.
- Dispatch: gh workflow run e2e.yaml --ref <pr-head-ref> --field jobs=onboard-repair
onboard-resume: Onboarding and sandbox state must converge across persisted metadata, reported status, and the live runtime.
- Dispatch: gh workflow run e2e.yaml --ref <pr-head-ref> --field jobs=onboard-resume

Optional E2E targets

None.

Relevant changed files

src/lib/onboard/created-sandbox-failure.ts
src/lib/onboard/created-sandbox-failure.test.ts

cv

Exact-head maintainer gate passed at d098cdc. Standard CI, DCO, CodeRabbit, Verified commit, dual trusted advisors, and onboard-repair/onboard-resume/cloud-onboard live runs are settled. GPT returned merge_as_is with zero findings. Nemotron’s only warning is a mechanical test-file overlap with #6445’s gitleaks comments, not semantic interference or a code blocker.

## Summary Release-prep documentation for v0.0.81 now summarizes user-facing changes merged since v0.0.80. It also closes the Hermes dashboard-profile backup gap and distinguishes direct blueprint-runner actions from public host CLI commands. ## Changes - Add the `v0.0.81` section to `docs/about/release-notes.mdx` with links to the detailed user guides. - Document that Hermes rebuilds preserve `.hermes/dashboard-home/`, including Dashboard `MEMORY.md` and `USER.md`. - Update Hermes manual backup and restore examples to transfer those two profile files without copying generated configuration or the secret-bearing dashboard `.env`. - Explain the new per-item backup failure causes. - Clarify that migration snapshot retention fragments are direct-runner arguments and are not exposed by the host `nemoclaw` CLI. ### Source summary - #6445 -> `docs/about/release-notes.mdx`, `docs/manage-sandboxes/backup-restore.mdx`, and `docs/manage-sandboxes/workspace-files.mdx`: Summarize manifest-owned key-level restore and current-config authority. - #6617 -> `docs/about/release-notes.mdx` and `docs/manage-sandboxes/backup-restore.mdx`: Record the fail-closed `/proc` fallback used to verify an idle Deep Agents runtime before snapshot creation. - #6685 -> `docs/about/release-notes.mdx`, `docs/manage-sandboxes/backup-restore.mdx`, and `docs/manage-sandboxes/workspace-files.mdx`: Document Hermes Web Dashboard profile persistence and safe manual transfer. - #6649 -> `docs/about/release-notes.mdx`: Summarize host-validated loopback compatible-endpoint routing through the sandbox gateway. - #6643 -> `docs/about/release-notes.mdx`: Summarize automatic `max_completion_tokens` handling for GPT-5 and o-series models. - #6661 -> `docs/about/release-notes.mdx`: Summarize bounded connection reuse for eligible provider-validation probes. - #6704 -> `docs/about/release-notes.mdx`: Record that direct blueprint apply stops instead of persisting incomplete state after provider or inference setup fails. - #6677 -> `docs/about/release-notes.mdx`: Summarize transactional recovery for legacy Docker containers whose managed supervisor disappeared after restart. - #6625 -> `docs/about/release-notes.mdx`: Record Hermes managed-startup persistence across direct Docker restarts. - #6597 -> `docs/about/release-notes.mdx`: Record final-sandbox gateway cleanup on macOS. - #6680 -> `docs/about/release-notes.mdx`: Summarize managed Deep Agents first-run and process-tree cleanup improvements. - #6647 -> `docs/about/release-notes.mdx`: Record fail-closed validation for the managed Deep Agents fetch CA bundle. - #6645 -> `docs/about/release-notes.mdx`: Summarize WhatsApp loopback pairing and trusted npm plugin provenance. - #6673 -> `docs/about/release-notes.mdx` and `docs/manage-sandboxes/backup-restore.mdx`: Document stopped-sandbox backup remediation. - #6631 -> `docs/about/release-notes.mdx` and `docs/manage-sandboxes/backup-restore.mdx`: Document per-item backup failure causes. - #6620 -> `docs/about/release-notes.mdx`: Record the created-but-not-ready sandbox lifecycle receipt. - #6664 -> `docs/about/release-notes.mdx`: Record prompt-aware onboarding progress output. - #6598 -> `docs/about/release-notes.mdx`: Summarize stale replay-result invalidation during resumed onboarding. - #6593 -> `docs/about/release-notes.mdx`: Summarize contextual OpenClaw audit findings for managed dashboard compatibility settings. - #6650 -> `docs/about/release-notes.mdx`: Record redaction of token-shaped URL query values. - #6638 -> `docs/about/release-notes.mdx`: Record the exact-path MCP `DELETE` policy recipe for session termination. - #5453 -> `docs/reference/host-files-and-state.mdx`: Clarify that snapshot retention actions belong to direct runner integrations and are not standalone host CLI commands. ### Skipped from docs-skip - #6633 matched the `openclaw-sandbox-permissive.yaml` path in `docs/.docs-skip` and produced no documentation in this update. ## Type of Change - [ ] Code change (feature, bug fix, or refactor) - [ ] Code change with doc updates - [ ] Doc only (prose changes, no code sample modifications) - [x] Doc only (includes code sample changes) ## Quality Gates - [ ] Tests added or updated for changed behavior - [ ] Existing tests cover changed behavior — justification: - [x] Tests not applicable — justification: This is a documentation-only release-prep update; behavior is protected by the merged source PRs, and the documentation build validates the changed examples and routes. - [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: ## Verification - [x] PR description includes the DCO sign-off declaration 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 — tests are not applicable for this documentation-only change; `npm run docs` completed successfully. - [ ] Applicable broad gate passed — `npm test` for broad runtime/test-harness changes; `npm run check` for repo-wide validation/coverage changes — command/result: not run for this documentation-only change. - [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) — 0 errors; two existing Fern warnings remain. - [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) — no new pages. --- Signed-off-by: Carlos Villela <cvillela@nvidia.com>  ## Summary by CodeRabbit - **Documentation** - Added release notes for v0.0.81 covering state preservation, inference setup, sandbox recovery, session setup, pairing, diagnostics, and security policy updates. - Expanded backup and restore guidance to include dashboard profile files and clarify files that must not be copied. - Added dashboard profile persistence details to workspace and rebuild documentation. - Clarified snapshot retention guidance and the distinction between host CLI capabilities and direct runner actions. - Added more detailed backup failure reporting information.  Signed-off-by: Carlos Villela <cvillela@nvidia.com>

## Summary Refs NVIDIA#3344. This is a narrow diagnostics slice for the created-but-not-ready onboard path; it does not change timeout budgets, cleanup behavior, or sandbox lifecycle semantics. - add a stable sandbox lifecycle receipt when a created sandbox never reaches Ready - include the sandbox name, readiness gate/reason, create-stream status, timeout, and terminal cleanup resolution - make the successful cleanup line name the exact sandbox target so retry-safety is evidenced instead of implied ## Validation - `npx vitest run --project cli src/lib/onboard/created-sandbox-failure.test.ts src/lib/onboard/sandbox-readiness-tracing.test.ts` - `npm run build:cli` - `npm run typecheck` - `npx prek run --files src/lib/onboard/created-sandbox-failure.ts src/lib/onboard/created-sandbox-failure.test.ts --stage pre-commit` - `npm run check:diff` ## DCO verification Signed-off-by: Ho Lim <subhoya@gmail.com>  ## Summary by CodeRabbit * **Bug Fixes** * Improved day-0 onboarding failure reporting for “created but not ready” sandboxes with consistent lifecycle receipt output. * Standardized lifecycle receipt details, including readiness gate and terminal-resolution across GPU patch, timed-out deleted/retained, and terminal failure outcomes. * Enhanced retry/cleanup guidance when sandbox deletion succeeds or requires manual intervention. * **Tests** * Strengthened validations to assert the exact, ordered “Sandbox lifecycle receipt” lines for multiple terminal scenarios and failurePhase variations.  Signed-off-by: Ho Lim <subhoya@gmail.com> Co-authored-by: Carlos Villela <cvillela@nvidia.com>

## Summary Release-prep documentation for v0.0.81 now summarizes user-facing changes merged since v0.0.80. It also closes the Hermes dashboard-profile backup gap and distinguishes direct blueprint-runner actions from public host CLI commands. ## Changes - Add the `v0.0.81` section to `docs/about/release-notes.mdx` with links to the detailed user guides. - Document that Hermes rebuilds preserve `.hermes/dashboard-home/`, including Dashboard `MEMORY.md` and `USER.md`. - Update Hermes manual backup and restore examples to transfer those two profile files without copying generated configuration or the secret-bearing dashboard `.env`. - Explain the new per-item backup failure causes. - Clarify that migration snapshot retention fragments are direct-runner arguments and are not exposed by the host `nemoclaw` CLI. ### Source summary - NVIDIA#6445 -> `docs/about/release-notes.mdx`, `docs/manage-sandboxes/backup-restore.mdx`, and `docs/manage-sandboxes/workspace-files.mdx`: Summarize manifest-owned key-level restore and current-config authority. - NVIDIA#6617 -> `docs/about/release-notes.mdx` and `docs/manage-sandboxes/backup-restore.mdx`: Record the fail-closed `/proc` fallback used to verify an idle Deep Agents runtime before snapshot creation. - NVIDIA#6685 -> `docs/about/release-notes.mdx`, `docs/manage-sandboxes/backup-restore.mdx`, and `docs/manage-sandboxes/workspace-files.mdx`: Document Hermes Web Dashboard profile persistence and safe manual transfer. - NVIDIA#6649 -> `docs/about/release-notes.mdx`: Summarize host-validated loopback compatible-endpoint routing through the sandbox gateway. - NVIDIA#6643 -> `docs/about/release-notes.mdx`: Summarize automatic `max_completion_tokens` handling for GPT-5 and o-series models. - NVIDIA#6661 -> `docs/about/release-notes.mdx`: Summarize bounded connection reuse for eligible provider-validation probes. - NVIDIA#6704 -> `docs/about/release-notes.mdx`: Record that direct blueprint apply stops instead of persisting incomplete state after provider or inference setup fails. - NVIDIA#6677 -> `docs/about/release-notes.mdx`: Summarize transactional recovery for legacy Docker containers whose managed supervisor disappeared after restart. - NVIDIA#6625 -> `docs/about/release-notes.mdx`: Record Hermes managed-startup persistence across direct Docker restarts. - NVIDIA#6597 -> `docs/about/release-notes.mdx`: Record final-sandbox gateway cleanup on macOS. - NVIDIA#6680 -> `docs/about/release-notes.mdx`: Summarize managed Deep Agents first-run and process-tree cleanup improvements. - NVIDIA#6647 -> `docs/about/release-notes.mdx`: Record fail-closed validation for the managed Deep Agents fetch CA bundle. - NVIDIA#6645 -> `docs/about/release-notes.mdx`: Summarize WhatsApp loopback pairing and trusted npm plugin provenance. - NVIDIA#6673 -> `docs/about/release-notes.mdx` and `docs/manage-sandboxes/backup-restore.mdx`: Document stopped-sandbox backup remediation. - NVIDIA#6631 -> `docs/about/release-notes.mdx` and `docs/manage-sandboxes/backup-restore.mdx`: Document per-item backup failure causes. - NVIDIA#6620 -> `docs/about/release-notes.mdx`: Record the created-but-not-ready sandbox lifecycle receipt. - NVIDIA#6664 -> `docs/about/release-notes.mdx`: Record prompt-aware onboarding progress output. - NVIDIA#6598 -> `docs/about/release-notes.mdx`: Summarize stale replay-result invalidation during resumed onboarding. - NVIDIA#6593 -> `docs/about/release-notes.mdx`: Summarize contextual OpenClaw audit findings for managed dashboard compatibility settings. - NVIDIA#6650 -> `docs/about/release-notes.mdx`: Record redaction of token-shaped URL query values. - NVIDIA#6638 -> `docs/about/release-notes.mdx`: Record the exact-path MCP `DELETE` policy recipe for session termination. - NVIDIA#5453 -> `docs/reference/host-files-and-state.mdx`: Clarify that snapshot retention actions belong to direct runner integrations and are not standalone host CLI commands. ### Skipped from docs-skip - NVIDIA#6633 matched the `openclaw-sandbox-permissive.yaml` path in `docs/.docs-skip` and produced no documentation in this update. ## Type of Change - [ ] Code change (feature, bug fix, or refactor) - [ ] Code change with doc updates - [ ] Doc only (prose changes, no code sample modifications) - [x] Doc only (includes code sample changes) ## Quality Gates - [ ] Tests added or updated for changed behavior - [ ] Existing tests cover changed behavior — justification: - [x] Tests not applicable — justification: This is a documentation-only release-prep update; behavior is protected by the merged source PRs, and the documentation build validates the changed examples and routes. - [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: ## Verification - [x] PR description includes the DCO sign-off declaration 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 — tests are not applicable for this documentation-only change; `npm run docs` completed successfully. - [ ] Applicable broad gate passed — `npm test` for broad runtime/test-harness changes; `npm run check` for repo-wide validation/coverage changes — command/result: not run for this documentation-only change. - [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) — 0 errors; two existing Fern warnings remain. - [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) — no new pages. --- Signed-off-by: Carlos Villela <cvillela@nvidia.com>  ## Summary by CodeRabbit - **Documentation** - Added release notes for v0.0.81 covering state preservation, inference setup, sandbox recovery, session setup, pairing, diagnostics, and security policy updates. - Expanded backup and restore guidance to include dashboard profile files and clarify files that must not be copied. - Added dashboard profile persistence details to workspace and rebuild documentation. - Clarified snapshot retention guidance and the distinction between host CLI capabilities and direct runner actions. - Added more detailed backup failure reporting information.  Signed-off-by: Carlos Villela <cvillela@nvidia.com>

Copilot AI review requested due to automatic review settings July 10, 2026 00:36

Copilot AI reviewed Jul 10, 2026

coderabbitai Bot reviewed Jul 10, 2026

View reviewed changes

Comment thread src/lib/onboard/created-sandbox-failure.test.ts Outdated

Comment thread src/lib/onboard/created-sandbox-failure.ts

HOYALIM force-pushed the codex/issue-3344-created-readiness-receipt branch from a69567b to 78642ca Compare July 10, 2026 00:42

coderabbitai Bot reviewed Jul 10, 2026

View reviewed changes

Comment thread src/lib/onboard/created-sandbox-failure.test.ts

fix(onboard): print created sandbox readiness receipt

d098cdc

Signed-off-by: Ho Lim <subhoya@gmail.com>

HOYALIM force-pushed the codex/issue-3344-created-readiness-receipt branch from 78642ca to d098cdc Compare July 10, 2026 00:47

github-actions Bot mentioned this pull request Jul 10, 2026

feat(state): add key-level restore ownership to agent manifests #6445

Merged

21 tasks

prekshivyas self-assigned this Jul 11, 2026

cv added the v0.0.81 Release target label Jul 11, 2026

cv approved these changes Jul 11, 2026

View reviewed changes

cv added 5 commits July 11, 2026 09:21

Merge branch 'main' into codex/issue-3344-created-readiness-receipt

3163939

Merge branch 'main' into codex/issue-3344-created-readiness-receipt

8347c7b

Merge branch 'main' into codex/issue-3344-created-readiness-receipt

a1914bc

Merge branch 'main' into codex/issue-3344-created-readiness-receipt

278da31

Merge branch 'main' into codex/issue-3344-created-readiness-receipt

e5a17af

cv merged commit da66f05 into NVIDIA:main Jul 11, 2026
37 checks passed

cv mentioned this pull request Jul 12, 2026

docs(release): add v0.0.81 release notes #6712

Merged

21 tasks

Uh oh!

Conversation

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

Uh oh!

Summary

Validation

DCO verification

Summary by CodeRabbit

Uh oh!

copy-pr-bot Bot commented Jul 10, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

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

Uh oh!

Walkthrough

Changes

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

HOYALIM commented Jul 10, 2026

Uh oh!

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

Uh oh!

Uh oh!

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

Uh oh!

E2E Advisor Recommendation

E2E Recommendation Advisor

Required E2E

Optional E2E

New E2E recommendations

Dispatch hint

Uh oh!

prekshivyas commented Jul 11, 2026

E2E Target Recommendation

E2E Target Advisor

Required E2E targets

Optional E2E targets

Relevant changed files

Uh oh!

cv left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

HOYALIM commented Jul 10, 2026 •

edited by coderabbitai Bot

Loading

coderabbitai Bot commented Jul 10, 2026 •

edited

Loading

coderabbitai Bot commented Jul 10, 2026 •

edited

Loading

prekshivyas commented Jul 11, 2026 •

edited by github-actions Bot

Loading