fix(connect): exit zero when probe succeeds without platform evidence by Dongni-Yang · Pull Request #9282 · NVIDIA/NemoClaw

Dongni-Yang · 2026-08-17T05:43:54Z

Summary

On macOS, nemoclaw <name> connect --probe-only completed the gateway probe and any dashboard-forward recovery, then exited 1 because the launch-readiness evidence store requires a Linux per-user runtime authority (/run/user/<uid>). The permanent platform gap turned every successful probe into a failure, so a scripted health check could not tell a healthy sandbox from a real outage. After this change, a successful probe and recovery on such a platform prints a note that evidence is unavailable and exits 0.

Related Issue

Closes #9278

Changes

src/lib/actions/sandbox/connect.ts: when publication reports evidence-failed and the readiness decision carries authorityUnsupported (thrown only for non-Linux platforms in src/lib/state/launch-readiness-lease.ts), print Note: launch-readiness evidence is unavailable on this platform; the next launch runs the complete preflight. and return with exit 0. A publication failure on a platform that supports evidence keeps Probe failed: ... and exit 1. Fence failures, validation failures, and unsafe-epoch exits are unchanged.
src/lib/actions/sandbox/connect-flow.test.ts: the macOS-shaped case now asserts recovery completes, the note prints, and the command resolves with no exit call. The sibling cases for Linux publication failure and validation failure still assert exit 1.
test/cli/connect-recovery.test.ts, test/cli/connect-terminal-agent.test.ts, test/sandbox-connect-inference/auto-pair-approval.test.ts: probe-only now expects exit 0 on every platform; the note substring still appears only on darwin.
docs/reference/commands.mdx, docs/manage-sandboxes/recover-rebuild-sandboxes.mdx: state the new macOS behavior and scope the nonzero publication-failure exits to Linux.

Design record

PR #8951 (#8942 launch-readiness leases) recorded the previous contract: macOS probe-only "completes recovery and probes, then returns nonzero because authoritative evidence is unavailable." This PR narrows that decision for the permanent platform gap only, per the QA expectation in #9278: the probe's product operation succeeded, launch runs the complete preflight without evidence on these platforms, and no consumer relies on the macOS nonzero exit. Verified consumers: internal probe-only callers (start.ts, hermes-cron-restore-recovery.ts) pass requireLaunchReadinessPublication: false and return before the changed branch; the E2E lease producer (test/e2e/live/launch-agent-turn.ts) requires exit 0; managed-cloud checks treat probe-only nonzero as failure. Linux infrastructure-producer strictness is untouched: a broken /run/user/<uid> classifies as missing, not unsupported, and still exits nonzero.

Type of Change

Code change with doc updates

Quality Gates

Tests added or updated for changed behavior
Docs updated for user-facing behavior changes
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: requested through this PR's maintainer review (sandbox connect path)

Documentation Writer Review

Documentation writer subagent reviewed the completed changes
Result: docs-updated
Evidence: docs/reference/commands.mdx, docs/manage-sandboxes/recover-rebuild-sandboxes.mdx; review verified the changed sentences against src/lib/actions/sandbox/connect.ts and the controlled-word list, and its one accuracy suggestion (scoping commands.mdx:1277 to Linux) is applied in this commit
Agent: Claude Code

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 validate:pr passed after refreshing origin/main when hooks were skipped or unavailable
Targeted behavior tests pass for the current change set, or tests are marked not applicable above — command/result: npx vitest run src/lib/actions/sandbox/connect-flow.test.ts 35/35 passed; npx vitest run test/cli/connect-recovery.test.ts test/cli/connect-terminal-agent.test.ts 6/6 passed; npx vitest run test/sandbox-connect-inference/auto-pair-approval.test.ts 9/9 passed; npm run typecheck:cli clean
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) — exits 0; the 2 remaining warnings (fern auth, theme contrast) exist on main before this change

Platform coverage

The Linux CI lanes exercise the unchanged strict behavior. The changed branch is platform-independent (it keys on the authorityUnsupported readiness-decision field, not on process.platform), and the unit test in src/lib/actions/sandbox/connect-flow.test.ts drives that exact decision shape end to end: recovery completes, the note prints, and no exit call is made. The three CLI-level tests assert exit 0 with the note on darwin and exit 0 without the note elsewhere.

