fix(onboard): reconcile managed bootstrap after restart

[ericksoa]

Summary

Reconcile every durable managed-bootstrap transaction before a new sandbox create begins, using the provider lifecycle boundary so restart recovery remains driver-neutral and pluggable. This slice remains inert: it does not advertise or activate buildless support.

Related Issue

Part of #7744.

Changes

• Add a driver-neutral recovery receipt contract and lifecycle hook with normalized, frozen, provider-owned results.
• Reconstruct Docker recovery authority from versioned journals for OpenClaw, Hermes, and DCode.
• Roll back staged, cutover, and rollback-authorized attempts using exact runtime and launch-spec identity.
• Resume shared-state-committed attempts through exact backup cleanup, receipt retirement, and terminal finalization.
• Persist terminal finalization before active-journal removal and compact retained journals idempotently after interruption.
• Enumerate unfinished records only together with the production recovery consumer; ignore journal, decision, and finalized crash temp sidecars while rejecting alien entries fail-closed.
• Use the canonical durable-receipt comparator during recovery compaction so reordered receipt fields remain equivalent without masking semantic changes.
• Reconcile unfinished work before sandbox create without adding Docker or Podman switches to central orchestration.
• Scope canonical schema 1/2 journals to their immutable provider, sandbox, and full runtime IDs without inventing the missing agent or trusting a possibly stale decision phase.
• Render exact recovery guidance at the public create boundary, preserve legacy authority, and document the inert pre-activation drain/retirement contract tracked by [Epic] Support native Podman with buildless managed onboarding #7744.

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: Exact-tree reconstruction review covered owner-retained rollback cleanup, durable finalization ordering, all-agent recovery, crash-sidecar handling, canonical receipt comparison, provider neutrality, and inert activation. Exact-head public advisors remain part of the qualification wave.
• Non-success, skipped, or missing CI check accepted by maintainer — check name, approval link, and follow-up issue: npm-advisory failures and their consequential same-repository E2E / PR Gate blockage are handled on a separate security stream and explicitly waived as blockers for this stack.

Documentation Writer Review

• Documentation writer subagent reviewed the completed changes
• Result: docs-updated
• Evidence: src/lib/onboard/managed-bootstrap/README.md preserves the identity-addressed/finality and driver-neutral ownership model, and adds the exact legacy journal drain contract: immutable-ID inspection, no mutable-name deletion, no inferred agent, preserved journal/sidecars, scoped unrelated-sandbox progress, and [Epic] Support native Podman with buildless managed onboarding #7744 retirement gating before activation.
• Agent: Codex Desktop

DGX Station Hardware Evidence

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

Verification

• Merged base: feat(onboard): persist managed bootstrap transactions #8041 produced main commit 03fbf5ebf1dfc09506c5fefb1debe4b8766fde57.
• Exact public head: aca6e3d1787b4b9d5952c86e290300fb48fea683; exact tree: 9b727abe92e634f006e55798f2a3fc78f02f14fa.
• Review scope from the merged base: 16 paths, +2816/-172.
• Stable patch ID: 49f44db7a412c74cc1e67ab03f41ea1bf28a5c9c.
• Binary diff SHA-256: 0fef658b79f052247f9dbb0d0ec4e9ff31eec8fedbcde1592b6d5659963cb4ba.
• The append-only history preserves the prior public graft f3d39891bab25bec0092de9a1f001fb62b1cdd6c, then adds signed+DCO review children 2d1c54276ac5bba78fc950eddb86106edef35d99, fd260f2e0fd7da6aa667f149e9c9edfd4d6283a3, 456fd86e3f45c030651a67ca0afe14be53ee4d7e, and aca6e3d1787b4b9d5952c86e290300fb48fea683; no remote history was rewritten.
• Durable refs: backup/podman-stack/pr8043-feedback-2d1c5427, backup/podman-stack/pr8043-feedback-fd260f2e, backup/podman-stack/pr8043-feedback-456fd86e, backup/podman-stack/pr8043-feedback-aca6e3d1, and hold/podman-stack/pr8045-base-aca6e3d1; all earlier source/reconstruction refs remain intact.
• The recovery cleanup passed 184 focused all-agent/provider/recovery tests, CLI build, CLI typecheck, Biome, pre-commit, pre-push, repository/source-shape/test-size checks, and diff checks. The legacy-recovery child passed 105 focused journal/recovery/provider/flow tests, CLI typecheck, Biome, pre-commit and pre-push hooks, repository/source-shape/test-size checks, and diff checks. The final evidence-hardening child passed 43 focused recovery/flow tests, CLI typecheck, Biome, signed commit hooks, and pre-push hooks.
• Review feedback now covers legacy-record fail-closed behavior, exact owner-retention authority, terminal ordering/idempotence, per-record bounded failure isolation, shared receipt retirement, canonical agent validation, shared finalization persistence, non-zero Docker removal recovery, exact legacy sandbox scoping, decision-sidecar phase uncertainty, guided public-boundary recovery, zero durable writes during legacy recovery, and secret-redacted provider detail.
• Production provider bootstrap remains unsupported; no user-visible buildless or Podman activation is added.

