Dockerfile (1)

412-414: Run the Dockerfile E2E matrix before merge.

Given this is an image-build/runtime contract change, please run the recommended jobs to validate behavior in real container execution paths:

gh workflow run nightly-e2e.yaml --ref <branch> -f jobs=cloud-e2e,sandbox-survival-e2e,hermes-e2e,rebuild-openclaw-e2e

As per coding guidelines, “Layer ordering, permissions, and baked config changes are only testable with a real container build.”

🤖 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 `@Dockerfile` around lines 412 - 414, Run the Dockerfile E2E matrix before
merging: trigger the nightly-e2e workflow for this branch with the jobs
cloud-e2e, sandbox-survival-e2e, hermes-e2e, and rebuild-openclaw-e2e and verify
in actual container runs that the Dockerfile steps invoking "openclaw plugins
install /opt/nemoclaw", "openclaw plugins enable nemoclaw", and "openclaw
plugins inspect nemoclaw --json" complete successfully (no errors, correct exit
codes, and expected inspection output), and fix any failures (permissions,
missing files, or runtime differences) found during those real container
builds/executions.

nemoclaw/src/register.test.ts (1)

34-39: ⚡ Quick win

Make the missing-config mock path-scoped and ENOENT-shaped.

mockMissingOpenClawConfig() currently throws a generic error for every readFileSync call. That can mask unrelated file reads and doesn’t emulate a real “missing file” condition for openclaw.json.

Proposed patch

 const mockedReadFileSync = vi.mocked(readFileSync);
+const defaultReadFileSyncImpl = mockedReadFileSync.getMockImplementation();
 const mockedLoadOnboardConfig = vi.mocked(loadOnboardConfig);

 function mockMissingOpenClawConfig(): void {
   mockedReadFileSync.mockReset();
-  mockedReadFileSync.mockImplementation(() => {
-    throw new Error("openclaw config unavailable");
+  mockedReadFileSync.mockImplementation((path, options) => {
+    if (String(path).endsWith("openclaw.json")) {
+      const err = new Error("openclaw config unavailable") as NodeJS.ErrnoException;
+      err.code = "ENOENT";
+      throw err;
+    }
+    return defaultReadFileSyncImpl
+      ? defaultReadFileSyncImpl(path as never, options as never)
+      : ("" as ReturnType<typeof readFileSync>);
   });
 }

🤖 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 `@nemoclaw/src/register.test.ts` around lines 34 - 39, Change
mockMissingOpenClawConfig to only throw a file-not-found (ENOENT) error for the
openclaw.json path instead of throwing for every read; capture the real
readFileSync (e.g. originalReadFileSync) and use
mockedReadFileSync.mockImplementation((path, ...args) => { if
(String(path).includes('openclaw.json')) throw Object.assign(new Error("openclaw
config unavailable"), { code: 'ENOENT' }); return originalReadFileSync(path,
...args); }); so unrelated reads still work and code that checks error.code ===
'ENOENT' will behave correctly; keep the function name mockMissingOpenClawConfig
and mockedReadFileSync in place.

Dockerfile (1)

402-404: Verify the fix with recommended E2E tests.

The fail-fast plugin installation correctly ensures /nemoclaw command registration happens at build time. To confirm this resolves the TUI slash-command issue (#2021) and doesn't regress existing flows, run the E2E test suites recommended for Dockerfile changes.

As per coding guidelines, run the following E2E tests on this branch:

gh workflow run nightly-e2e.yaml --ref fix/openclaw-slash-command-registration -f jobs=cloud-e2e,sandbox-survival-e2e,hermes-e2e,rebuild-openclaw-e2e

Expected results:

• cloud-e2e: Onboard + cloud inference completes without plugin registration errors
• sandbox-survival-e2e: Gateway restart does not lose the /nemoclaw command
• hermes-e2e: Hermes agent onboard + inference works with the plugin enabled
• rebuild-openclaw-e2e: Workspace state survives rebuild and /nemoclaw remains registered

🤖 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 `@Dockerfile` around lines 402 - 404, The Dockerfile change ensures the
nemoclaw plugin is installed/enabled at build time using the openclaw CLI
(openclaw plugins install /opt/nemoclaw, openclaw plugins enable nemoclaw,
openclaw plugins inspect nemoclaw), so validate this by running the recommended
E2E workflows: execute the GitHub Actions command to run nightly-e2e.yaml for
jobs cloud-e2e, sandbox-survival-e2e, hermes-e2e, rebuild-openclaw-e2e (as
provided) and confirm cloud-e2e completes without plugin registration errors,
sandbox-survival-e2e preserves the /nemoclaw command across gateway restarts,
hermes-e2e allows Hermes agent onboard+inference with the plugin, and
rebuild-openclaw-e2e preserves workspace state and the /nemoclaw registration.