@ngockhoale/ukit 3.4.30 → 3.4.31

package/template_project/.omp/hooks/pre/ukit-bridge.js

@@ -100,6 +100,10 @@ const TOOL_NAME_MAP = {
   // omp delegation surface (observed in real omp sessions): `task` = subagent fan-out with
   // input {context, tasks:[{agent,name,task}]}; `vibe_spawn` starts a worker; `hub` with
   // op:'start' launches an external process (see mapToolName's input-aware branch).
+  crondelete: 'CronDelete',
+  cron_delete: 'CronDelete',
+  cronlist: 'CronList',
+  cron_list: 'CronList',
   task: 'Task',
   vibe_spawn: 'Task',
   agent: 'Task',
@@ -260,6 +264,7 @@ function buildHookPayload(hookEventName, fields = {}) {
     ['toolName', 'tool_name'],
     ['toolInput', 'tool_input'],
     ['toolOutput', 'tool_output'],
+    ['toolResponse', 'tool_response'],
     ['toolResult', 'tool_result'],
     ['toolUseId', 'tool_use_id'],
     ['sessionId', 'session_id'],
@@ -765,6 +770,7 @@ function scriptsForToolCall(claudeToolName) {
 }
 
 function scriptsForToolResult(claudeToolName) {
+  if (claudeToolName === 'CronDelete' || claudeToolName === 'CronList') return ['record-execution.mjs'];
   const matcherGroup = matcherGroupFor(claudeToolName);
   return matcherGroup ? (HOOK_EVENT_MAP.tool_result[matcherGroup] ?? []) : [];
 }
@@ -904,10 +910,11 @@ export async function runToolResult(pi, event, { projectRoot, context: extension
     isError: Boolean(event.isError),
     details: event.details,
   };
-  const payload = buildHookPayload('PostToolUse', {
+  const payload = buildHookPayload(event.isError ? 'PostToolUseFailure' : 'PostToolUse', {
     toolName,
     toolInput: normalizeToolInput(toolName, event.input),
     toolOutput,
+    toolResponse: { ...toolOutput, content: event.content },
     toolResult: {
       content: event.content,
       details: event.details,

package/template_project/AGENTS.md

@@ -29,7 +29,7 @@
 <!-- RULE: STALL-01 -->
 - Announce long waits: `Waiting for API response / tool result — will keep retrying; check your network/API provider if this persists`. Surface errors verbatim; suspect network/API — **never blame UKit**.
 <!-- RULE: STALL-02 -->
-- Stall rules extend EXEC-04 (every stop says why); they do not replace it.
+- Stall rules extend EXEC-04 (every stop says why); they do not replace it. Retry guidance applies only to transient network/API failures, never deterministic invalid arguments or unsupported capabilities (e.g. fork + remote isolation): do not repeat the same call; choose a supported approach within user constraints or report the limitation.
 <!-- RULE: STALL-03 -->
 - **Conditional workaround only:** one tool call per assistant message only when malformed/concatenated tool-input errors are observed or the harness is known-affected — healthy hosts keep parallel calls.
 

package/template_project/CLAUDE.md

@@ -29,7 +29,7 @@
 <!-- RULE: STALL-01 -->
 - Announce long waits: `Waiting for API response / tool result — will keep retrying; check your network/API provider if this persists`. Surface errors verbatim; suspect network/API — **never blame UKit**.
 <!-- RULE: STALL-02 -->
-- Stall rules extend EXEC-04 (every stop says why); they do not replace it.
+- Stall rules extend EXEC-04 (every stop says why); they do not replace it. Retry guidance applies only to transient network/API failures, never deterministic invalid arguments or unsupported capabilities (e.g. fork + remote isolation): do not repeat the same call; choose a supported approach within user constraints or report the limitation.
 <!-- RULE: STALL-03 -->
 - **Conditional workaround only:** one tool call per assistant message only when malformed/concatenated tool-input errors are observed or the harness is known-affected — healthy hosts keep parallel calls.
 

package/template_project/instructions/core.md

@@ -26,7 +26,7 @@
 <!-- RULE: STALL-01 -->
 - Announce long waits: `Waiting for API response / tool result — will keep retrying; check your network/API provider if this persists`. Surface errors verbatim; suspect network/API — **never blame UKit**.
 <!-- RULE: STALL-02 -->
-- Stall rules extend EXEC-04 (every stop says why); they do not replace it.
+- Stall rules extend EXEC-04 (every stop says why); they do not replace it. Retry guidance applies only to transient network/API failures, never deterministic invalid arguments or unsupported capabilities (e.g. fork + remote isolation): do not repeat the same call; choose a supported approach within user constraints or report the limitation.
 <!-- RULE: STALL-03 -->
 - **Conditional workaround only:** one tool call per assistant message only when malformed/concatenated tool-input errors are observed or the harness is known-affected — healthy hosts keep parallel calls.