Stack

• Base: merged PR3.12A feat(onboard): persist managed bootstrap transactions #8041, main commit 03fbf5ebf1dfc09506c5fefb1debe4b8766fde57.
• This slice: PR3.12B fix(onboard): reconcile managed bootstrap after restart #8043, exact public head aca6e3d1787b4b9d5952c86e290300fb48fea683, targeting main.
• Next: feat(onboard): add managed bootstrap image runtime #8045 targets hold/podman-stack/pr8045-base-aca6e3d1 while its exact patch is recascaded append-only after this merge.
• Buildless and Podman support remain disabled until the complete all-agent, multiarch, GPU/local-inference, recovery, installer, and protected-E2E activation gates in [Epic] Support native Podman with buildless managed onboarding #7744 pass.

---

Signed-off-by: Aaron Erickson aerickson@nvidia.com

Summary by CodeRabbit

• New Features

  • Added automatic recovery for unfinished managed bootstrap transactions after interruption or restart.
  • Added durable rollback, cleanup, and reconciliation for partially completed Docker operations.
  • Added lifecycle recovery checks before creating new sandboxes.
  • Sandbox creation now stops for relevant recovery failures and warns about unrelated issues.
  • Added support for recovering legacy state with stronger identity validation and diagnostics.

• Bug Fixes

  • Improved recovery ordering, journal cleanup, state reconciliation, and handling of uncertain Docker operation results.
  • Added clearer, bounded recovery reports and failure guidance.

[copy-pr-bot]

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.

[ericksoa]

Exact-head CodeRabbit follow-up on fd260f2e0fd7da6aa667f149e9c9edfd4d6283a3:

• Canonical agent validation now uses MANAGED_STARTUP_AGENTS.
• A real non-zero docker rm result is modeled separately from process failure and proves the durable journal remains for retry.
• Normal and restart-recovery finalization now share one write/reconcile/re-read invariant.
• The suggested three fixture if replacements were intentionally not applied: those added test conditionals violate this repository’s growth guard. The existing switch form preserves the same injected-failure behavior while the exact head adds zero test if statements.

Focused tests, CLI typecheck, Biome, commit hooks, and push hooks pass locally; exact-head CI/advisors are now running.

[coderabbitai]

Actionable comments posted: 2

🧹 Nitpick comments (6)

src/lib/onboard/managed-bootstrap/docker-journal.test.ts (1)

520-530: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Remove the redundant try/catch or assert on a captured error.

Line 522 already asserts the throw. The try/catch at lines 525-529 repeats the call. If the parser stopped throwing, the catch body would never run, so the not.toBeInstanceOf expectation would silently pass. Capture the error once and assert both properties on it.

