Fix ops sentinel runtime guard import

Proof: ops-sentinel runtime evaluation no longer throws ReferenceError while checking disabled executor containment; covered by a regression test and full npm test.

Assumptions: Runtime containment remains intentionally disabled by shouldContainExecutorForAlerts returning false; this change only restores the symbol needed for evaluation to complete.

Still fake: Alert surfaces remain suppressed per the current safety/alert simplification; venue-native terminal fill events and realized per-trade PnL are still unavailable.

src/apps/ops-sentinel.mjs

@@ -13,6 +13,7 @@ import {
   buildRuntimeAlert,
   createRuntimeHealthThresholds,
   evaluateRuntimeHealth,
+  shouldContainExecutorForAlerts,
   shouldRaiseIngestPublishStale,
 } from '../core/runtime-health.mjs';
 import {

test/ops-sentinel-static.test.mjs

@@ -0,0 +1,13 @@
+import test from 'node:test';
+import assert from 'node:assert/strict';
+import { readFileSync } from 'node:fs';
+
+const source = readFileSync(new URL('../src/apps/ops-sentinel.mjs', import.meta.url), 'utf8');
+
+test('ops sentinel imports executor containment guard used by runtime evaluation', () => {
+  assert.match(source, /shouldContainExecutorForAlerts\(alerts\)/);
+  assert.match(
+    source,
+    /import\s*\{[\s\S]*shouldContainExecutorForAlerts[\s\S]*\}\s*from\s*'\.\.\/core\/runtime-health\.mjs';/,
+  );
+});