Signed-off-by: Dongni Yang dongniy@nvidia.com

Summary by CodeRabbit

Bug Fixes
- macOS connect --probe-only now completes recovery successfully when launch-readiness evidence is unavailable.
- Probe-only checks consistently return exit code 0 when core checks pass.
- macOS evidence limitations are clearly reported as informational notes rather than failures.
- Linux readiness and publication failures continue to return nonzero results with appropriate diagnostics.
Documentation
- Clarified platform-specific probe-only behavior and subsequent launch checks.

`connect --probe-only` completed the gateway probe and any dashboard- forward recovery, then exited 1 on macOS because the launch-readiness evidence store requires a Linux per-user runtime authority. The permanent platform gap converted every successful probe into a failure, so a scripted health check could not distinguish a healthy sandbox from a real outage. After a successful probe and recovery, print a note that evidence is unavailable on this platform and exit 0. A publication failure on a platform that supports evidence still exits 1. Fence failures, validation failures, and unsafe epochs are unchanged. Closes #9278 Signed-off-by: Dongni Yang <dongniy@nvidia.com>

coderabbitai · 2026-08-17T05:44:28Z

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: f6c02b8b-9b72-416f-be0a-0c0d3a05b3e1

📥 Commits

Reviewing files that changed from the base of the PR and between 9d94ca3 and 8b5f742.

📒 Files selected for processing (7)

docs/manage-sandboxes/recover-rebuild-sandboxes.mdx
docs/reference/commands.mdx
src/lib/actions/sandbox/connect-flow.test.ts
src/lib/actions/sandbox/connect.ts
test/cli/connect-recovery.test.ts
test/cli/connect-terminal-agent.test.ts
test/sandbox-connect-inference/auto-pair-approval.test.ts

Included review availability: Your plan includes up to 12 reviews per rolling hour; 11 remain after this review.

📝 Walkthrough

Walkthrough

connect --probe-only now exits successfully on macOS after recovery when launch-readiness evidence is unavailable. Linux publication failures retain non-zero outcomes and redacted diagnostics. Unit, CLI, and documentation updates reflect the platform-specific behavior.

Changes

Sandbox probe outcome

Layer / File(s)	Summary
Probe outcome handling `src/lib/actions/sandbox/connect.ts`, `src/lib/actions/sandbox/connect-flow.test.ts`	The connect flow treats unsupported macOS launch-readiness authority as informational. Tests verify successful recovery, the platform note, and no probe failure.
Probe validation and documentation `test/cli/connect-recovery.test.ts`, `test/cli/connect-terminal-agent.test.ts`, `test/sandbox-connect-inference/auto-pair-approval.test.ts`, `docs/manage-sandboxes/recover-rebuild-sandboxes.mdx`, `docs/reference/commands.mdx`	CLI tests expect exit code `0` on macOS. Documentation describes successful macOS completion and non-zero Linux publication failures.

Estimated code review effort: 2 (Simple) | ~10 minutes

Merge Risk: ⚪ Minimal · up to 8b5f7

The PR narrows probe-only failures on platforms without launch-readiness evidence so successful probes exit 0 while genuine Linux publication, validation, fence, and unsafe-epoch failures remain nonzero; no actionable merge-blocking risk remains after normal checks and review.

Suggested reviewers: apurvvkumaria, cv

🚥 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 describes the main change: successful probe-only connections now exit zero when platform evidence is unavailable.
Linked Issues check	✅ Passed	The changes satisfy issue `#9278` by returning zero after successful probe and recovery while preserving failures for actual errors.
Out of Scope Changes check	✅ Passed	The code, tests, and documentation changes directly support the platform-specific probe-only exit behavior and remain in scope.

✨ Finishing Touches 💡 1

📝 Generate docstrings 💡

Create stacked PR
Commit on current branch

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch fix/9278-probe-only-platform-evidence

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

github-code-quality · 2026-08-17T05:44:36Z

Code Coverage Overview

Languages: TypeScript

TypeScript / code-coverage/plugin

The overall coverage in commit 8b5f742 in the fix/9278-probe-only-... branch remains at 96%, unchanged from commit 97761a4 in the main branch.

