moving
Some checks failed
Installer Smoke / installer-smoke (push) Has been cancelled

This commit is contained in:
Oleg Maslov
2026-09-02 10:10:29 +02:00
commit 0c3e2ead3b
3841 changed files with 970576 additions and 0 deletions

View File

@@ -0,0 +1,60 @@
/**
* Verification-before-completion gate (premium harness D3 — structural).
*
* R3 (`f9be0b4`) put the "a task is not done until verified" contract in
* BEHAVIORAL_SPEC as prose. R6 is direct evidence that a model does not
* reliably obey in-context discipline. Premium D3 ("not done until
* verified; reproduce the check") therefore needs a STRUCTURAL gate, the
* same way R2/R5a made memory integrity structural rather than prose.
*
* This classifier flags a final turn that *asserts* the work is
* verified / passing / working while NO verification-class tool was run
* that turn — i.e. an unverified completion claim, the exact
* confabulation R3 prohibits. The agent loop uses it to force ONE
* corrective turn before accepting completion (one-shot; loop-guard /
* maxTurns still bound the loop).
*
* Pure + conservatively tuned: it must fire on explicit success/verified
* assertions and NOT on neutral "done", honest "I could not verify"
* non-claims, or turns where a check actually ran. False negatives are
* safe (no behavior change); false positives would disrupt normal flows,
* so the bar to fire is deliberately high.
*/
/** Tool-name fragments that count as actually running a check. */
const VERIFICATION_TOOL = /test|build|\brun\b|run_|verif|lint|typecheck|tsc|pytest|jest|vitest|exec|bash|compile|spec/i;
/** Explicit "the work is verified / passing / working" success assertions. */
const SUCCESS_ASSERTION: RegExp[] = [
/\b(?:all\s+)?(?:tests?|suite|specs?)\s+(?:pass(?:ed|ing)?|are\s+green|is\s+green)\b/i,
/\b\d+\s+tests?\s+(?:pass(?:ed|ing)?|green)\b/i,
/\bbuild\s+(?:succeed(?:s|ed)?|passes|is\s+green)\b/i,
/\bit\s+(?:now\s+)?compiles?\b|\beverything\s+compiles\b/i,
/\bI(?:'ve| have)?\s+verified\b|\bverified\s+(?:that\s+)?(?:everything|it|the)\b/i,
/\bit\s+works\s+(?:now|correctly|as\s+expected)\b|\beverything\s+works\b/i,
/\bI\s+ran\s+it\b[^.]*\b(?:correct|works?|pass(?:es|ed)?)\b/i,
/\b(?:confirmed|validated)\s+(?:it|the|that)\b[^.]*\b(?:works?|passes?|correct)\b/i,
];
/**
* True when `content` asserts verified/passing/working completion but
* none of `toolsUsed` is a verification-class tool — an unverified
* completion claim that must not be accepted as "done".
*/
export function assertsUnverifiedCompletion(content: string, toolsUsed: readonly string[]): boolean {
if (!content || content.length < 12) return false;
// A check actually ran this turn → the claim is grounded; do not fire.
if (toolsUsed.some(t => VERIFICATION_TOOL.test(t))) return false;
return SUCCESS_ASSERTION.some(re => re.test(content));
}
/**
* One-shot corrective directive injected when the gate fires. Mirrors
* BEHAVIORAL_SPEC's verification contract into an actionable instruction.
*/
export const VERIFICATION_GATE_DIRECTIVE =
'You asserted the work is verified/passing/working but ran no verification '
+ 'tool this turn. Per the verification-before-completion contract: actually '
+ 'run the check now (the tests / build / the original reproduction) and quote '
+ 'the real output, OR explicitly label the result UNVERIFIED and say what '
+ 'remains unchecked. Do not reassert success without evidence.';