feat: require concrete evidence for progress claims

scripts/long_task_gate_lock.mjs

@@ -197,7 +197,7 @@ function claimsProgressionWithoutEvidence(input) {
 
   if (!hasNonEmptyString(progressionClaim)) return false;
 
-  return !(hasProgressEvidence(input) || hasExecutionEvidence(input));
+  return !hasProgressEvidence(input);
 }
 
 function evaluateGate(input) {

scripts/test_force_recall_long_task_preflight.mjs

@@ -69,8 +69,10 @@ async function main() {
     'reason=claimed progression without concrete progress evidence is forbidden',
     'requiredEvidence=progressEvidence',
     'requiredValue=sessionKey, runId, modified_files, verification result, or equivalent concrete progress evidence',
+    'ENFORCEMENT: Hook input should include progressEvidence (or equivalent concrete fields) whenever a progression claim is present.',
     'HARD_GATE: Block any plain-text handoff or silent-continuation claim when externalized checkpoint evidence is missing.',
     'HARD_GATE: Block any reply path that says you already moved into the next task or are advancing the next step without concrete progress evidence.',
+    'HARD_GATE: If a progression claim exists, the hook input must supply progressEvidence (or equivalent concrete fields) before the claim can pass gate.',
     'HARD_GATE: Do not say you are already on the next task, already dispatched follow-up work, or already progressing in background unless you can point to a sessionKey, runId, modified_files record, verification result, actual tool execution, file changes, emitted messages, or checkpoint records.',
     'ENFORCEMENT: Forbidden path: plain-text handoff that pretends the long task is already continuing without an externalized checkpoint.',
     'ENFORCEMENT: Forbidden path: stating you have already entered the next task/step when the record only contains planning language and no concrete execution evidence.',