♻️ Proposed single-capture assertion

   it("does not classify a malformed legacy journal as upgradeable authority", () => {
     const malformed = { ...legacyJournalV2(), agent: "hermes" };
-    expect(() => parseDockerManagedBootstrapJournal(`${JSON.stringify(malformed)}\n`)).toThrow(
-      "legacy journal schema is invalid",
-    );
-    try {
-      parseDockerManagedBootstrapJournal(`${JSON.stringify(malformed)}\n`);
-    } catch (error) {
-      expect(error).not.toBeInstanceOf(DockerManagedBootstrapLegacyRecordRequiresAgentError);
-    }
+    let failure: unknown;
+    try {
+      parseDockerManagedBootstrapJournal(`${JSON.stringify(malformed)}\n`);
+    } catch (error) {
+      failure = error;
+    }
+    expect(failure).toBeInstanceOf(Error);
+    expect(failure).not.toBeInstanceOf(DockerManagedBootstrapLegacyRecordRequiresAgentError);
+    expect((failure as Error).message).toContain("legacy journal schema is invalid");
   });

🤖 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 `@src/lib/onboard/managed-bootstrap/docker-journal.test.ts` around lines 520 -
530, Update the test “does not classify a malformed legacy journal as
upgradeable authority” to invoke parseDockerManagedBootstrapJournal once,
capture the thrown error, and assert both its message and that it is not a
DockerManagedBootstrapLegacyRecordRequiresAgentError. Remove the redundant
try/catch and repeated parser call while preserving the malformed journal setup.

Source: Path instructions

src/lib/onboard/managed-bootstrap/docker.test.ts (2)

150-154: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Use expectEventBefore here too.

Lines 150-154 repeat the presence-and-index pattern that the new helper encapsulates. Replace them with one helper call for consistency inside the same test.

♻️ Proposed fix

-    expect(fake.events).toContain("journal:shared-state-committed");
-    expect(fake.events).toContain(`rm:${OLD_ID}`);
-    expect(fake.events.indexOf("journal:shared-state-committed")).toBeLessThan(
-      fake.events.indexOf(`rm:${OLD_ID}`),
-    );
+    expectEventBefore(fake.events, "journal:shared-state-committed", `rm:${OLD_ID}`);

🤖 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 `@src/lib/onboard/managed-bootstrap/docker.test.ts` around lines 150 - 154,
Replace the repeated event-presence and ordering assertions in the affected test
with a single expectEventBefore call, passing "journal:shared-state-committed"
and the OLD_ID removal event, while preserving the existing ordering
requirement.

---

27-31: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Duplicated expectEventBefore helper in two test files. Both files define the identical event-ordering helper. Both already import shared helpers from src/lib/onboard/managed-bootstrap/docker-test-fixture.ts, so the helper belongs there and should be exported once.

• src/lib/onboard/managed-bootstrap/docker.test.ts#L27-L31: delete the local definition and import expectEventBefore from ./docker-test-fixture.
• src/lib/onboard/managed-bootstrap/docker-recovery.test.ts#L40-L44: delete the local definition and import the same shared helper.

🤖 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 `@src/lib/onboard/managed-bootstrap/docker.test.ts` around lines 27 - 31, The
event-ordering helper is duplicated across both test files. In
src/lib/onboard/managed-bootstrap/docker.test.ts lines 27-31, remove the local
expectEventBefore definition and import it from ./docker-test-fixture; make the
same removal and import change in
src/lib/onboard/managed-bootstrap/docker-recovery.test.ts lines 40-44, exporting
the single shared helper from docker-test-fixture.

src/lib/onboard/managed-bootstrap/adapter.ts (1)

584-593: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Extract the ownership predicate once.

Lines 585 and 588 repeat the same condition. A future change to the ownership rule must be applied in both places. Extract one predicate and derive both the blocking list and the warning list from it.

♻️ Proposed extraction