TypeScript / code-coverage/cli

The overall coverage in commit 8b5f742 in the fix/9278-probe-only-... branch remains at 83%, unchanged from commit c594c33 in the main branch.

Show a code coverage summary of the most impacted files.

File	`main` c594c33	`fix/9278-probe-only-...` 8b5f742	+/-
`src/lib/actions...dbox/connect.ts`	79%	79%	0%
`src/lib/inference/config.ts`	98%	98%	0%
`src/lib/onboard...ider-profile.ts`	100%	100%	0%
`src/lib/onboard...orward-start.ts`	99%	99%	0%
`src/lib/onboard...command-flag.ts`	100%	100%	0%
`src/lib/sandbox...rce-identity.ts`	86%	86%	0%
`src/lib/actions...ld-mcp-phase.ts`	87%	98%	+11%

_{Updated August 17, 2026 05:56 UTC}

github-actions · 2026-08-17T05:44:58Z

🌿 Preview your docs: https://nvidia-preview-pr-9282.docs.buildwithfern.com/nemoclaw

github-actions · 2026-08-17T05:49:09Z

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 · medium confidence · 0 blockers · 0 warnings · 0 suggestions
Nemotron 3 Ultra (second opinion): Failed

Second-opinion terminology and E2E selections are advisory. Live E2E does not run automatically for pull requests.

2 semantic terminology decisions

Terminology decisions are advisory. They affect the assessment only when a separate finding identifies concrete semantic impact.

established — launch-readiness evidence at src/lib/actions/sandbox/connect.ts:1342: Retain the established term.
established — complete preflight at src/lib/actions/sandbox/connect.ts:1342: Retain the established term.

E2E guidance

Advisory only. A maintainer can dispatch the default E2E suite for the commit under review.

Recommended E2E: None

Manual-only E2E: onboard-repair, onboard-resume
The manual PR workflow does not run these selectors for the commit under review. Run them from reviewed code on main.

Workflow run details

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

prekshivyas

Reviewed exact head 8b5f742fea499015ca2e8461b93a7eb2350fb852 against #9278, the complete diff, current review threads, and the sensitive-path security rubric.

Code verdict: no blocking diff finding. The success conversion is limited to a fallback decision whose authorityUnsupported bit is produced by the OS runtime-authority boundary; Linux fence/publication, validation, changed-epoch, and unsafe-state failures still exit nonzero. The complete probe and recovery runs before the informational return. Focused validation passed locally: 4 files, 50/50 tests.

Security categories

PASS — no secrets or credential flow changed.
PASS — no new external input reaches execution or policy decisions.
PASS — no authentication or authorization boundary changed.
PASS — no dependencies or downloaded artifacts changed.
PASS — only the proven unsupported-platform publication gap becomes informational; real validation/publication failures remain propagated.
PASS — no cryptography or protected-data handling changed.
PASS — Linux authority and restrictive launch-readiness defaults are preserved.
PASS — unit and CLI coverage exercise macOS success and preserve Linux/non-platform failure behavior.
PASS — mutation locks, epoch revalidation, complete preflight, and recovery ordering are unchanged.

I am not approving this head while the required checks gate is red. The failing job is the CLI credential-filter coverage ratchet (credential-filter.ts below its 80/80/65 per-file floor), outside this PR diff; update/re-run against the coverage fix before approval. CodeRabbit and the PR Review Advisor report no actionable diff findings.

