correx

T

kami e32bd121e5 fix: store ProcessResult artifact for every shell tool outcome, not only FATAL

Move ProcessResult artifact content storage into dispatchToolCalls so it
fires for all outcomes (success, ERROR, FATAL) — the spec mandates the
artifact MUST always be produced.

- dispatchToolCalls now stores ProcessResult JSON in CAS + cache for
  every tool call result, using the current toolCall's function.arguments
  as the command field (not firstOrNull)
- Replace storeFailedProcessResult with emitProcessResultEvents — event
  emission only, content already stored by dispatchToolCalls
- FATAL and ERROR branches both now emit artifact lifecycle events,
  fixing the gap where retryable ToolResult.Failure produced no artifact

2026-05-26 17:33:07 +04:00

apps

fix(server): send SessionStarted/StageToolManifest before launching orchestrator

2026-05-26 16:03:13 +04:00

core

fix: store ProcessResult artifact for every shell tool outcome, not only FATAL

2026-05-26 17:33:07 +04:00

docs

docs: add module documentation in AsciiDoc with PlantUML diagrams

2026-05-26 16:59:21 +04:00

examples/workflows

fix(apps): send workflowId not path from CLI; wire sandboxRoot and systemPromptPath in server; update prompts and fixtures