…range

Patch 4 monkey-patches OpenClaw's `replaceConfigFile` to suppress EACCES
inside the sandbox.  Until the upstream fix in openclaw/openclaw#72950
lands, the patch's only effect is downgrading a hard EACCES crash to a
warning during plugin metadata persistence (plugins still load via
auto-discovery from extensions/).

But the patch's regex tracks OpenClaw's internal source shape, and each
OpenClaw refactor has broken it -- v0.0.29 hit one such break (#2686);
v0.0.40 on macOS hit a stale-install variant (#3497).  Each break is a
hard image-build failure even though the patch is, by design, a fallback
for noisier behaviour in the sandbox.

Replace the hard-assert with a version-gated soft-fail:

* `rcf_patch.py` now reads `OPENCLAW_VERSION` from env.  When it exceeds
  the new `LAST_OPENCLAW_NEEDING_RCF_PATCH` sentinel, the script exits 0
  without touching the source on the assumption that the upstream fix
  has landed and the patch is no longer needed.  Maintainers bump the
  sentinel DOWN once that becomes true.

* When the regex fails to match -- the OpenClaw refactor case the
  hard-assert was guarding -- the script now emits a loud
  `[nemoclaw] WARN` line and exits 0.  Plugin metadata persistence in
  the sandbox surfaces raw EACCES at runtime instead of being suppressed,
  but the image still builds.  The Dockerfile's post-patch grep follows
  the same shape (`echo WARN`, not `exit 1`).

* `test/rcf-patch.test.ts` covers the four new branches: pattern miss
  (soft-warn), missing function (soft-warn), past-sentinel skip, and
  unparseable / empty `OPENCLAW_VERSION` (still attempts the patch).

Signed-off-by: Tinson Lai <tinsonl@nvidia.com>

Patch 4 (Dockerfile step 17 + scripts/rcf_patch.py) used a regex over
OpenClaw's compiled JS to wrap `replaceConfigFile` in an EACCES try/catch
suppression for the read-only sandbox. The regex tracked OpenClaw's
internal source shape, which has already broken twice (#2686, #3497) and
will break again every time the upstream refactors the function.

Switch to a runtime trap via `NODE_OPTIONS=--require` instead:

* nemoclaw-blueprint/scripts/openclaw-rcf-shim.js hooks
  `Module.prototype.require`, detects when the OpenClaw `mutate.js`
  module loads, and wraps the exported `replaceConfigFile` with the
  same try/catch behaviour. The wrap is gated on the running OpenClaw
  version being at or below a sentinel
  (`last_openclaw_needing_rcf_shim` in blueprint.yaml, initial value
  `9999.99.99`).  Bump the sentinel DOWN when openclaw/openclaw#72950
  lands; the shim then self-disables for newer versions.
* scripts/nemoclaw-start.sh::install_openclaw_rcf_shim() reads the
  sentinel from blueprint.yaml and the current OpenClaw version from
  `openclaw --version`, exports both as env vars the shim consumes,
  and threads `--require` into `NODE_OPTIONS`.
* The Dockerfile's Step 16 emits a subtle INFO note when the sentinel
  still sits above min_openclaw_version — a maintenance nudge to keep
  the sentinel current as openclaw/openclaw#72950 progresses.
* Drop scripts/rcf_patch.py and test/rcf-patch.test.ts entirely.
* Add test/openclaw-rcf-shim.test.ts covering the six behaviour
  branches (no-op outside sandbox, EACCES swallow + synthesised
  ConfigReplaceResult, non-EACCES re-throw, happy-path pass-through,
  past-sentinel skip, non-matching filename skip).
* schemas/blueprint.schema.json gains the new sentinel key; the
  blueprint validation test covers it.
* src/lib/sandbox/build-context.ts no longer stages rcf_patch.py.

Resolves #2686
Resolves #3497
Refs openclaw/openclaw#72950 (upstream defect; this PR only stops the
crash, the real fix has to land there)

Signed-off-by: Tinson Lai <tinsonl@nvidia.com>

Patch 4 is a regex-based monkey-patch over OpenClaw's compiled JS that
suppresses EACCES inside replaceConfigFile. Its source-shape coupling
has broken three times in eight days (#2377, #2484, #2876) chasing
upstream refactors; #2686 and #3497 report the latest casualty, where
the regex no longer finds the function in 2026.4.24 and the image build
fails.

Patch 4 is also unnecessary by design:

* In mutable-default mode, openclaw.json is chmod 660 sandbox:sandbox
  and the gateway UID is in the sandbox group (#2681), so plugin
  install writes through without ever hitting EACCES.
* In shields-up mode, the entire config tree (file + parent dir + the
  plugin/extensions state dirs in HIGH_RISK_STATE_DIRS) is locked to
  root:root by design — refusing runtime mutations is the whole point
  of shields-up. Suppressing the EACCES masked that refusal and made
  the install appear to succeed silently while only the auto-discovery
  half landed.

The expected flow is configure-in-mutable-mode → shields up → run.
Plugin install attempted while shielded should fail cleanly, which is
what happens without Patch 4.

Reverts the rcf-shim replacement attempt; the require-hook approach
does not catch OpenClaw's ESM named imports anyway (capture-at-import-
time semantics).

Resolves #2686
Resolves #3497

Signed-off-by: Tinson Lai <tinsonl@nvidia.com>