blun-king-cli 9.1.396 → 9.1.397

package/LIESMICH.txt

@@ -381,6 +381,17 @@ Anweisung wie "Zeig mir den letzten Telegram-Verlauf" das passende Werkzeug im
 selben Modellschritt erhalten, während Begrüßungen und fachfremde Anfragen keine
 zusätzlichen Schemata laden.
 
+Abschlussbedingungen mit Laufzeitbeleg
+--------------------------------------
+
+Ab BLUN King 9.1.397 kann ein autonomes Ziel mit ausdrücklich gesetzter
+Abschlussbedingung nicht mehr allein aufgrund einer Textbehauptung als fertig
+markiert werden. Vor dem Abschluss muss ein aktueller Prüf-Checkpoint vorliegen,
+der auf mindestens einem erfolgreichen Laufzeitwerkzeug beruht und als verifiziert
+eingestuft ist. Fehlt dieser Beleg, bleibt das Ziel aktiv und King erhält eine
+konkrete Nachbesserung statt einer falschen Fertigmeldung. Ziele ohne ausdrücklich
+gesetzte Abschlussbedingung behalten ihr bisheriges Verhalten.
+
 Angehängte Bilder werden weiterhin mit ReadMediaFile gelesen. Bild-, Video- und
 Spracherzeugung laufen asynchron, sodass die Konsole während der Verarbeitung
 nutzbar bleibt. GenerateVideo kann außerdem einen abgeschlossenen Bildauftrag

package/README.md

@@ -391,6 +391,16 @@ Anweisung wie „Zeig mir den letzten Telegram-Verlauf“ das passende Werkzeug
 selben Modellschritt erhalten, während Begrüßungen und fachfremde Anfragen keine
 zusätzlichen Schemata laden.
 
+## Abschlussbedingungen mit Laufzeitbeleg
+
+Ab BLUN King 9.1.397 kann ein autonomes Ziel mit ausdrücklich gesetzter
+Abschlussbedingung nicht mehr allein aufgrund einer Textbehauptung als fertig
+markiert werden. Vor dem Abschluss muss ein aktueller Prüf-Checkpoint vorliegen,
+der auf mindestens einem erfolgreichen Laufzeitwerkzeug beruht und als verifiziert
+eingestuft ist. Fehlt dieser Beleg, bleibt das Ziel aktiv und King erhält eine
+konkrete Nachbesserung statt einer falschen Fertigmeldung. Ziele ohne ausdrücklich
+gesetzte Abschlussbedingung behalten ihr bisheriges Verhalten.
+
 Angehängte Bilder werden weiterhin mit `ReadMediaFile` gelesen. Bild-, Video-
 und Spracherzeugung laufen asynchron, sodass die Konsole während der Verarbeitung
 nutzbar bleibt. `GenerateVideo` kann außerdem einen abgeschlossenen Bildauftrag

package/bin/goal-completion-evidence-policy.cjs

@@ -0,0 +1,57 @@
+'use strict';
+
+function hasCompletionCriterion(goal) {
+  return typeof goal?.completionCriterion === 'string'
+    && goal.completionCriterion.trim().length > 0;
+}
+
+function successfulRuntimeEvidence(checkpoint) {
+  const successfulTools = Number(checkpoint?.evidenceReceipt?.successfulTools);
+  return Number.isSafeInteger(successfulTools) && successfulTools > 0;
+}
+
+function evaluateGoalCompletionEvidence(goal) {
+  if (!hasCompletionCriterion(goal)) {
+    return {
+      required: false,
+      allPassed: true,
+      result: 'satisfied',
+      gaps: [],
+    };
+  }
+
+  const checkpoint = goal?.actionCheckpoint;
+  if (!checkpoint || typeof checkpoint !== 'object' || Array.isArray(checkpoint)) {
+    return {
+      required: true,
+      allPassed: false,
+      result: 'needs_revision',
+      gaps: ['Save a verify-phase action checkpoint before completing the goal.'],
+    };
+  }
+
+  const gaps = [];
+  if (checkpoint.phase !== 'verify') {
+    gaps.push('The latest action checkpoint must be in the verify phase.');
+  }
+  if (checkpoint.evidenceBasis !== 'runtime_tool') {
+    gaps.push('The completion proof must come from a runtime tool.');
+  }
+  if (checkpoint.epistemicState !== 'verified') {
+    gaps.push('The completion proof must be classified as verified.');
+  }
+  if (!successfulRuntimeEvidence(checkpoint)) {
+    gaps.push('The runtime evidence receipt must contain at least one successful tool result.');
+  }
+
+  return {
+    required: true,
+    allPassed: gaps.length === 0,
+    result: gaps.length === 0 ? 'satisfied' : 'needs_revision',
+    gaps,
+  };
+}
+
+module.exports = {
+  evaluateGoalCompletionEvidence,
+};

package/blun.mjs