… created (#9285) ## Summary On Ubuntu 24.04, `nemoclaw <name> connect --probe-only` exits 1 with *"no prior launch-readiness evidence can be accepted, but new launch-readiness authority could not be created"* **before running any preflight or recovery**, whenever the launch-readiness authority and receipt are both securely absent and new authority creation fails (e.g. no per-user OS runtime authority in the current session). That early exit contradicts the shipped contract in two places: - **Docs** (`docs/reference/commands.mdx`): "A securely absent runtime authority and receipt let ordinary `launch` run the complete preflight without optimization if new authority creation fails, but `connect --probe-only` still exits nonzero **because it could not publish launch-readiness evidence**" — i.e. the preflight runs and only the publication fails. - **`launchSandbox`** (`src/lib/actions/sandbox/launch.ts`): refuses only on `decision.recoveryBlocked` and runs the complete preflight for this same decision. ## Change - `connectSandbox` probe-only guard now exits early only when `recoveryBlocked` is set (a prior epoch might exist and could not be durably rotated). The securely-absent case (`fenceFailed` with `recoveryBlocked === false`) proceeds into the launch-readiness mutation gate. - Safety is preserved: the gate independently re-verifies via `checkLaunchReadinessMutationAuthority(null)` that **both stores are still missing** before admitting the null-epoch recovery; any other state returns `changed`/`unsafe` and recovery does not run. - After recovery, publication reports honestly: "Probe failed: complete probe and recovery succeeded, but final launch-readiness evidence could not be verified or published." (exit 1, per the documented Linux contract). Lifecycle callers with `requireLaunchReadinessPublication: false` now continue after recovery instead of failing before it. - Rewrote the test that pinned the early exit (`connect-flow.test.ts`) to assert recovery runs, publication is attempted, and the misleading message is gone. ## Why Refs, not Closes The issue's Expected Result asks for exit 0. The documented contract deliberately keeps `connect --probe-only` nonzero on Linux when evidence cannot be published, because a missing per-user runtime authority is a deployment signal infrastructure must repair. This PR fixes the defective part — recovery not running and the misleading refusal — and keeps the documented exit code. If maintainers want exit 0 for the securely-absent case (mirroring #9282's treatment of platform-unsupported evidence), that is a small follow-up on top of this change. With this fix, the reproduction now prints "Probe complete: … restored dashboard port forward." followed by the honest publication failure, instead of refusing to recover at all. Refs #9280 ## Testing - `npx vitest run src/lib/actions/sandbox/connect-flow.test.ts` (35 passed) - `npx vitest run test/cli/connect-recovery.test.ts` (5 passed) - sibling probe/readiness suites (93 passed), `npm run typecheck:cli`, `oxlint`, `npm run format:check` all clean Signed-off-by: Dongni Yang <dongniy@nvidia.com> 🤖 Generated with [Claude Code](https://claude.com/claude-code)  ## Summary by CodeRabbit * **Bug Fixes** * Improved probe-only sandbox connection recovery when launch-readiness checks encounter fencing issues. * Recovery and sandbox setup now proceed in eligible cases, with failures reported as unavailable or unverifiable evidence. * Removed misleading authority-creation failure reporting.  Signed-off-by: Dongni Yang <dongniy@nvidia.com>

## Summary Add the canonical dated changelog entry required before planning the v0.0.110 release. The entry summarizes user-facing changes merged since v0.0.109 and links each change to its published documentation route and source PR. ## Changes - Add `docs/changelog/2026-08-17.mdx` with the exact `## v0.0.110` release heading. - Cover managed local inference, endpoint validation, onboarding and recovery, explicit experimental Portable OpenClaw, messaging and policy cleanup, backup and security hardening, and release qualification. - Preserve the documentation skip list and the current supported-agent matrix; test-only refactors, dormant activation work, and Pi-only changes are intentionally excluded. ### Source-to-doc mapping - #8711 -> `docs/changelog/2026-08-17.mdx`: Add the Muse Glimmer llama.cpp profile. - #9099 -> `docs/changelog/2026-08-17.mdx`: Update the Muse Glimmer vLLM runtime. - #9319 -> `docs/changelog/2026-08-17.mdx`: Select the provider required by an explicit serving profile. - #9311 -> `docs/changelog/2026-08-17.mdx`: Report probe-image pull failures separately. - #9345 -> `docs/changelog/2026-08-17.mdx`: Reuse mirrored Windows Ollama. - #9284 -> `docs/changelog/2026-08-17.mdx`: Complete the required Ollama upgrade. - #9320 -> `docs/changelog/2026-08-17.mdx`: Reject unsafe custom endpoint URLs before mutation. - #9119 -> `docs/changelog/2026-08-17.mdx`: Reject unsupported custom endpoint URL components. - #9236 -> `docs/changelog/2026-08-17.mdx`: Require native Anthropic tool-use evidence. - #9347 -> `docs/changelog/2026-08-17.mdx`: Distinguish Gemini runtime 404 diagnostics. - #9307 -> `docs/changelog/2026-08-17.mdx`: Preserve the recorded API family when only the model drifts. - #9233 -> `docs/changelog/2026-08-17.mdx`: Fail incomplete Hermes route synchronization. - #9185 -> `docs/changelog/2026-08-17.mdx`: Serialize Model Router lifecycle work across gateways. - #9112 -> `docs/changelog/2026-08-17.mdx`: Stop Model Router after the last routed sandbox is destroyed. - #9229 -> `docs/changelog/2026-08-17.mdx`: Verify fresh sandbox execution readiness. - #9299 -> `docs/changelog/2026-08-17.mdx`: Verify a separate agent API host forward before reporting ready. - #9318 -> `docs/changelog/2026-08-17.mdx`: Honor explicit sandbox recreation. - #9325 -> `docs/changelog/2026-08-17.mdx`: Measure readiness reuse windows from collection completion. - #9352 -> `docs/changelog/2026-08-17.mdx`: Guide users away from the deprecated global start command. - #9370 -> `docs/changelog/2026-08-17.mdx`: Persist managed OpenClaw agent identity. - #9366 -> `docs/changelog/2026-08-17.mdx`: Pass messaging dependencies during reused onboarding. - #9321 -> `docs/changelog/2026-08-17.mdx`: Detect proxied connect sessions. - #9285 -> `docs/changelog/2026-08-17.mdx`: Run probe-only recovery when absent authority cannot be created. - #9282 -> `docs/changelog/2026-08-17.mdx`: Complete probe-only recovery without platform evidence. - #8920 -> `docs/changelog/2026-08-17.mdx`: Preserve legacy gateway identity. - #9198 -> `docs/changelog/2026-08-17.mdx`: Report sandbox config-read failures. - #9201 -> `docs/changelog/2026-08-17.mdx`: Remove only the exact Docker orphan on destroy. - #9176 -> `docs/changelog/2026-08-17.mdx`: Use rootless Podman for Portable lifecycle operations. - #9197 -> `docs/changelog/2026-08-17.mdx`: Preflight Portable CPU delegation. - #9289 -> `docs/changelog/2026-08-17.mdx`: Narrow Portable policy defaults. - #9270 -> `docs/changelog/2026-08-17.mdx`: Preserve Portable model intent. - #9339 -> `docs/changelog/2026-08-17.mdx`: Reconcile timed-out Portable stop state. - #9209 -> `docs/changelog/2026-08-17.mdx`: Clean receipt-owned Portable Podman resources. - #9186 -> `docs/changelog/2026-08-17.mdx`: Separate Podman activation readiness. - #9376 -> `docs/changelog/2026-08-17.mdx`: Settle Portable OpenClaw pairing before readiness. - #9296 -> `docs/changelog/2026-08-17.mdx`: Retire messaging channel presets the host no longer configures. - #9327 -> `docs/changelog/2026-08-17.mdx`: Drop retired channels from reused messaging selections. - #9306 -> `docs/changelog/2026-08-17.mdx`: Remove gateway-enforced presets without a local record. - #9248 -> `docs/changelog/2026-08-17.mdx`: Activate Google Chat pairing approval. - #9374 -> `docs/changelog/2026-08-17.mdx`: Accept schema-owned messaging plan fields. - #9317 -> `docs/changelog/2026-08-17.mdx`: Accept safe hard-linked package files during backup. - #9288 -> `docs/changelog/2026-08-17.mdx`: Remove managed CLI shims with destroyed user data. - #9239 -> `docs/changelog/2026-08-17.mdx`: Read voice credentials from fixed descriptors. - #9269 -> `docs/changelog/2026-08-17.mdx`: Accept bounded native OpenClaw device modes. - #9371 -> `docs/changelog/2026-08-17.mdx`: Isolate OpenClaw startup-guard output. - #9351 -> `docs/changelog/2026-08-17.mdx`: Restore staging Launchable validation. - #9350 -> `docs/changelog/2026-08-17.mdx`: Retry transient collaborator-permission reads. - #9353 -> `docs/changelog/2026-08-17.mdx`: Retry transient exact-artifact downloads. - #9226 -> `docs/changelog/2026-08-17.mdx`: Add bounded Brev readiness diagnostics. - #9237 -> `docs/changelog/2026-08-17.mdx`: Report same-commit E2E reliability. - #9232 -> `docs/changelog/2026-08-17.mdx`: Execute native-runtime qualification. - #9275 -> `docs/changelog/2026-08-17.mdx`: Define E2E selection and retry guidance. - #9234 -> `docs/changelog/2026-08-17.mdx`: Move documentation review after merge. - #9365 -> `docs/changelog/2026-08-17.mdx`: Mount documentation reviewer inputs before startup. ## 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 the dated release-entry contract. - [ ] Tests 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: ## DGX Station Hardware Evidence - [ ] Tested on DGX Station - Tested commit: Not applicable; documentation-only change. - Station profile/scenario: Not applicable. - Result: Not applicable. - Supporting evidence: Not applicable. ## 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 validate:pr` passed after refreshing `origin/main` 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` (7 passed) - [x] 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 one prose-only changelog page; `npm run docs` passed the repository's strict documentation gate. - [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) — passed with 0 errors and the 2 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) — the SPDX header is present; dated changelog pages intentionally do not use frontmatter. --- Signed-off-by: Charan Jagwani <cjagwani@nvidia.com>  ## Summary by CodeRabbit * **Documentation** * Added release notes for v0.0.110. * Documented experimental managed llama.cpp and Portable OpenClaw profiles. * Covered inference validation, onboarding and recovery improvements, rootless lifecycle handling, messaging and policy updates, backups, credential handling, filesystem protections, and release qualification updates.

prekshivyas self-assigned this Aug 17, 2026

prekshivyas reviewed Aug 17, 2026

View reviewed changes

Dongni-Yang mentioned this pull request Aug 17, 2026

fix(connect): run probe-only recovery when absent authority cannot be created #9285

Merged

prekshivyas approved these changes Aug 17, 2026

View reviewed changes

prekshivyas merged commit 692d1fa into main Aug 17, 2026
71 of 74 checks passed

prekshivyas deleted the fix/9278-probe-only-platform-evidence branch August 17, 2026 06:19

github-actions Bot added the v0.0.110 label Aug 17, 2026

Dongni-Yang mentioned this pull request Aug 17, 2026

[Ubuntu 24.04][CLI&UX] connect --probe-only exits 1 after restoring dashboard forward because launch-readiness authority cannot be recreated #9280

Open

cjagwani mentioned this pull request Aug 18, 2026

docs(changelog): add v0.0.110 release entry #9380

Merged

20 tasks

coderabbitai Bot mentioned this pull request Aug 18, 2026

fix(recovery): close post-merge failure gaps #9449

Merged

20 tasks

Navigation Menu

Uh oh!

fix(connect): exit zero when probe succeeds without platform evidence - #9282

fix(connect): exit zero when probe succeeds without platform evidence#9282
prekshivyas merged 1 commit into
mainfrom
fix/9278-probe-only-platform-evidence

Dongni-Yang commented Aug 17, 2026 •

edited

Loading

Uh oh!

coderabbitai Bot commented Aug 17, 2026 •

edited

Loading

Walkthrough

Changes

❌ Failed checks (1 warning)

Uh oh!

github-code-quality Bot commented Aug 17, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Aug 17, 2026

Uh oh!

github-actions Bot commented Aug 17, 2026 •

edited

Loading

Uh oh!

prekshivyas left a comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

Dongni-Yang commented Aug 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Related Issue

Changes

Design record

Type of Change

Quality Gates

Documentation Writer Review

Verification

Platform coverage

Summary by CodeRabbit

Uh oh!

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

Uh oh!

Walkthrough

Changes

❌ Failed checks (1 warning)

Uh oh!

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

Uh oh!

Code Coverage Overview

TypeScript / code-coverage/plugin

TypeScript / code-coverage/cli

Uh oh!

github-actions Bot commented Aug 17, 2026

Uh oh!

github-actions Bot commented Aug 17, 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!

prekshivyas left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Dongni-Yang commented Aug 17, 2026 •

edited

Loading

coderabbitai Bot commented Aug 17, 2026 •

edited

Loading

github-code-quality Bot commented Aug 17, 2026 •

edited

Loading

github-actions Bot commented Aug 17, 2026 •

edited

Loading