pi-usereq 0.77.0 → 0.79.0

package/README.md

@@ -1,4 +1,4 @@
-# PI-useReq/pi-usereq (0.77.0)
+# PI-useReq/pi-usereq (0.79.0)
 
 <p align="center">
   <img src="https://img.shields.io/badge/python-3.11%2B-3776AB?style=flat-square&logo=python&logoColor=white" alt="Python 3.11+">

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-usereq",
-  "version": "0.77.0",
+  "version": "0.79.0",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/Ogekuri/PI-useReq.git"

package/src/core/debug-runtime.ts

@@ -891,6 +891,35 @@ export function formatPromptDebugErrorFileName(
   return `${formatPromptDebugTimestamp(date)}-${getDebugPromptName(promptName)}-error-${errorCode}`;
 }
 
+/**
+ * @brief Resolves the failing HTTP status carried by one finalized agent message.
+ * @details Extracts the leading provider error status from one `message_end` assistant message whose `stopReason` equals `error`, accepting the pi `formatProviderError` display shapes (`"<status>: <body>"` and `"<prefix> (<status>): <body>"`) plus the raw SDK `error.message` shape (`"<status> <body>"`) surfaced unchanged by the agent run-failure path, so provider APIs whose SDK clients throw before emitting `after_provider_response` for non-2xx statuses (the OpenAI-compatible family, including `zai`) still flush the captured provider request payload through the message lifecycle channel. Runtime is O(n) in the inspected error-message prefix length. No external state is mutated.
+ * @param[in] message {unknown} Finalized agent message forwarded by one `message_end` lifecycle event.
+ * @return {number | undefined} Failing HTTP status greater than or equal to `400`, or `undefined` when the message carries no provider error status.
+ * @satisfies REQ-422, REQ-423, REQ-425
+ */
+export function resolveProviderErrorFlushStatusFromMessage(message: unknown): number | undefined {
+  if (typeof message !== "object" || message === null) {
+    return undefined;
+  }
+  const candidateMessage = message as { role?: unknown; stopReason?: unknown; errorMessage?: unknown };
+  if (candidateMessage.role !== "assistant" || candidateMessage.stopReason !== "error") {
+    return undefined;
+  }
+  if (typeof candidateMessage.errorMessage !== "string") {
+    return undefined;
+  }
+  const unprefixedStatus = /^(\d{3}):/.exec(candidateMessage.errorMessage)?.[1];
+  const prefixedStatus = /^[^(]+\((\d{3})\): /.exec(candidateMessage.errorMessage)?.[1];
+  const rawSdkStatus = /^(\d{3})\s/.exec(candidateMessage.errorMessage)?.[1];
+  const statusText = unprefixedStatus ?? prefixedStatus ?? rawSdkStatus;
+  if (statusText === undefined) {
+    return undefined;
+  }
+  const status = Number.parseInt(statusText, 10);
+  return Number.isFinite(status) && status >= 400 ? status : undefined;
+}
+
 /**
  * @brief Serializes one provider request payload into deterministic text.
  * @details Pretty-prints the payload as JSON while degrading circular references into one `[Circular]` token and bigint values into decimal strings so serialization failures never discard the capture. Runtime is O(n) in serialized payload size. No external state is mutated.

package/src/core/extension-status.ts

@@ -824,13 +824,13 @@ export function setPiUsereqWorkflowState(
 
 /**
  * @brief Updates mutable status state for one intercepted lifecycle hook.
- * @details Refreshes stored context usage on every hook, resets or restores persisted elapsed counters during `session_start`, loads the active runtime sound level from persisted config during `session_start`, restores persisted prompt-command metadata when the active session matches a forked execution session, resynchronizes that metadata on later lifecycle hooks so post-switch workflow transitions performed by the initiating command handler become visible to the replacement-session runtime, resets workflow state to `idle` for documented session-start reasons, starts run timing on `agent_start`, promotes pending prompt-request metadata into the active run, captures non-aborted run duration on `agent_end` or `agent_settled`, accumulates successful runtime into `Σ`, preserves in-memory prompt-command state plus process-scoped persistence across switch-triggered `session_shutdown`, tolerates stale post-replacement render contexts, synchronizes the live ticker, and re-renders the status bar with the runtime extension identity prefix when configuration is available. Runtime is O(n) in `agent_end` message count and otherwise O(1). Side effects include in-memory state mutation, interval scheduling, process-scoped persistence mutation, and footer-status updates.
+ * @details Refreshes stored context usage on every hook, resets or restores persisted elapsed counters during `session_start`, loads the active runtime sound level from persisted config during `session_start`, restores persisted prompt-command metadata when the active session matches a forked execution session, resynchronizes that metadata on later lifecycle hooks so post-switch workflow transitions performed by the initiating command handler become visible to the replacement-session runtime, resets workflow state to `idle` for documented session-start reasons, starts run timing and promotes the pending prompt-request metadata into the active run on `agent_start` while preserving an already-promoted active request across pi-host agent-run restarts such as overflow compact-and-retry recovery, captures non-aborted run duration on `agent_end` or `agent_settled`, accumulates successful runtime into `Σ`, preserves in-memory prompt-command state plus process-scoped persistence across switch-triggered `session_shutdown`, tolerates stale post-replacement render contexts, synchronizes the live ticker, and re-renders the status bar with the runtime extension identity prefix when configuration is available. Runtime is O(n) in `agent_end` message count and otherwise O(1). Side effects include in-memory state mutation, interval scheduling, process-scoped persistence mutation, and footer-status updates.
  * @param[in,out] controller {PiUsereqStatusController} Mutable status controller.
  * @param[in] hookName {PiUsereqStatusHookName} Intercepted hook name.
  * @param[in] event {unknown} Hook payload forwarded from the wrapper.
  * @param[in] ctx {ExtensionContext} Active extension context.
  * @return {void} No return value.
- * @satisfies REQ-009, REQ-117, REQ-118, REQ-119, REQ-123, REQ-124, REQ-125, REQ-159, REQ-169, REQ-217, REQ-221, REQ-278, REQ-279, REQ-280, REQ-285
+ * @satisfies REQ-009, REQ-117, REQ-118, REQ-119, REQ-123, REQ-124, REQ-125, REQ-159, REQ-169, REQ-217, REQ-221, REQ-278, REQ-279, REQ-280, REQ-285, REQ-421
  */
 export function updateExtensionStatus(
   controller: PiUsereqStatusController,
@@ -869,8 +869,18 @@ export function updateExtensionStatus(
 
   if (hookName === "agent_start") {
     controller.state.runStartTimeMs = nowMs;
-    controller.state.activePromptRequest = controller.state.pendingPromptRequest;
-    controller.state.pendingPromptRequest = undefined;
+    // Promote only when a pending request exists: the pi host restarts the agent run for
+    // overflow compact-and-retry recovery (agent_end -> session_before_compact ->
+    // session_compact -> agent_start -> retried provider request) while the originating
+    // prompt-command orchestration stays in flight. Overwriting the already-promoted
+    // active request with an undefined pending request would drop the run from controller
+    // state and process-scoped persistence, silencing every retried before_provider_request
+    // capture (REQ-421) and the later matched-success or matched-failure closure handling.
+    const pendingPromptRequest = controller.state.pendingPromptRequest;
+    if (pendingPromptRequest !== undefined) {
+      controller.state.activePromptRequest = pendingPromptRequest;
+      controller.state.pendingPromptRequest = undefined;
+    }
   }
 
   if (

package/src/index.ts

@@ -150,6 +150,7 @@ import {
   normalizeDebugStatusChanges,
   normalizeDebugToolCommandsEnabled,
   normalizeDebugWorkflowEvents,
+  resolveProviderErrorFlushStatusFromMessage,
   setRuntimeDebugEnabled,
   shouldLogDebugPromptWorkflowState,
   type DebugLogOnStatus,
@@ -1448,7 +1449,7 @@ async function finalizeMatchedPromptSuccess(
 
 /**
  * @brief Handles one intercepted pi lifecycle hook for pi-usereq status updates.
- * @details Applies session-start-specific resource validation, project-config refresh, idle-time shared-tokenizer and context-file measurement pre-warm, startup-tool enablement, and selected debug-tool logging before forwarding the originating hook name and payload into the shared `updateExtensionStatus(...)` pipeline. After the status update, captures the exact `before_provider_request` provider payload for the live active or pending prompt run with a fresh config fallback when the controller has no cached config, flushes the process-scoped captured payload as one `<timestamp>-<req-command>-error-<status>` file whenever `after_provider_response` reports a status >= 400 without requiring live workflow state, and discards the capture at prompt-run end so stale payloads never reach later runs. Before `agent_start`, re-verifies any prepared prompt execution session switch. On `agent_end`, dispatches configured command-notify, sound, and prompt-specific Pushover effects, logs dedicated workflow-closure diagnostics, classifies the prompt outcome, and for every matched successful worktree-backed completion defers the restore switch, stash-assisted merge, and worktree deletion to `agent_settled` when the running pi host supports that 0.80.4+ event (because its `switchSession` awaits the active agent run to become idle and would deadlock inside `agent_end`), or executes the finalization directly at `agent_end` when the host does not emit `agent_settled`. On `agent_settled`, reuses persisted replacement-session command contexts when event contexts omit `switchSession()`, executes the deferred stash-assisted merge-and-delete finalization path, emits a warning-only notification when restored `base-path` changes are reapplied after merge, tolerates stale replacement-session notification contexts after session replacement, retains the worktree plus notifies closure failure for interrupted or failed outcomes, logs selected prompt workflow transitions, and transitions workflow state through `merging`, `error`, and `idle` as required. On `session_shutdown`, captures pre-update prompt snapshots so workflow-shutdown diagnostics and same-runtime command continuation preserve the active prompt workflow state across switch-triggered rebinding, then disposes the shared controller. Runtime is dominated by configuration loading during `session_start` and git finalization during matched successful closure handling; all other hooks are O(1). Side effects include resource checks, active-tool mutation, active-session replacement, status updates, live-ticker disposal on shutdown, optional child-process spawning, outbound HTTPS requests, branch merges, worktree deletion, and optional debug-log writes.
+ * @details Applies session-start-specific resource validation, project-config refresh, idle-time shared-tokenizer and context-file measurement pre-warm, startup-tool enablement, and selected debug-tool logging before forwarding the originating hook name and payload into the shared `updateExtensionStatus(...)` pipeline. After the status update, captures the exact `before_provider_request` provider payload for the live active or pending prompt run with a fresh config fallback when the controller has no cached config, flushes the process-scoped captured payload as one `<timestamp>-<req-command>-error-<status>` file whenever `after_provider_response` reports a status >= 400 or whenever one finalized `message_end` assistant error message carries a leading HTTP status >= 400 (the provider-independent fallback for provider APIs whose SDK clients throw before emitting `after_provider_response` for non-2xx statuses) without requiring live workflow state, and discards the capture at prompt-run end so stale payloads never reach later runs. Before `agent_start`, re-verifies any prepared prompt execution session switch. On `agent_end`, dispatches configured command-notify, sound, and prompt-specific Pushover effects, logs dedicated workflow-closure diagnostics, classifies the prompt outcome, and for every matched successful worktree-backed completion defers the restore switch, stash-assisted merge, and worktree deletion to `agent_settled` when the running pi host supports that 0.80.4+ event (because its `switchSession` awaits the active agent run to become idle and would deadlock inside `agent_end`), or executes the finalization directly at `agent_end` when the host does not emit `agent_settled`. On `agent_settled`, reuses persisted replacement-session command contexts when event contexts omit `switchSession()`, executes the deferred stash-assisted merge-and-delete finalization path, emits a warning-only notification when restored `base-path` changes are reapplied after merge, tolerates stale replacement-session notification contexts after session replacement, retains the worktree plus notifies closure failure for interrupted or failed outcomes, logs selected prompt workflow transitions, and transitions workflow state through `merging`, `error`, and `idle` as required. On `session_shutdown`, captures pre-update prompt snapshots so workflow-shutdown diagnostics and same-runtime command continuation preserve the active prompt workflow state across switch-triggered rebinding, then disposes the shared controller. Runtime is dominated by configuration loading during `session_start` and git finalization during matched successful closure handling; all other hooks are O(1). Side effects include resource checks, active-tool mutation, active-session replacement, status updates, live-ticker disposal on shutdown, optional child-process spawning, outbound HTTPS requests, branch merges, worktree deletion, and optional debug-log writes.
  * @param[in] pi {ExtensionAPI} Active extension API instance.
  * @param[in,out] statusController {PiUsereqStatusController} Mutable status controller.
  * @param[in] hookName {PiUsereqStatusHookName} Intercepted hook name.
@@ -1536,6 +1537,20 @@ async function handleExtensionStatusEvent(
       flushCapturedPromptErrorPayload(providerResponseEvent.status);
     }
   }
+  // Provider APIs whose SDK clients throw on non-2xx statuses (the OpenAI-compatible family,
+  // including `zai`) never reach their `onResponse` hook for failing responses, so
+  // `after_provider_response` stays silent exactly when REQ-422 must fire. The finalized
+  // error assistant message is the provider-independent signal: the pi agent loop emits
+  // `message_end` for every failed provider request with the HTTP status embedded in
+  // `errorMessage` by `formatProviderError`.
+  if (hookName === "message_end") {
+    const providerErrorStatus = resolveProviderErrorFlushStatusFromMessage(
+      (event as { message?: unknown }).message,
+    );
+    if (providerErrorStatus !== undefined) {
+      flushCapturedPromptErrorPayload(providerErrorStatus);
+    }
+  }
   if (hookName === "agent_end" || hookName === "agent_settled") {
     discardCapturedPromptErrorPayload();
   }