@@ -21447,6 +21447,7 @@ var { projectSoulText } = createRequire(import.meta.url)("./bin/soul-organizatio
 var { soulFileInstruction } = createRequire(import.meta.url)("./bin/soul-preservation-policy.cjs");
 var { readProfilePersona, resolveSoulFile } = createRequire(import.meta.url)("./bin/profile-identity-resolution.cjs");
 var { advanceActionEvidenceReceipt, assertActionCheckpointEvidenceBasis, assertActionCheckpointRevision, emptyActionEvidenceReceipt, normalizeActionCheckpoint, projectActionCheckpoint } = createRequire(import.meta.url)("./bin/cognitive-action-checkpoint.cjs");
+var { evaluateGoalCompletionEvidence } = createRequire(import.meta.url)("./bin/goal-completion-evidence-policy.cjs");
 async function prepareSystemPromptContext(kaos, brandHome, options) {
 	const additionalDirs = normalizeAdditionalDirs(options?.additionalDirs ?? []);
 	const [cwdListing, agentsMdResult, additionalDirsInfo] = await Promise.all([
@@ -230394,6 +230395,10 @@ var init_goal$1 = __esmMin((() => {
 		async markComplete(input = {}, actor = "model") {
 			const state = this.state;
 			if (state === void 0 || state.status !== "active") return null;
+			const completionEvidence = evaluateGoalCompletionEvidence(state);
+			if (!completionEvidence.allPassed) {
+				throw new BlunError(ErrorCodes.GOAL_STATUS_INVALID, `Completion criterion needs revision: ${completionEvidence.gaps.join(" ")} Run the required verification, save a runtime-backed verify checkpoint, then mark the goal complete.`);
+			}
 			const mcInjector = this.agent.injection?.getMissionContractInjector();
 			if (mcInjector) {
 				const evaluation = mcInjector.evaluate();
@@ -262710,7 +262715,7 @@ var init_outcome_prompts = __esmMin((() => {}));
 //#region ../../packages/agent-core/src/tools/builtin/goal/update-goal.md?raw
 var update_goal_default;
 var init_update_goal$1 = __esmMin((() => {
-	update_goal_default = "Update the current autonomous goal. Set `status` only for a lifecycle change. After a coherent work slice, save `actionCheckpoint` with a monotone revision, the last verified result, exact next action, expected evidence, and an explicit evidence basis. Use `runtime_tool` only when a successful tool in this turn measured the result; use `user_statement` for a direct user assertion, `external_report` for a report not independently measured here, and `carried_forward` only when the last verified text is unchanged. Classify knowledge as `verified`, `credible_unverified`, `hypothesis`, `uncertain_memory`, `stale`, or `unknown`; never present a weaker state as verified, and preserve the state on carry-forward. Start at revision 1 and increment the currently projected revision by exactly one; stale writers fail closed. This is durable progress state, not permission, and should change only when the facts change. A checkpoint-only call keeps the goal active.\n\n- `active` — resume a paused or blocked goal when the user explicitly asks you to work on that goal.\n- `complete` — the objective is fully satisfied, all files are written, all tests pass, and any stated validation has passed.\n- `blocked` — a genuine external condition or required user decision prevents progress.\n- `paused` — set the goal aside for now.\n\nDo not mark complete after a plan or partial result. If useful work remains, checkpoint it and continue. Do not ask for permission merely to execute an already authorized checkpoint; ask only at a real rights boundary or missing user decision.\n";
+	update_goal_default = "Update the current autonomous goal. Set `status` only for a lifecycle change. After a coherent work slice, save `actionCheckpoint` with a monotone revision, the last verified result, exact next action, expected evidence, and an explicit evidence basis. Use `runtime_tool` only when a successful tool in this turn measured the result; use `user_statement` for a direct user assertion, `external_report` for a report not independently measured here, and `carried_forward` only when the last verified text is unchanged. Classify knowledge as `verified`, `credible_unverified`, `hypothesis`, `uncertain_memory`, `stale`, or `unknown`; never present a weaker state as verified, and preserve the state on carry-forward. Start at revision 1 and increment the currently projected revision by exactly one; stale writers fail closed. This is durable progress state, not permission, and should change only when the facts change. A checkpoint-only call keeps the goal active.\n\n- `active` — resume a paused or blocked goal when the user explicitly asks you to work on that goal.\n- `complete` — the objective is fully satisfied, all files are written, all tests pass, and any stated validation has passed. When the goal has a completion criterion, first save a `verify` checkpoint with `runtime_tool`, `verified`, and a successful runtime evidence receipt.\n- `blocked` — a genuine external condition or required user decision prevents progress.\n- `paused` — set the goal aside for now.\n\nDo not mark complete after a plan or partial result. If useful work remains, checkpoint it and continue. Do not ask for permission merely to execute an already authorized checkpoint; ask only at a real rights boundary or missing user decision.\n";
 }));
 //#endregion
 //#region ../../packages/agent-core/src/tools/builtin/goal/update-goal.ts

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "blun-king-cli",
-  "version": "9.1.396",
+  "version": "9.1.397",
   "description": "BLUN CLI - your own AI agent with a Telegram channel. Get it done. With BLUN.",
   "license": "MIT",
   "bin": {