🧹 fix: 🛡️ Sentinel: [code health] enforce landlock mode

[Hardonian]

🎯 What: Evaluated and enabled strict landlock enforcement mode in the openclaw-sandbox.yaml base policy.
💡 Why: Switching from best_effort to strict enforcing secures the sandbox by failing closed rather than silently ignoring landlock enforcement failures.
✅ Verification: Verified testing suite passes cleanly with npm run verify:core.
✨ Result: A more secure and predictable default sandbox environment configuration.

---

PR created automatically by Jules for task 6561170165977134394 started by @Hardonian

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[github-actions]

This repository limits contributors to 10 open pull requests. Please close or merge existing PRs before opening new ones.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4202d1f953

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Add preflight handling before enabling strict Landlock

In environments where the Docker VM or Linux host kernel lacks Landlock support (for example <5.13 or Landlock disabled), switching the base policy to compatibility: strict makes sandbox creation fail closed, but the onboarding code only checks kernel support after the sandbox has already been created and still tells users restrictions will degrade in best-effort mode (src/lib/onboard.ts). This turns a previously supported/degraded onboarding path into an opaque create-time failure unless the preflight/docs/error path are updated to make Landlock a hard prerequisite before this policy is applied.

Useful? React with 👍 / 👎.

[kilo-code-bot]

Code Review Summary

Status: 1 Issue Found | Recommendation: Address before merge

Overview

Severity	Count
CRITICAL	1
WARNING	0
SUGGESTION	0

Issue Details (click to expand)

CRITICAL

File	Line	Issue
docs/deployment/sandbox-hardening.md	114	Documentation states landlock uses compatibility: best_effort which no longer matches the updated openclaw-sandbox.yaml policy. This creates misinformation about the sandbox's actual kernel compatibility behavior.

Other Observations (not in diff)

Issues found in unchanged code that cannot receive inline comments:

File	Line	Issue
nemoclaw-blueprint/policies/openclaw-sandbox-permissive.yaml	35	Landlock compatibility remains best_effort while base policy changed to strict - intentional inconsistency but worth documenting or aligning.
agents/hermes/policy-additions.yaml	34	Landlock compatibility remains best_effort while base policy changed to strict.
agents/hermes/policy-permissive.yaml	36	Landlock compatibility remains best_effort while base policy changed to strict.
agents/openclaw/policy-permissive.yaml	30	Landlock compatibility remains best_effort while base policy changed to strict.
docs/deployment/sandbox-hardening.md	116-117	Documentation states "Files outside the writable paths would be inaccessible to the agent regardless of DAC permissions" - this DAC fallback behavior only applies with best_effort mode, not strict.

Files Reviewed (1 files)

• nemoclaw-blueprint/policies/openclaw-sandbox.yaml - Policy change: landlock compatibility from best_effort to strict

---

_{Reviewed by laguna-m.1-20260312:free · 1,115,183 tokens}