@lmzhen/dsh-evolution-approval 0.3.67 → 0.3.69

package/lib/index.js

@@ -6,8 +6,13 @@ import z from "@deepseek-ai/schemastery";
 * Stage/pending write approval for self-evolution mutations.
 *
 * DSH's native approval seam is one-shot only. This service adds the
-* Hermes-style staged queue: background review/curator writes are stored in
-* `ctx.evolutionState`, and a human approves or rejects them later. A runner
+* Hermes-style staged queue: a write whose ORIGIN is the background review —
+* or a foreground write while `stageForeground` is on — is recorded in
+* `ctx.evolutionState`, and a human approves or rejects it later. The CURATOR
+* does NOT route through this queue: it owns its own gate set and writes
+* directly (batch/consolidate), so "curator writes are staged" is not a
+* property of this service (V27 G6.2; see evolution-curator's gate set for what
+* actually constrains an autonomous curator write). A runner
 * registry replays the exact mutation without passing through the gate a
 * second time. Resolved records are kept as audit history up to
 * PENDING_RESOLVED_CAP (the most recent N; the state provider archives the
@@ -228,7 +233,7 @@ var EvolutionApproval = class extends Service {
 				await this.state().releasePendingClaim(id, claimId);
 				return {
 					ok: false,
-					message: result.message
+					message: /changed since this plan|no entry matching|not found|no longer exists/i.test(result.message) ? `${result.message} — a sibling write from the same plan may have already changed this target, so repeated approves will keep failing. Reject this record unless the target changed again.` : result.message
 				};
 			}
 		} catch (error) {
@@ -239,7 +244,15 @@ var EvolutionApproval = class extends Service {
 				message: "Replay runner failed; the pending write remains pending."
 			};
 		}
-		if (!(await this.state().tryResolvePending(id, "approved", claimId)).applied) {
+		const resolution = await this.state().tryResolvePending(id, "approved", claimId).catch((error) => {
+			this.ctx.logger.warn(error);
+			return `failed: ${error instanceof Error ? error.message : String(error)}`;
+		});
+		if (typeof resolution === "string") return {
+			ok: false,
+			message: `Approved write "${id}" was replayed, but resolving the record failed (${resolution.slice(8)}) — the effect has LANDED while the audit row stays "executing". Verify the write manually; approve will not re-run it.`
+		};
+		if (!resolution.applied) {
 			if ((await this.state().listPending("rejected")).find((item) => item.id === id)) return {
 				ok: false,
 				message: `Approved write "${id}" was replayed, but the record was resolved to "rejected" concurrently — the effect has landed while the audit reads rejected. Verify the write and do NOT replay it.`

package/lib/types/index.d.ts

@@ -2,8 +2,13 @@
  * Stage/pending write approval for self-evolution mutations.
  *
  * DSH's native approval seam is one-shot only. This service adds the
- * Hermes-style staged queue: background review/curator writes are stored in
- * `ctx.evolutionState`, and a human approves or rejects them later. A runner
+ * Hermes-style staged queue: a write whose ORIGIN is the background review —
+ * or a foreground write while `stageForeground` is on — is recorded in
+ * `ctx.evolutionState`, and a human approves or rejects it later. The CURATOR
+ * does NOT route through this queue: it owns its own gate set and writes
+ * directly (batch/consolidate), so "curator writes are staged" is not a
+ * property of this service (V27 G6.2; see evolution-curator's gate set for what
+ * actually constrains an autonomous curator write). A runner
  * registry replays the exact mutation without passing through the gate a
  * second time. Resolved records are kept as audit history up to
  * PENDING_RESOLVED_CAP (the most recent N; the state provider archives the
@@ -31,6 +36,13 @@ export interface ApprovalRequest {
      * so the write is allowed instead of staging an unanswerable pending record
      * (claw alignment: "skip approval for non-interactive contexts"). Absent
      * (no session / no approval service) keeps the previous behavior.
+     *
+     * V27 G6.2: this field is a FALLBACK, not the authority. With the platform
+     * `approval` service mounted, `request()` derives the policy from it
+     * (`overrideOf` → deployment `config.policy` → 'ask') and ignores this value
+     * entirely; it is read only in assemblies WITHOUT that service. A caller
+     * holding the session object must pass it as `session`: a bare `sessionId`
+     * cannot be probed (the platform reads `session.events` off the object).
      */
     sessionPolicy?: 'ask' | 'never';
     /** 0.3.17 (E-25): the requesting session id, kept on the record for

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@lmzhen/dsh-evolution-approval",
   "description": "Stage/pending approval service for Hermes-style self-evolution writes (community build)",
-  "version": "0.3.67",
+  "version": "0.3.69",
   "publishConfig": {
     "access": "public"
   },
@@ -35,15 +35,15 @@
   "peerDependencies": {
     "@deepseek-ai/dsh-invariants": "^0.1.1-rc.2",
     "@deepseek-ai/cordis": "^4.0.1",
-    "@lmzhen/dsh-evolution-state-storage": "^0.3.67",
-    "@lmzhen/dsh-evolution-state": "^0.3.67"
+    "@lmzhen/dsh-evolution-state-storage": "^0.3.69",
+    "@lmzhen/dsh-evolution-state": "^0.3.69"
   },
   "devDependencies": {
     "@deepseek-ai/dsh-invariants": "^0.1.1-rc.2",
-    "@lmzhen/dsh-evolution-state-storage": "^0.3.67",
-    "@lmzhen/dsh-evolution-state": "^0.3.67",
-    "@lmzhen/dsh-evolution-io": "^0.3.67",
-    "@lmzhen/dsh-evolution-io-node": "^0.3.67",
-    "@lmzhen/dsh-evolution-state-json": "^0.3.67"
+    "@lmzhen/dsh-evolution-state-storage": "^0.3.69",
+    "@lmzhen/dsh-evolution-state": "^0.3.69",
+    "@lmzhen/dsh-evolution-io": "^0.3.69",
+    "@lmzhen/dsh-evolution-io-node": "^0.3.69",
+    "@lmzhen/dsh-evolution-state-json": "^0.3.69"
   }
 }