96b5e3cbe7
All checks were successful
deploy / deploy (push) Successful in 33s
Proof: Sentinel auto-containment now ignores quote-stale-only conditions, executor arming is exposed in the dashboard safe controls, and regression tests cover both containment gating and control routing. Assumptions: Quote silence alone is not sufficient evidence of a broken execution truth path, while ingest disconnect, publish stall, and history-writer stall remain containment-grade failures. Still fake: Live deployment still depends on the repo pipeline completing for this commit; executor disarm provenance is still not durably explained in the dashboard.
26 lines
858 B
JavaScript
26 lines
858 B
JavaScript
import test from 'node:test';
|
|
import assert from 'node:assert/strict';
|
|
|
|
import { shouldContainExecutorForAlerts } from '../src/core/runtime-health.mjs';
|
|
|
|
test('executor containment ignores quote-stale-only conditions', () => {
|
|
assert.equal(shouldContainExecutorForAlerts([{
|
|
alert_code: 'near_intents_quotes_stale',
|
|
severity: 'critical',
|
|
}]), false);
|
|
});
|
|
|
|
test('executor containment still triggers on broken truth path alerts', () => {
|
|
assert.equal(shouldContainExecutorForAlerts([{
|
|
alert_code: 'near_intents_ingest_disconnected',
|
|
severity: 'critical',
|
|
}]), true);
|
|
assert.equal(shouldContainExecutorForAlerts([{
|
|
alert_code: 'near_intents_publish_stale',
|
|
severity: 'critical',
|
|
}]), true);
|
|
assert.equal(shouldContainExecutorForAlerts([{
|
|
alert_code: 'history_writer_stalled',
|
|
severity: 'critical',
|
|
}]), true);
|
|
});
|