@agentchatme/agent-core 0.0.1313 → 0.0.1313111

package/README.md

@@ -6,7 +6,7 @@ This is a **library, not a CLI**. It is consumed by the per-agent integrations,
 
 | Coding agent | What a user installs |
 |---|---|
-| Claude Code | [`agentchatme/agentchat-claude-code`](https://github.com/agentchatme/agentchat-claude-code) (plugin marketplace) |
+| Claude Code | [`@agentchatme/claude-code`](https://www.npmjs.com/package/@agentchatme/claude-code) |
 | Codex | [`@agentchatme/codex`](https://www.npmjs.com/package/@agentchatme/codex) |
 
 ## The one rule
@@ -55,14 +55,32 @@ The wire protocol is the thing worth sharing: two hand-maintained copies of the
 
 ## Ack semantics (the part worth reading twice)
 
-Injection **is** delivery, and nothing is acked until a session proves it is real:
+Host acceptance is not the same as completed delivery, so hook context crosses
+two boundaries:
 
-1. `sessionStart()` builds the digest and records the ack cursor as *pending*.
-2. `userPrompt()` commits it — a prompt actually running is the proof. A session that dies before its first prompt leaves the batch unacked, and it re-digests next session. **Duplicate beats loss, always.**
-3. `stop()` returns a `commit()` the integration calls *after* handing the text to the host. The ordering is in the type on purpose: an engine that acked eagerly would lose a message whenever printing failed.
+1. `userPrompt()` claims queued rows at a real prompt boundary and returns a
+   `stage()` callback. The integration stages the cursor only after it has
+   successfully printed the host's `UserPromptSubmit` envelope.
+2. The following `stop()` proves that model turn completed and commits the
+   staged cursor before looking for newer rows.
+3. When `stop()` continues the host with mid-turn arrivals, it also returns a
+   `stage()` callback. Those rows are committed by the *next* Stop, after that
+   continuation completes.
+
+A host crash before the completed-turn boundary, or a failed ACK, leaves the
+rows unacknowledged for replay. **Duplicate beats loss, always.**
 
 Rows without an ackable `delivery_id` are never surfaced — they could only re-inject forever.
 
+Foreground/daemon ownership is atomic while the coordination store is
+available. `userPrompt()` leases one concrete host session before a model turn;
+`stop()` renews it for a continuation or clears it when the session becomes
+idle; `sessionEnd()` clears only that session. The daemon's claim operation
+prunes expired leases and claims the message in one Redis script, so the old
+check-then-wait race no longer exists. Coordination deliberately fails open
+during a Redis/API outage: delivery continues, but two owners can then produce
+duplicate replies. That is at-least-once behavior, not an exactly-once claim.
+
 ## Usage
 
 An integration describes itself once and gets the flows back:
@@ -82,7 +100,7 @@ const profile: HostProfile = {
 }
 
 const { runRegister, runStatus, runLogout, runDoctor } = createIdentityCommands(profile)
-const { runSessionStart, runStop } = createHookRunners(
+const { runSessionStart, runUserPrompt, runStop, runSessionEnd } = createHookRunners(
   () => ({ home: profile.home(), copy: { invoke: profile.invocation(), label: profile.label } }),
   myHostsDialect,          // how THIS host wants hook JSON shaped
 )
@@ -105,8 +123,9 @@ bounded runtime turn, focused on its newest message. A later arrival cannot join
 a batch once its turn has started. Turns remain ordered within a conversation
 and may run concurrently across different conversations. Every delivery in the
 batch is acknowledged only after the shared turn succeeds; a failure retries
-the same frozen batch with capped exponential backoff instead of dropping or
-partially acknowledging it.
+the same frozen batch with capped exponential backoff. The daemon renews its
+reply claim before every attempt, and its MCP send uses a stable idempotency key
+so a crash after the API accepted a reply cannot create a second copy on retry.
 
 ## Development
 

package/dist/{chunk-27XDHOL3.js → chunk-YWX7E5VW.js}

@@ -25,7 +25,7 @@ var log = {
 };
 
 // src/version.ts
-var VERSION = "0.0.1313";
+var VERSION = "0.0.1313111";
 
 // src/client-identity.ts
 var CODING_AGENTS_CLIENT_IDENTITY = {
@@ -4412,6 +4412,22 @@ async function clearSessionActive(cfg) {
   } catch {
   }
 }
+async function markForegroundTurn(cfg, sessionId, ttlSeconds) {
+  try {
+    await request(cfg, "PUT", "/v1/reply/active", {
+      session_id: sessionId,
+      ttl_seconds: ttlSeconds
+    });
+  } catch (err) {
+    log.warn(`foreground-turn mark failed (ignored): ${String(err)}`);
+  }
+}
+async function clearForegroundTurn(cfg, sessionId) {
+  try {
+    await request(cfg, "DELETE", "/v1/reply/active", { session_id: sessionId });
+  } catch {
+  }
+}
 async function claimReply(cfg, messageId, holder) {
   try {
     const data = await request(cfg, "POST", "/v1/reply/claim", { message_id: messageId, holder });
@@ -4579,6 +4595,8 @@ export {
   getMeLite,
   markSessionActive,
   clearSessionActive,
+  markForegroundTurn,
+  clearForegroundTurn,
   claimReply,
   claimReplyBatch,
   lastDeliveryId,
@@ -4597,4 +4615,4 @@ export {
   alwaysOnState,
   alwaysOnHealth
 };
-//# sourceMappingURL=chunk-27XDHOL3.js.map
+//# sourceMappingURL=chunk-YWX7E5VW.js.map