-  const blocking = report.failures.filter(
-    (failure) => failure.sandbox === null || failure.sandbox.sandboxName === sandboxName,
-  );
-  for (const failure of report.failures) {
-    if (failure.sandbox === null || failure.sandbox.sandboxName === sandboxName) continue;
+  const ownsRequestedName = (failure: ManagedBootstrapRecoveryFailure) =>
+    failure.sandbox === null || failure.sandbox.sandboxName === sandboxName;
+  const blocking = report.failures.filter(ownsRequestedName);
+  for (const failure of report.failures) {
+    if (ownsRequestedName(failure)) continue;
     warn(
       `Managed bootstrap recovery retained unrelated sandbox '${failure.sandbox.sandboxName}' ` +
         `(${failure.bootstrapIdentity}, ${failure.code}).`,
     );
   }

🤖 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 `@src/lib/onboard/managed-bootstrap/adapter.ts` around lines 584 - 593, In the
managed bootstrap recovery logic, extract the repeated sandbox ownership
condition into a single predicate near the blocking calculation. Reuse that
predicate both when filtering blocking failures and when selecting unrelated
failures for warnings, preserving the current ownership behavior.

src/lib/onboard/managed-bootstrap/docker-test-fixture.ts (2)

548-555: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Drop the unnecessary cast on line 549.

original is declared as DockerContainerInspect | null. Assigning null needs no cast. The as unknown as DockerContainerInspect cast suppresses type checking and can hide a real type error after a future refactor.

♻️ Proposed fix

     removeOriginalExternally() {
-      original = null as unknown as DockerContainerInspect;
+      original = null;
       events.push(`external-rm:${OLD_ID}`);
     },

🤖 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 `@src/lib/onboard/managed-bootstrap/docker-test-fixture.ts` around lines 548 -
555, Remove the unnecessary `as unknown as DockerContainerInspect` cast in
`removeOriginalExternally()` and assign `null` directly to `original`,
preserving the existing event behavior.

---

312-323: 🗄️ Data Integrity & Integration | 🔵 Trivial | ⚡ Quick win

The fake store ignores the finalization context, so provider-side context wiring is untested.

recordFinalization and loadFinalization accept an optional DockerManagedBootstrapFinalizationContext in the real store, and the real store fails when the record contradicts the context. This fake drops the parameter. docker.ts passes a context from finalizationContext(handle) and from the recovered journal. A wrong context there would still pass every Docker fixture test.

Validate the supplied context in the fake so the durable contract is exercised at the boundary.

♻️ Proposed context assertion in the fake store

-    recordFinalization(value) {
+    recordFinalization(value, context) {
+      if (context) assertFinalizationContext(value, context);
       if (
         finalization &&
         serializeDockerManagedBootstrapFinalizationRecord(finalization) !==
           serializeDockerManagedBootstrapFinalizationRecord(value)
       ) {
         throw new Error("finalization changed");
       }
       finalization = structuredClone(value);
       events.push(`finalization:${value.phase}`);
     },
-    loadFinalization: () => (finalization ? structuredClone(finalization) : null),
+    loadFinalization: (_identity, context) => {
+      if (!finalization) return null;
+      if (context) assertFinalizationContext(finalization, context);
+      return structuredClone(finalization);
+    },

Add the helper next to failFixture:

function assertFinalizationContext(
  record: DockerManagedBootstrapFinalizationRecord,
  context: DockerManagedBootstrapFinalizationContext,
): void {
  if (
    record.bootstrapIdentity !== context.bootstrapIdentity ||
    record.providerId !== context.providerId ||
    record.agent !== context.agent ||
    record.sandbox.sandboxName !== context.sandbox.sandboxName ||
    record.sandbox.sandboxId !== context.sandbox.sandboxId ||
    record.sandbox.driverId !== context.sandbox.driverId ||
    record.planFingerprint !== context.planFingerprint ||
    record.profileFingerprint !== context.profileFingerprint ||
    record.imageReference !== context.imageReference
  ) {
    failFixture("finalization record does not match supplied durable context");
  }
}

🤖 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 `@src/lib/onboard/managed-bootstrap/docker-test-fixture.ts` around lines 312 -
323, Update the fake store’s recordFinalization and loadFinalization methods to
accept the optional DockerManagedBootstrapFinalizationContext and validate it
against the finalization record before storing or returning it. Add an
assertFinalizationContext helper near failFixture that compares all durable
identity, provider, agent, sandbox, plan/profile fingerprint, and
image-reference fields, calling failFixture on mismatch; preserve existing
cloning and change-detection behavior.

🤖 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/managed-bootstrap/docker-journal.ts`:
- Around line 421-428: Update normalizeDockerManagedBootstrapJournal and the
journal store.load path so schema-1 and schema-2 journals are upgraded in place
using the durable context, matching the finalization reader’s legacy-record
handling, before returning the normalized journal. Preserve the
DockerManagedBootstrapLegacyRecordRequiresAgentError path only when the legacy
journal cannot be safely upgraded, so stale journals no longer cause a
permanently blocking null sandbox.

In `@src/lib/onboard/sandbox-gpu-create-run-attempt.ts`:
- Around line 147-152: Update the public runSandboxGpuCreateFlow boundary to
catch ManagedBootstrapRecoveryBlockedError from managed lifecycle recovery, then
print its actionable recovery guidance instead of allowing the typed error to
propagate. Preserve existing recovery handling and behavior for other errors.

---

Nitpick comments:
In `@src/lib/onboard/managed-bootstrap/adapter.ts`:
- Around line 584-593: In the managed bootstrap recovery logic, extract the
repeated sandbox ownership condition into a single predicate near the blocking
calculation. Reuse that predicate both when filtering blocking failures and when
selecting unrelated failures for warnings, preserving the current ownership
behavior.

In `@src/lib/onboard/managed-bootstrap/docker-journal.test.ts`:
- Around line 520-530: Update the test “does not classify a malformed legacy
journal as upgradeable authority” to invoke parseDockerManagedBootstrapJournal
once, capture the thrown error, and assert both its message and that it is not a
DockerManagedBootstrapLegacyRecordRequiresAgentError. Remove the redundant
try/catch and repeated parser call while preserving the malformed journal setup.

In `@src/lib/onboard/managed-bootstrap/docker-test-fixture.ts`:
- Around line 548-555: Remove the unnecessary `as unknown as
DockerContainerInspect` cast in `removeOriginalExternally()` and assign `null`
directly to `original`, preserving the existing event behavior.
- Around line 312-323: Update the fake store’s recordFinalization and
loadFinalization methods to accept the optional
DockerManagedBootstrapFinalizationContext and validate it against the
finalization record before storing or returning it. Add an
assertFinalizationContext helper near failFixture that compares all durable
identity, provider, agent, sandbox, plan/profile fingerprint, and
image-reference fields, calling failFixture on mismatch; preserve existing
cloning and change-detection behavior.

In `@src/lib/onboard/managed-bootstrap/docker.test.ts`:
- Around line 150-154: Replace the repeated event-presence and ordering
assertions in the affected test with a single expectEventBefore call, passing
"journal:shared-state-committed" and the OLD_ID removal event, while preserving
the existing ordering requirement.
- Around line 27-31: The event-ordering helper is duplicated across both test
files. In src/lib/onboard/managed-bootstrap/docker.test.ts lines 27-31, remove
the local expectEventBefore definition and import it from ./docker-test-fixture;
make the same removal and import change in
src/lib/onboard/managed-bootstrap/docker-recovery.test.ts lines 40-44, exporting
the single shared helper from docker-test-fixture.

🪄 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: 1f6d6547-2611-4bae-bd91-2bac2bddef4a

📥 Commits

Reviewing files that changed from the base of the PR and between d91ee2c and fd260f2.

📒 Files selected for processing (15)

• src/lib/onboard/managed-bootstrap/README.md
• src/lib/onboard/managed-bootstrap/adapter.test.ts
• src/lib/onboard/managed-bootstrap/adapter.ts
• src/lib/onboard/managed-bootstrap/docker-journal.test.ts
• src/lib/onboard/managed-bootstrap/docker-journal.ts
• src/lib/onboard/managed-bootstrap/docker-recovery.test.ts
• src/lib/onboard/managed-bootstrap/docker-runtime.ts
• src/lib/onboard/managed-bootstrap/docker-test-fixture.ts
• src/lib/onboard/managed-bootstrap/docker.test.ts
• src/lib/onboard/managed-bootstrap/docker.ts
• src/lib/onboard/managed-bootstrap/index.ts
• src/lib/onboard/managed-bootstrap/runtime-create.ts
• src/lib/onboard/runtime-provider/runtime-provider-contract.test.ts
• src/lib/onboard/sandbox-gpu-create-flow.test.ts
• src/lib/onboard/sandbox-gpu-create-run-attempt.ts

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

• src/lib/onboard/sandbox-gpu-create-flow.test.ts
• src/lib/onboard/managed-bootstrap/index.ts
• src/lib/onboard/runtime-provider/runtime-provider-contract.test.ts
• src/lib/onboard/managed-bootstrap/README.md
• src/lib/onboard/managed-bootstrap/docker-runtime.ts
• src/lib/onboard/managed-bootstrap/docker.ts

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

src/lib/onboard/sandbox-gpu-create-flow.ts (1)

225-231: 🎯 Functional Correctness | 🔵 Trivial | ⚡ Quick win

Assert recovery-detail redaction at the public boundary.

The existing case covers ManagedBootstrapRecoveryBlockedError and proves that sandbox creation stops. Use a token-bearing recovery detail and assert that errorOutput() contains the redacted value and not the original value.

🤖 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 `@src/lib/onboard/sandbox-gpu-create-flow.ts` around lines 225 - 231, Update
the test around the sandbox creation flow’s catch handling to use a recovery
detail containing a sensitive token, then assert that errorOutput() includes the
redacted value and excludes the original token when
ManagedBootstrapRecoveryBlockedError reaches the public boundary. Preserve the
existing assertion that sandbox creation stops.

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.

Inline comments:
In `@src/lib/onboard/managed-bootstrap/docker-recovery.test.ts`:
- Around line 107-109: Update the legacy recovery test around the existing
fake.events and fake.journal assertions to verify that fake.events is empty
after recovery, ensuring no durable finalization record or other mutation is
written. Retain the fake.journal null assertion and use the existing event
fixture rather than adding new state.

---

Nitpick comments:
In `@src/lib/onboard/sandbox-gpu-create-flow.ts`:
- Around line 225-231: Update the test around the sandbox creation flow’s catch
handling to use a recovery detail containing a sensitive token, then assert that
errorOutput() includes the redacted value and excludes the original token when
ManagedBootstrapRecoveryBlockedError reaches the public boundary. Preserve the
existing assertion that sandbox creation stops.

🪄 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: 6116e2a6-1ff5-457e-8c1c-df52a3496d62

📥 Commits

Reviewing files that changed from the base of the PR and between fd260f2 and 456fd86.

📒 Files selected for processing (7)

• src/lib/onboard/managed-bootstrap/README.md
• src/lib/onboard/managed-bootstrap/docker-journal.test.ts
• src/lib/onboard/managed-bootstrap/docker-journal.ts
• src/lib/onboard/managed-bootstrap/docker-recovery.test.ts
• src/lib/onboard/managed-bootstrap/docker.ts
• src/lib/onboard/sandbox-gpu-create-flow.test.ts
• src/lib/onboard/sandbox-gpu-create-flow.ts

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

• src/lib/onboard/sandbox-gpu-create-flow.test.ts
• src/lib/onboard/managed-bootstrap/docker-journal.test.ts
• src/lib/onboard/managed-bootstrap/docker-journal.ts