Function checkDoneGuard

src/session/contract_guard.js:57–96

* Inspect a candidate final assistant message. If it claims completion while * the active contract still has blockers, return an injection payload the * caller can splice into history. Otherwise return null. * * Caller wires in the agent loop (bin/smallcode.js): * const guard = checkDoneGuard

(content, cwd)

 *   }
 */
function checkDoneGuard(content, cwd) {
  if (process.env.SMALLCODE_CONTRACT === 'false') return null;
  if (!looksLikeDoneClaim(content)) return null;

  let store, c;
  try {
    store = getStore(cwd || process.cwd());
    c = store.active();
  } catch {
    return null;
  }
  if (!c) return null; // no active contract → guard inactive

  const ds = c.doneStatus();
  if (ds.done) return null; // contract is fully resolved — let the response through

  const blockerLines = ds.blockers
    .map((b) => `  - ${b.id} (${b.state}) ${b.text}`)
    .join('\n');

  const injection =
`[CONTRACT-GUARD] You claimed the task is complete, but the active contract "${c.title}" (${c.id}) still has unresolved assertions:

${blockerLines}

You cannot deliver a final response while assertions are pending or failed. Do one of the following before claiming done:

  1. Run the right command(s) and call contract_assert_pass <id> with evidence
  2. Call contract_assert_fail <id> with the actual failure (if it really is broken)
  3. Call contract_assert_skip <id> with a reason (if it is genuinely out of scope)
  4. Call contract_status to refresh the assertion list

If you are blocked from completing an assertion, explain the specific blocker and ask the user — do not claim completion. Disable this guard with SMALLCODE_CONTRACT=false.`;

  return {
    injection,
    contractId: c.id,
    blockers: ds.blockers,
  };
}

module.exports = { checkDoneGuard, looksLikeDoneClaim, DONE_PATTERNS };