@junghanacs/entwurf 0.22.0 → 0.23.1

package/pi-extensions/lib/acp/acp-client.ts

@@ -46,8 +46,8 @@ import type { AcpTextBlock } from "./context.js";
  * shape) and never onto those four. A field rename upstream fails the typecheck
  * here rather than silently zeroing the operator's cache-effect badge.
  */
-/** One `_meta.quota.token_count` row (claude-agent-acp 0.76.0
- *  `dist/acp-agent.js:6566-6575`). `cachedInputTokens` is cache READS — the name
+/** One `_meta.quota.token_count` row (claude-agent-acp 0.79.0
+ *  `dist/acp-agent.js:6579-6588`). `cachedInputTokens` is cache READS — the name
  *  differs from `usage.cachedReadTokens` because the shape is shared with
  *  codex-acp; `cachedWriteTokens` is Claude's extra sibling. */
 export type AcpQuotaTokenCount = {
@@ -64,7 +64,7 @@ export type AcpPromptResponse = {
 	/** Vendor-private, version-pinned. `_meta` is a standard ACP extension slot
 	 *  whose values a client may not assume, and `quota` is NOT in
 	 *  claude-agent-acp's exported types — it is produced by the private
-	 *  `turnQuotaMeta()` (read at 0.76.0 `dist/acp-agent.js:6549-6558`). Read
+	 *  `turnQuotaMeta()` (read at 0.79.0 `dist/acp-agent.js:6562-6571`). Read
 	 *  defensively, never structurally required, and re-measure on a pin move. */
 	_meta?: {
 		quota?: {

package/pi-extensions/lib/acp/backend-adapter.ts

@@ -150,7 +150,7 @@ export interface AcpAdapterSettingsParams {
  *
  * During stream handling the vendor keeps a per-message snapshot in
  * `lastAssistantUsage`, but its `usage_update` publishes only the scalar `used`
- * value (read at claude-agent-acp 0.76.0 `dist/acp-agent.js:3857-3882`). Until
+ * value (read at claude-agent-acp 0.79.0 `dist/acp-agent.js:3920-3945`). Until
  * that partition is carried on the wire, NOTHING honest can go in pi's four
  * fields, so entwurf writes none of them.
  */
@@ -342,8 +342,8 @@ export const claudeAdapter: AcpBackendAdapter = {
 
 	// MEASURED (2026-09-02, #93): claude-agent-acp's `usage_update` carries a
 	// session-cumulative ESTIMATED cost (`cost.amount = message.total_cost_usd`)
-	// and a context-occupancy scalar (`used`; both read at 0.76.0
-	// `dist/acp-agent.js:3471-3486`). Both are measured, so backend.ts seals them.
+	// and a context-occupancy scalar (`used`; both read at 0.79.0
+	// `dist/acp-agent.js:3504-3519`). Both are measured, so backend.ts seals them.
 	// The token partition is NOT declared here: ACP's only token carrier is a
 	// per-turn round-trip aggregate, which is not what pi's four fields mean.
 	sealsTurnAccounting: true,

package/pi-extensions/lib/acp/backend.ts

@@ -137,7 +137,7 @@ function finiteOrZero(value: unknown): number {
  * "the accounting-grade figure per the SDK" — it also counts Task subagents,
  * sidechains, and INTERNAL CALLS SUCH AS COMPACTION, so its rows "can total more
  * than `token_count`" and are "the fuller picture, not a decomposition of it"
- * (read at claude-agent-acp 0.76.0 `dist/acp-agent.js:6538-6558`). The narrower
+ * (read at claude-agent-acp 0.79.0 `dist/acp-agent.js:6551-6571`). The narrower
  * `PromptResponse.usage` (== `quota.token_count`) is the MAIN AGENT LOOP only.
  *
  * The wider one is the right numerator because the denominator already has that
@@ -1237,7 +1237,7 @@ export function streamAcpTurn(
 		// Writing zeros is not a placeholder for a better number we could compute:
 		// the per-request partition is genuinely absent from the wire. The vendor
 		// builds it in `lastAssistantUsage` and sends only its scalar sum (read at
-		// claude-agent-acp 0.76.0 `dist/acp-agent.js:3857-3882`) — #96.
+		// claude-agent-acp 0.79.0 `dist/acp-agent.js:3920-3945`) — #96.
 		//
 		// But silence is NOT the resting state. A cache miss the operator never sees
 		// is a false reading, not a modest one: a session can run for hours believing
@@ -1356,9 +1356,9 @@ export function streamAcpTurn(
 				// between them is exactly why the notice below names a MECHANISM and
 				// never a cause: claude-agent-acp's `conversation_reset` handler only
 				// switches the SDK to a fresh conversation and touches no cost at all
-				// (read at 0.76.0 `dist/acp-agent.js:4286-4293`), while claude-agent-sdk
+				// (read at 0.79.0 `dist/acp-agent.js:4349-4356`), while claude-agent-sdk
 				// separately documents that "a mid-session /clear resets the running
-				// total" (read at 0.3.257 `sdk.d.ts:4884`). A reset therefore PLAUSIBLY
+				// total" (read at 0.3.274 `sdk.d.ts:5342`). A reset therefore PLAUSIBLY
 				// explains a backwards total, but nothing here has MEASURED that it did,
 				// and asserting the cause would be the same unmeasured claim this lane
 				// exists to end.

package/pi-extensions/lib/acp/event-mapper.ts

@@ -60,8 +60,8 @@ export type AcpPiStreamState = {
 	 *
 	 * Last write wins, never a sum: both are latest session-level observations, and
 	 * one turn can legitimately see several (claude emits one per `result` message,
-	 * including a sub-agent's own — read at claude-agent-acp 0.76.0
-	 * `dist/acp-agent.js:3471-3486`), each carrying that result's current values.
+	 * including a sub-agent's own — read at claude-agent-acp 0.79.0
+	 * `dist/acp-agent.js:3504-3519`), each carrying that result's current values.
 	 */
 	observedSessionCostUsd?: number;
 	observedContextOccupancyTokens?: number;
@@ -346,9 +346,9 @@ export function applyAcpSessionUpdate(
 		case "usage_update": {
 			// `used` is OCCUPANCY-shaped — the backend's post-turn context size, not
 			// the prompt response's turn aggregate. Claude sends `lastAssistantTotalUsage`
-			// as `used` (read at claude-agent-acp 0.76.0
-			// `dist/acp-agent.js:3871-3882`), after constructing that scalar from the
-			// latest assistant snapshot (`:3853-3866`). pi reads `usage.totalTokens` as
+			// as `used` (read at claude-agent-acp 0.79.0
+			// `dist/acp-agent.js:3934-3945`), after constructing that scalar from the
+			// latest assistant snapshot (`:3916-3929`). pi reads `usage.totalTokens` as
 			// exactly that occupancy (`calculateContextTokens(usage) = usage.totalTokens
 			// || input + output + cacheRead + cacheWrite`, read at pi-coding-agent
 			// `dist/core/compaction/compaction.js:86-88`). The assignment below is the

package/pi-extensions/lib/acp/tool-surface.ts

@@ -154,7 +154,8 @@ export function buildClaudeSessionMeta(
 		// claude-agent-acp also accepts a STRING PATH, and at 0.76.0 the readFile +
 		// JSON.parse for that form moved out of `resolvedProvider` up onto the
 		// unconditional `session/new` path — a shape that WOULD reach us, and does not,
-		// only because we never hand it a path. Keep it inline: a path would put file
+		// only because we never hand it a path. Still on that path at 0.79.0
+		// (`dist/acp-agent.js:6010-6012`). Keep it inline: a path would put file
 		// IO, and its failure modes, inside every session creation.
 		settings: {
 			permissions: {