fix(onboard): reconstruct recovery before admission - #11168
Conversation
Signed-off-by: San Dang <sdang@nvidia.com>
|
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. |
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueComment |
|
🌿 Preview your docs: https://nvidia-preview-pr-11168.docs.buildwithfern.com/nemoclaw |
|
PR Review Advisor finished for commit |
|
Closing this follow-up because it addresses a non-critical recovery edge case outside the original Express installer blocker. The original fix was completed in #11124 and validated manually on GB300. |
Outcome
Onboarding now reconstructs missing recovery evidence before it evaluates recovery-only admission. A retained sandbox remains blocked, while an explicit different sandbox name can continue.
Reason
PR #11124 restored registry-only recovery after locking. A
recovery_requiredsession could still fail during the earlier option read because its independent recovery record did not exist yet.Related issues
Refs #11096
Follow-up to #11124
Changes
destroy --yesretry requires a durable identity fingerprint.Verification
npm run test:changed— 122 files passed; 1,925 tests passed and 1 skipped.npx vitest run --project cli src/lib/onboard/entry-options.test.ts src/lib/onboard/portable-resume-lock-boundary.test.ts— 60 tests passed.npm run typecheck:cli— passed.npm run docs— passed.npm run validate:pr— passed against canonicalmainat1c6031569639a8ac2668552da11bc9e9d1ef9cd2.Review notes
The parent fix completed a physical DGX Station GB300 Express install at
049f3c469, including CUDA proof and the final OpenShell replacement handoff. This follow-up changes only recovery admission ordering.Signed-off-by: San Dang sdang@nvidia.com