docs: prepare v0.0.117 documentation - #10599
Merged
Merged
Conversation
Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
sandl99
marked this pull request as ready for review
August 31, 2026 03:45
Contributor
Author
|
🌿 Preview your docs: https://nvidia-preview-pr-10599.docs.buildwithfern.com/nemoclaw |
Contributor
Author
|
PR Review Advisor finished for commit |
sandl99
enabled auto-merge (squash)
August 31, 2026 04:53
sandl99
approved these changes
Aug 31, 2026
prekshivyas
added a commit
that referenced
this pull request
Aug 31, 2026
<!-- markdownlint-disable MD041 --> ## Outcome Rebuild now treats every present failed nested-onboarding status as a recreation failure. Numeric and integer-string exit codes enter the existing recovery path. A malformed present value fails closed as exit 1. Rebuild does not run `onCreated`, restore state, or print the final success message after that failure. It restores the caller process exit status in `finally`. ## Related issue Part of #10394. This PR fixes only the contradictory success/result gap. It does not close the issue. ## Scope closeout | #10394 behavior | Status in this PR | Evidence or decision boundary | | --- | --- | --- | | Nested onboarding records failure, but rebuild prints success | Fixed | Number, integer-string, direct deferred exit, normal return, and malformed-present cases enter recovery. No creation callback, restore, or success output follows the failure. | | An expired credential is not detected before destructive rebuild | Open | Maintainers must select an authoritative OpenShell validity query and accept hard-abort, warning, or force behavior. | | Connect cannot repair the route after credential repair | Open | The connect repair subsystem still needs an owner, state-transition contract, and acceptance plan. | ## Prerequisite work - #10617 fixed Advisor base/head ref propagation and merged as `1f90124`. - #10515 removed obsolete receipt-bound policy authority from the legacy rebuild fixture and merged as `8708e19`. - Both changes are already in this PR's history. They do not need another PR or sequencing action. ## Changes - Add one shared process-exit normalizer. Absent status remains success. Integers and integer strings are preserved. Malformed present values become exit 1. - Apply that boundary to deferred `process.exit()` and the nested onboarding return observed by rebuild. - Reuse the typed deferred-exit path with `deferProcessExit: true` instead of replacing `process.exit` inside rebuild. - Route every normalized nonzero result through the existing recreation recovery path. - Include the normalized failure code in the operator diagnostic. - Preserve the caller exit-code slot across nested onboarding success and failure. - Keep the Shields recovery steps sequential and keep destructive-operation safety unchanged. ## Verification Commit under review: `5685990d939c18759d54cab76aafd9f5584f6a24` Dispatch-time base and workflow: `2cedcef9c2fb4d29f155690001be2e214a33f331` - Focused seven-file CLI suite: 128/128 passed. - `npm run typecheck:cli`: passed. - `npm run validate:pr`: passed. - Core CI: [run 33357921811](https://github.com/NVIDIA/NemoClaw/actions/runs/33357921811). Attempt 1 had one 5-second timeout in untouched `setup-nim-flow-serving-profile.test.ts`; the same base shard was green and the file passed locally 4/4. One failed-job rerun passed the shard, `cli-tests`, and final `checks` on attempt 2. - Managed images: [run 33357921807](https://github.com/NVIDIA/NemoClaw/actions/runs/33357921807), success on attempt 1. OpenClaw, Hermes, Deep Agents Code, Pi amd64/arm64, staging permission, activation, and MCP lanes passed. - Advisor: [run 33357920868](https://github.com/NVIDIA/NemoClaw/actions/runs/33357920868), success. All nine specialist artifacts report no actionable finding. - CodeRabbit completed a full review of the same code diff at `644056813798f04a12a88a1111728ebeb3728b40`. The latest commit only merged `main`; the [new review request](#10590 (comment)) reported no changed files. GitHub reports zero unresolved review threads. - Trusted `rebuild-openclaw`: [run 33359179320](https://github.com/NVIDIA/NemoClaw/actions/runs/33359179320), correlation `f4a4ea9e-be62-4c10-b921-1ef5d79ccc30`, success on attempt 1. The dispatch receipt binds candidate `5685990d...` and base/workflow `2cedcef9...`. - The trusted run rebuilt OpenClaw 2026.3.11 to 2026.7.1, exited 0, preserved the workspace marker and policy state, rotated the gateway token, matched the runtime token to config, and wrote a valid changed config hash. The cleanup manifest records five passed cleanup outcomes and no failures. - Earlier [run 33350310624](https://github.com/NVIDIA/NemoClaw/actions/runs/33350310624) stopped before candidate execution because its managed-image prerequisite was unavailable. It created no candidate resources. Run 33359179320 supersedes it. - The trusted target proves ordinary old-version rebuild, state preservation, and token rotation. It does not inject or prove expired credentials. - GitHub marks the latest PR commit as verified with a valid SSH signature. The commit has a DCO trailer. - A final SSH fetch found `main` at `e50c45d182087a70b556165d285bf467e491acef`. That commit changes only documentation in #10599, overlaps no PR file, and #10590 remains mergeable. The diff contains no secrets or credentials. ## Next human action A maintainer must review and approve #10590, then merge it under repository policy. Keep #10394 open for the credential-validity and connect-repair design decisions. No self-approval or merge was performed. --- Signed-off-by: Charan Jagwani <cjagwani@nvidia.com> Signed-off-by: Prekshi Vyas <prekshiv@nvidia.com> <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Bug Fixes** * Improved rebuild handling for numeric, string, null, and invalid exit codes. * Failed onboarding now prevents restoration and success reporting while preserving the original exit status. * Recovery guidance now appears only when shields were previously locked. * **Tests** * Added coverage for exit-code normalization, rebuild failures, rollback, logging, and recovery behavior. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Signed-off-by: Charan Jagwani <cjagwani@nvidia.com> Signed-off-by: Prekshi Vyas <prekshiv@nvidia.com> Co-authored-by: Prekshi Vyas <prekshiv@nvidia.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release target
This cumulative documentation update prepares
v0.0.117from changes afterv0.0.116throughmaincommit2cedcef9c2fb4d29f155690001be2e214a33f331.That
mainboundary is the second parent of the release-entry merge commit.Readers receive a canonical release entry for the policy-authority, recovery, lifecycle, messaging, and maintainer-tooling changes in this patch, plus corrected architecture terminology for supported agent runtimes.
Pages and contracts
docs/changelog/2026-08-31.mdxwith thev0.0.117release entry.docs/reference/architecture.mdxto distinguish the OpenShell sandbox platform from supported agent runtimes and to replace the retirednemoclaw deployflow.WRITING.md,docs/STYLE.md,docs/AUTOMATION.md, and the documentation contribution and independent-review contracts.Validation
Validation ran against exact commit
498415ccfac8618f7f01c39d3dd5d8c26f2defed:npm run docs— passed with 0 errors and 2 existing Fern warnings.git diff --check— passed.Independent review
The PR Review Advisor reviewed exact commit
498415ccfac8618f7f01c39d3dd5d8c26f2defedin run 33357929165.All nine specialists completed successfully, and the Documentation specialist reported that no documentation issue requires a change.
The complete feedback collection contains no formal reviews, inline comments, or unresolved review threads.
Managed state
Ready-for-review status transferred branch ownership from the post-merge documentation workflow to maintainers.
Follow Post-Merge Documentation Catch-Up for release-cutoff routing.
Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>