omnius 1.0.697 → 1.0.698

package/dist/update-worker.js

@@ -292930,6 +292930,9 @@ var DECAY_TAU2 = {
 var DEFAULT_INLINE_KG_MAX_BYTES = 512 * 1024 * 1024;
 var DEFAULT_INLINE_EPISODES_MAX_BYTES = 1024 * 1024 * 1024;
 
+// packages/execution/dist/tools/diagnostic.js
+init_process_async();
+
 // packages/execution/dist/tools/background-task.js
 init_process_kill();
 init_process_lifecycle();

package/docs/DISCOVERY.json

@@ -32878,6 +32878,46 @@
         }
       ]
     },
+    {
+      "id": "guide.work-orders-runtime-health-remediation-live-telegram-log-review-2026-09-05-uppercase",
+      "kind": "guide",
+      "title": "Telegram field review after publication — September 5, 2026",
+      "summary": "Scope: read-only review requested after the user observed improvement. Runtime package is 1.0.697. The launcher started at 01:05 PDT; its current runtime child and Telegram poll owner is PID 4160370, started at 13:33 PDT. Two processes are the launcher/child relationship, not evidence of competing pollers.",
+      "keywords": [
+        "work",
+        "orders",
+        "runtime",
+        "health",
+        "remediation",
+        "LIVE",
+        "TELEGRAM",
+        "LOG",
+        "REVIEW",
+        "2026",
+        "09",
+        "05",
+        "md"
+      ],
+      "maturity": "internal",
+      "audiences": [
+        "maintainer",
+        "large-context-agent"
+      ],
+      "layer": "documentation",
+      "interfaces": [
+        {
+          "type": "file",
+          "target": "docs/work-orders/runtime-health-remediation/LIVE-TELEGRAM-LOG-REVIEW-2026-09-05.md"
+        }
+      ],
+      "references": [
+        {
+          "type": "documentation",
+          "target": "docs/work-orders/runtime-health-remediation/LIVE-TELEGRAM-LOG-REVIEW-2026-09-05.md",
+          "relation": "canonical-artifact"
+        }
+      ]
+    },
     {
       "id": "guide.work-orders-runtime-health-remediation-readme-uppercase",
       "kind": "guide",
@@ -35015,6 +35055,120 @@
         }
       ]
     },
+    {
+      "id": "guide.work-orders-runtime-health-remediation-wo-46-shell-result-authority-uppercase",
+      "kind": "guide",
+      "title": "WO-46: Preserve process authority for shell observations",
+      "summary": "Status: repository repair complete and delivered to origin/main. Publication and live validation remain with the user.",
+      "keywords": [
+        "work",
+        "orders",
+        "runtime",
+        "health",
+        "remediation",
+        "WO",
+        "46",
+        "shell",
+        "result",
+        "authority",
+        "md"
+      ],
+      "maturity": "internal",
+      "audiences": [
+        "maintainer",
+        "large-context-agent"
+      ],
+      "layer": "documentation",
+      "interfaces": [
+        {
+          "type": "file",
+          "target": "docs/work-orders/runtime-health-remediation/WO-46-shell-result-authority.md"
+        }
+      ],
+      "references": [
+        {
+          "type": "documentation",
+          "target": "docs/work-orders/runtime-health-remediation/WO-46-shell-result-authority.md",
+          "relation": "canonical-artifact"
+        }
+      ]
+    },
+    {
+      "id": "guide.work-orders-runtime-health-remediation-wo-47-diagnostic-execution-contract-uppercase",
+      "kind": "guide",
+      "title": "WO-47: Validate and execute diagnostics without blocking the agent",
+      "summary": "Status: repository repair complete and delivered to origin/main. Publication and live validation remain with the user.",
+      "keywords": [
+        "work",
+        "orders",
+        "runtime",
+        "health",
+        "remediation",
+        "WO",
+        "47",
+        "diagnostic",
+        "execution",
+        "contract",
+        "md"
+      ],
+      "maturity": "internal",
+      "audiences": [
+        "maintainer",
+        "large-context-agent"
+      ],
+      "layer": "documentation",
+      "interfaces": [
+        {
+          "type": "file",
+          "target": "docs/work-orders/runtime-health-remediation/WO-47-diagnostic-execution-contract.md"
+        }
+      ],
+      "references": [
+        {
+          "type": "documentation",
+          "target": "docs/work-orders/runtime-health-remediation/WO-47-diagnostic-execution-contract.md",
+          "relation": "canonical-artifact"
+        }
+      ]
+    },
+    {
+      "id": "guide.work-orders-runtime-health-remediation-wo-48-conversation-result-evidence-uppercase",
+      "kind": "guide",
+      "title": "WO-48: Retain command evidence in conversation results",
+      "summary": "Status: repository repair complete and delivered to origin/main. Publication and live validation remain with the user.",
+      "keywords": [
+        "work",
+        "orders",
+        "runtime",
+        "health",
+        "remediation",
+        "WO",
+        "48",
+        "conversation",
+        "result",
+        "evidence",
+        "md"
+      ],
+      "maturity": "internal",
+      "audiences": [
+        "maintainer",
+        "large-context-agent"
+      ],
+      "layer": "documentation",
+      "interfaces": [
+        {
+          "type": "file",
+          "target": "docs/work-orders/runtime-health-remediation/WO-48-conversation-result-evidence.md"
+        }
+      ],
+      "references": [
+        {
+          "type": "documentation",
+          "target": "docs/work-orders/runtime-health-remediation/WO-48-conversation-result-evidence.md",
+          "relation": "canonical-artifact"
+        }
+      ]
+    },
     {
       "id": "guide.work-orders-telegram-dmn-wo-22-dmn-outreach-and-learning-uppercase",
       "kind": "guide",

package/docs/DISCOVERY.md

@@ -534,6 +534,7 @@ Daemon equivalents are `GET /v1/discovery/bootstrap`, `GET /v1/discovery?q=<inte
 | `guide.work-orders-runtime-health-remediation-h1-h2-h7-telegram-continuity-evidence-uppercase` | H1, H2, and H7 Telegram continuity evidence | Scope: deterministic Telegram stream ownership, immutable task-local routing, exact-once text delivery evidence, bounded long-poll client replacement, bridge restart authority, and task-local delegated-agent runtime ownership. |
 | `guide.work-orders-runtime-health-remediation-h6-main-tui-wo-05-confirmation-evidence-uppercase` | H6 Main-TUI and WO-05 Confirmation Evidence | This closure wires the top-level TUI FullSubAgentTool to live parent-context headroom and the exact owning task cancellation signal. It also confirms the WO-05 completion authority after the interruption, safe-media, workboard, and canonical-context changes. |
 | `guide.work-orders-runtime-health-remediation-live-telegram-log-review-2026-09-03-uppercase` | Live Telegram Log Review, 2026-09-03 | This review is read-only. It examines the persisted Telegram conversation and intake lifecycle records in /home/roko/Documents/Projects/Adjacent/telegramtest/.omnius. The running global Omnius package reports version 1.0.687. This means the observations describe the deployed pre-publication runtime, not the newer source commits on this repository's main bran |
+| `guide.work-orders-runtime-health-remediation-live-telegram-log-review-2026-09-05-uppercase` | Telegram field review after publication — September 5, 2026 | Scope: read-only review requested after the user observed improvement. Runtime package is 1.0.697. The launcher started at 01:05 PDT; its current runtime child and Telegram poll owner is PID 4160370, started at 13:33 PDT. Two processes are the launcher/child relationship, not evidence of competing pollers. |
 | `guide.work-orders-runtime-health-remediation-readme-uppercase` | Runtime Health Remediation Program | Program ID: RHR-2026-09-02 Status: active, implementation authorized Owner: Omnius runtime, orchestration, execution, memory, and Telegram packages External dependency: /home/roko/Desktop/ollama-unify Last reconciled: 2026-09-03 |
 | `guide.work-orders-runtime-health-remediation-telegram-longhaul-2026-09-04-uppercase` | September 4 Telegram long-haul remediation | Status: complete; all five root repairs verified and delivered to origin/main Baseline: Omnius main 69c4a160; installed package 1.0.694 Incident run: telegram-64ac9937dc7647a8-1788572475259-1 Observation window: 2026-09-04 18:41–20:43 PDT Owner: repository repair; user owns publication and subsequent live testing |
 | `guide.work-orders-runtime-health-remediation-tool-quality-2026-09-05-uppercase` | September 5 tool-quality and live-behavior follow-up | Status: WO-30 through WO-42 complete in repository; full verification passed; delivered to origin/main for user publication Repository baseline: 501e8394 on origin/main Verified source head: 7005aa41; subsequent closure changes are documentation only Observed running package: 1.0.695, verified from its actual executable/package path User scope: monitor live  |
@@ -590,6 +591,9 @@ Daemon equivalents are `GET /v1/discovery/bootstrap`, `GET /v1/discovery?q=<inte
 | `guide.work-orders-runtime-health-remediation-wo-43-telegram-router-progress-boundary-uppercase` | WO-43: Keep router failures out of Telegram progress and repair routing contracts | Status: complete in repository; verified for user publication Priority: P1 Reported: September 5, 2026, after publication of 1.0.696 Source baseline: d8e6e2ed on origin/main |
 | `guide.work-orders-runtime-health-remediation-wo-44-evidence-backed-terminal-results-uppercase` | WO-44: Deliver an evidence-backed final result in Telegram | Status: complete in repository; publication and live acceptance remain with the user Priority: P1 Source baseline: 44fa69cc Observed runtime: 1.0.696, sibling telegramtest; read-only inspection |
 | `guide.work-orders-runtime-health-remediation-wo-45-native-ollama-tool-contract-uppercase` | WO-45: Preserve tools across the native Ollama transport | Status: complete — implementation, mocked transport verification and scoped Git delivery Priority: P1 for callers selecting native Ollama chat with tools Source baseline: af6fb8eb |
+| `guide.work-orders-runtime-health-remediation-wo-46-shell-result-authority-uppercase` | WO-46: Preserve process authority for shell observations | Status: repository repair complete and delivered to origin/main. Publication and live validation remain with the user. |
+| `guide.work-orders-runtime-health-remediation-wo-47-diagnostic-execution-contract-uppercase` | WO-47: Validate and execute diagnostics without blocking the agent | Status: repository repair complete and delivered to origin/main. Publication and live validation remain with the user. |
+| `guide.work-orders-runtime-health-remediation-wo-48-conversation-result-evidence-uppercase` | WO-48: Retain command evidence in conversation results | Status: repository repair complete and delivered to origin/main. Publication and live validation remain with the user. |
 | `guide.work-orders-telegram-dmn-wo-22-dmn-outreach-and-learning-uppercase` | WO-22: DMN outreach, DM sharing, and outcome learning | On 2026-09-03 at 17:07 PDT the bot posted in the OMNIUS group without being addressed. The operator asked whether this was self-induced reflection. |
 | `guide.work-orders-telegram-dropbear-context-rca-workorder` | Telegram Dropbear Context Engineering RCA Work Order | Observed run: /home/roko/Documents/Projects/Adjacent/telegramtest/.omnius, run id 1782873796963-i5r7mv. |
 | `guide.work-orders-wo-am-gaps-uppercase` | Associative Memory Gap Work Orders | Generated: 2026-04-13 Source: Deep audit of multimodal associative memory systems Status: READY FOR IMPLEMENTATION |

package/docs/work-orders/runtime-health-remediation/LIVE-TELEGRAM-LOG-REVIEW-2026-09-05.md

@@ -0,0 +1,58 @@
+# Telegram field review after publication — September 5, 2026
+
+Scope: read-only review requested after the user observed improvement. Runtime package is **1.0.697**. The launcher started at 01:05 PDT; its current runtime child and Telegram poll owner is PID 4160370, started at 13:33 PDT. Two processes are the launcher/child relationship, not evidence of competing pollers.
+
+Sources are under the sibling `telegram_test/.omnius/`. Selected records were copied and hashed before analysis; capture directories are `/tmp/omnius-latest-completion-audit-oeh__cit`, `/tmp/omnius-telegram-delivery-audit-20260905-2045`, and `/tmp/omnius-field-context-w8e603c3`. Timestamps below are PDT (UTC−07:00). This review does not send inference or Telegram requests or change the running workspace.
+
+## Confirmed improvement
+
+The assessment run `telegram-64ac9937dc7647a8-1788640550740-1` executed from 13:35:50 to 13:41:07: 17 turns, 25 tool calls, about 316 seconds. Its task was to identify remaining work and validation for boutique-agent-services. Its completed status applies to that assessment; the project itself remains unfinished.
+
+At **13:41:08.452**, Telegram received a concrete 1,494-character final answer with six remaining integration gaps and ordered next actions. It did not contain the previous opaque completion fallback or internal router rationale. The reported checks have supporting tool output: TypeScript exited zero and Vitest reported **21/21 passing**, exit zero. No project mutations were recorded for the assessment.
+
+Evidence:
+
+- `telegram-conversations/64ac9937dc7647a833ca.events.jsonl:1510`: final message 2767.
+- `telegram-intake/98fe41d25e55150bca68.jsonl:836`: assessment consumed because the reply was delivered.
+- `terminal-trajectories/telegram-64ac9937dc7647a8-1788640550740-1.json:8`: run outcome and scope.
+- Captured debug records `2026-09-05T20-39-34-017Z-shell-d1e40f17f3.json:21` and `2026-09-05T20-39-35-953Z-shell-686a982eff.json:21`: actual check output.
+
+## Liveness, routing and context
+
+Both recent requests moved from deferred to dispatched in about 352–353 ms. Routing/admission still took approximately 37–38 seconds before each execution began. The assessment used one strict routing retry and subsequently delivered its answer. The selected records do not identify the first retry's cause.
+
+Twelve draft updates were accepted across the assessment and its continuation by the sampled delivery window, with no recorded rejection, rate limit or ambiguity. A draft-only delivery ledger remaining pending is expected; terminal state requires a final, fallback or receipt. The poll health snapshot had zero consecutive poll failures and one pending update corresponding to active work.
+
+Continuous typing cannot be established from these records: they do not log every typing pulse. Current stdout/stderr point to `/dev/pts/3`; the ordinary `.omnius/logs` files are stale and must not be treated as current transport evidence.
+
+The continuation `telegram-64ac9937dc7647a8-1788640948905-1` began at **13:42:28**. By the final **13:48:02** snapshot it retained the boutique-agent-services wiring objective, acknowledged 14 file reads and updated four relevant todos, marking discovery done and implementation in progress at 13:46:46. No source mutation, completed verification, ambiguous effect or terminal result was observed yet. Five completed main calls took 23–82 seconds each; the current call had been pending 59 seconds at capture, which does not establish a stall.
+
+All **22 sampled main requests** were admitted: roughly 9,752–33,023 input tokens against 262,144 capacity, with at least 79.3% free capacity. The latest prompt dropped from 31,729 to 16,784 input tokens through canonical supersession of 20 messages, preserving current task continuity. No memory-compilation stage or capacity-driven compaction was exercised. Latest admission and todo evidence are in `context-window-dumps/2026-09-05T20-47-03-254Z-main-d47c4be5a1.json:87` and `:1265`.
+
+The native `feature_workflow` was **not selected**: no workflow store, workflow tool call or protected workflow-owner context appeared in the captured records. This review establishes ordinary task continuity under the observed load, not live acceptance of native long-horizon workflow recovery or compaction.
+
+## Remaining findings
+
+### F1 — P2: source reads are falsely classified as runtime failures
+
+Two successful `cat` commands returned native transcript `status: success`, `exit_code: 0`, no stderr and no mutations, but the runner changed the result to `Runtime exception: throw new Error`. The phrase was source code being read.
+
+Root: `packages/orchestrator/src/agenticRunner.ts:32094` applies semantic stdout failure detection to successful shell output; the detector at line 15911 treats a literal `throw new Error` as an exception without a command-role or typed-process-receipt boundary. The contradiction survives in `context-window-dumps/2026-09-05T20-37-42-904Z-main-06ca92faa6.json:915` and `:942`. Raw typed receipts were not retained for this conversation run, so the field conclusion relies on its native transcript and non-mutation records.
+
+Required repair: preserve successful observation commands using host-owned command/receipt classification. Keep actual nonzero exits, timeouts and declared verification failures authoritative. Regressions should execute source-reading commands whose output contains exception/build/test-failure literals and confirm they remain observations, alongside real failing-command controls.
+
+### F2 — P2: malformed diagnostic arguments escape validation and crash
+
+The model supplied `steps` as a JSON-encoded string. `DiagnosticTool` casts it to `string[]` at `packages/execution/src/tools/diagnostic.ts:53`, then calls `.filter` at line 60. It has no executable input schema or value-level validator, so the runner's required-field-only fallback admits the value. The recorded error is `requestedSteps.filter is not a function` in captured debug record `2026-09-05T20-38-27-750Z-diagnostic-537aa683ec.json:22`.
+
+Required repair: introduce an executable input contract and validate direct invocation too; return an actionable argument error before executing anything. Test string/null/object steps, invalid members, valid subsets and explicit unavailable checks. This run recovered by executing TypeScript and Vitest directly.
+
+### F3 — coverage limitation: conversation checks do not populate the terminal evidence ledger
+
+The new bound terminal report exists in `completion-finalizations/telegram-64ac9937dc7647a8-1788640550740-1.json:83`, but its structured changes/checks/observations are empty and it explicitly reports the absent evidence snapshot. Telegram's chat profile selects conversation interaction mode; `writesUserTaskArtifacts()` at `agenticRunner.ts:6719` and startup at line 24954 leave that mode's completion ledger null.
+
+This is a reporting-coverage limitation, not evidence of a failed persistence write or missing delivered answer in this run. The accepted model final was delivered. The action continuation has an open ledger with actual command evidence. A follow-up design should retain observational command receipts for conversation reports without granting task/mutation authority or manufacturing verification claims.
+
+## Assessment
+
+No hard blocker was established in the sampled records. Useful final delivery, prompt continuity and queue dispatch improved; two tool defects caused avoidable failures but recovered. The implementation continuation remains active and must not be reported as completed. F1–F3 are findings from this review, not repaired or live-validated claims. Native workflow behavior and continuous typing still require the corresponding field evidence.

package/docs/work-orders/runtime-health-remediation/TRACKER.md

@@ -4,6 +4,19 @@
 **Checked-item rule:** code, focused tests, and named evidence must all exist
 **Last reconciled:** 2026-09-05
 
+## September 5 post-publication field review
+
+[Runtime 1.0.697 field review](LIVE-TELEGRAM-LOG-REVIEW-2026-09-05.md): a useful assessment final was delivered at 13:41 PDT, supported by TypeScript and 21 passing tests. At the reviewed checkpoint, the next implementation run was active. No hard blocker was established; source-read false failures, malformed diagnostic input handling and conversation-mode report coverage triggered the repairs below. Native feature workflow selection and continuous typing are not established by this sample.
+
+The user authorized end-to-end repair of the remaining defects; repository work is now complete:
+
+- [x] [WO-46: shell result authority](WO-46-shell-result-authority.md).
+- [x] [WO-47: diagnostic execution contract](WO-47-diagnostic-execution-contract.md).
+- [x] [WO-48: conversation result evidence](WO-48-conversation-result-evidence.md).
+
+Repairs `a3c26eca` (shell authority), `d4c37489` (validated asynchronous diagnostics), and `672bef53` (durable conversation evidence and terminal reporting) are delivered to `origin/main`. Clean workspace build passed. Execution: 1,820 passed / 3 existing skips; CLI: 2,575 passed. Orchestrator: 2,847 passed / 1 existing skip in the full run, with its sole outdated receipt fixture corrected and all 10 tests in that suite passing on rerun. All 7,243 distinct non-skipped affected-package tests have a passing result on the final implementation; the workorders retain exact commands, initial failures, limits and evidence paths. Publication and live acceptance remain with the user.
+
+
 ## September 5 terminal result and long-horizon follow-up
 
 Current terminal repair authority: [WO-44](WO-44-evidence-backed-terminal-results.md).

package/docs/work-orders/runtime-health-remediation/WO-46-shell-result-authority.md

@@ -0,0 +1,42 @@
+# WO-46: Preserve process authority for shell observations
+
+Status: repository repair complete and delivered to `origin/main`. Publication and live validation remain with the user.
+
+## Finding and root repair
+
+Field review F1 recorded successful source reads changed into failures because source text contained `throw new Error`. The runner's semantic stdout scanner and ShellTool's own soft-failure scanner both infer process failure from arbitrary output. A controlled reproduction also finds a false failure after `cd . && cat` prints a documented error line.
+
+Preserve observed command/process outcomes through both execution loops. Reconcile actual nonzero exits, timeout, primary-command failures and properly bound verifier protocol results before workflow settlement. Source or documentation reads must not manufacture runtime or verification failures from their bytes. Share existing command semantics where needed to bind explicit verifier output; retain existing import compatibility.
+
+## Owned paths
+
+- `packages/orchestrator/src/agenticRunner.ts`: shared tool result reconciliation and removal of generic semantic failure authority.
+- `packages/execution/src/tools/shell.ts`: process/result producer and explicit verifier binding.
+- Existing command-classification modules and compatibility exports, if required for one shared interpretation.
+- Shell and actual-runner regression tests for both loops.
+
+## Acceptance
+
+- [x] Successful source reads containing exception, compiler, test and verifier-marker literals remain successful observations.
+- [x] Real nonzero, timeout, masked pipeline primary failures and bound explicit verification failures remain failed.
+- [x] Both production loops and workflow settlement observe the same typed result.
+- [x] No source output is promoted into verification authority; existing task/shell regressions pass.
+- [x] Record full package verification, scoped commit and push.
+
+## Verification evidence
+
+- 192 focused orchestrator tests passed, including both execution loops, actual ShellTool reads and verifier controls. Log: `/tmp/omnius-wo46-focused-final.log`.
+- 63 focused execution tests passed; the complete execution package then passed 1,820 tests with 3 pre-existing skips across 163 suites. Log: `/tmp/omnius-remedies-execution-full.log`.
+- Execution build, orchestrator typecheck and whitespace checks passed.
+- Terminal-report handling of accepted negative searches and preview exits is completed with WO48, using the same command classification. Publication/live validation remain pending with the user.
+
+## Repository acceptance and delivery
+
+- Source repair: `a3c26eca`, delivered to `origin/main`; coordinated changes: `672bef53 (terminal observation/report integration)`.
+- Clean rebuild of all workspace packages and final orchestrator rebuild passed.
+- Execution: 1,820 passed / 3 existing skips across 163 suites.
+- CLI: 2,575 passed across 274 suites. Rerun with `--maxWorkers=4 --minWorkers=1` cleared the original five UI import timeouts without changing those tests or their limits.
+- Orchestrator: full run covered 228 suites with 2,847 passed / 1 existing skip / 1 outdated fixture failure. The fixture lacked required `pipefail`; it was corrected, and all 10 tests in that suite then passed. No production source changed after the full run began. This is full-suite coverage plus the corrected suite rerun, not a claim that the initial command exited successfully.
+- Across these packages, all 7,243 distinct non-skipped tests have a passing result on the final implementation. Logs: `/tmp/omnius-remedies-execution-full.log`, `/tmp/omnius-remedies-orchestrator-full.log`, `/tmp/omnius-remedies-receipt-fixture.log`, `/tmp/omnius-remedies-cli-final.log`.
+
+Checks used hermetic backend/Telegram transport and synthetic local process/project fixtures. No live inference, service restart, installed-package replacement, Telegram sends or publication were performed. The existing publish staging and unrelated discovery changes were preserved.

package/docs/work-orders/runtime-health-remediation/WO-47-diagnostic-execution-contract.md

@@ -0,0 +1,54 @@
+# WO-47: Validate and execute diagnostics without blocking the agent
+
+Status: repository repair complete and delivered to `origin/main`. Publication and live validation remain with the user.
+
+## Finding and root repair
+
+Field review F2 recorded `requestedSteps.filter is not a function`: a JSON-encoded string reached an unchecked array cast. Review also found silently omitted requested checks, successful 0/0 results, implicit package downloads, and synchronous subprocess calls that can block typing and Stop for two minutes per step.
+
+Use an executable input contract at runner admission and direct invocation. Validate requested steps and project paths before launching anything. Report unavailable requested checks and empty detection explicitly. Use configured local commands through the existing asynchronous process runner, with bounded output, timeout and cancellation of the owning process group. Preserve actual per-step outcomes in typed command receipts; never invent an aggregate successful command.
+
+## Owned paths
+
+- `packages/execution/src/tools/diagnostic.ts` and diagnostic tests.
+- `packages/execution/src/types.ts`: optional array of actual command receipts.
+- Runner and CLI adapter receipt propagation, coordinated with WO-48.
+
+## Acceptance
+
+- [x] String/null/object/invalid/empty steps and invalid path/fix arguments are rejected before execution, with actionable errors.
+- [x] Valid subsets execute exactly; explicit unavailable checks and zero detected checks cannot report success.
+- [x] No implicit dependency download or empty-test override; actual exit failures remain visible regardless of stdout.
+- [x] Event-loop responsiveness, bounded timeout, Stop, descendant cleanup and sibling isolation are exercised with local fixtures.
+- [x] Actual per-step receipts survive adapter, runner evidence recording and terminal reporting, including mixed outcomes.
+- [x] Record full package verification, scoped commit and push.
+
+## Implemented behavior and focused verification
+
+`DiagnosticTool.validateInput` and direct `execute` share the same value-level guard. The production CLI regression reproduces the field's JSON-string `steps` through the real adapter and runner: validation rejects it before the tool body or a process executes. Unsupported or unavailable explicit checks reject the whole request before dispatch. Default detection requires at least one available command.
+
+Configured package scripts run through `npm run <step>` with argument arrays; fallback runners must already exist in a local `node_modules/.bin` directory. The tool no longer launches `npx` or adds Jest's `--passWithNoTests`. Local ESLint and Biome receive their respective `--fix` and `--write` flags. Commands execute using `runProcessBuffer` with a copied environment, bounded capture, a per-command timeout, and private process-group cancellation on Unix. Stop drains the owning invocation and prevents later steps; another tool instance remains independent. Build, lint fixes and package scripts retain external-effect authority.
+
+`ToolResult.executionReceipts` carries one actual command receipt per attempted step. Completed processes retain their actual exit status. Timeout, cancellation and incomplete capture use null effective/primary status, preserving any raw zero exit in `runnerExitCode`; a cancelled process cannot become verification success merely by handling TERM with `exit(0)`. Earlier completed checks remain separately attributable when a later check fails. No aggregate successful command is invented.
+
+Focused verification (2026-09-05, synthetic processes and temporary projects only):
+
+- `packages/execution/tests/diagnostic.test.ts`: 35 passing tests.
+- Existing `packages/execution/tests/process-async.test.ts`: 1 passing descendant-cancellation test.
+- `packages/cli/tests/diagnostic-boundary.test.ts`: 3 passing production-boundary tests, including exact two-command terminal reports with exit pairs `[0, 0]` and `[0, 7]`.
+- Execution typecheck passed. Logs: `/tmp/omnius-wo47-diagnostic-tests.log`, `/tmp/omnius-wo47-cli-boundary-tests.log`, `/tmp/omnius-wo47-execution-types.log`.
+
+These receipts prove the observed process outcomes, not the completeness of a project's test suite. Configured package scripts remain project-owned commands and may themselves perform network access or modify files; the diagnostic tool does not invent a sandbox or infer an exact changed-file list. Unix descendant ownership is covered on the current host. Publication and live validation remain outside this workorder's repair execution.
+
+The complete execution package passed 1,820 tests with 3 pre-existing skips across 163 suites (`/tmp/omnius-remedies-execution-full.log`). The production CLI boundary tests and receipt consumer ship with WO48 so that each source commit has its dependencies.
+
+## Repository acceptance and delivery
+
+- Source repair: `d4c37489`, delivered to `origin/main`; coordinated changes: `672bef53 (CLI adapter and report integration)`.
+- Clean rebuild of all workspace packages and final orchestrator rebuild passed.
+- Execution: 1,820 passed / 3 existing skips across 163 suites.
+- CLI: 2,575 passed across 274 suites. Rerun with `--maxWorkers=4 --minWorkers=1` cleared the original five UI import timeouts without changing those tests or their limits.
+- Orchestrator: full run covered 228 suites with 2,847 passed / 1 existing skip / 1 outdated fixture failure. The fixture lacked required `pipefail`; it was corrected, and all 10 tests in that suite then passed. No production source changed after the full run began. This is full-suite coverage plus the corrected suite rerun, not a claim that the initial command exited successfully.
+- Across these packages, all 7,243 distinct non-skipped tests have a passing result on the final implementation. Logs: `/tmp/omnius-remedies-execution-full.log`, `/tmp/omnius-remedies-orchestrator-full.log`, `/tmp/omnius-remedies-receipt-fixture.log`, `/tmp/omnius-remedies-cli-final.log`.
+
+Checks used hermetic backend/Telegram transport and synthetic local process/project fixtures. No live inference, service restart, installed-package replacement, Telegram sends or publication were performed. The existing publish staging and unrelated discovery changes were preserved.

package/docs/work-orders/runtime-health-remediation/WO-48-conversation-result-evidence.md

@@ -0,0 +1,63 @@
+# WO-48: Retain command evidence in conversation results
+
+Status: repository repair complete and delivered to `origin/main`. Publication and live validation remain with the user.
+
+## Finding and root repair
+
+Field review F3 found an accepted conversation final with actual check output but an empty structured terminal report. Conversation mode intentionally disables the task ledger; the shared result producer therefore discards evidence before reporting.
+
+Maintain report-only evidence for the exact conversation run and task epoch, reusing existing evidence types and immutable artifact storage. Preserve accepted process facts and observations independently of the task ledger. Persist the report snapshot before terminal delivery. Task claims, todos, workboards, mission artifacts and completion requirements must remain governed by their existing authority; enabling reporting cannot grant task or mutation permissions.
+
+## Owned paths
+
+- `packages/orchestrator/src/agenticRunner.ts`: evidence producer, run/epoch initialization and terminal commit.
+- `packages/orchestrator/src/conversationReportEvidence.ts` and production-runner/recovery tests.
+- `packages/orchestrator/src/commandEvidenceReceipt.ts`: shared strict receipt parser before nested field access or recovery.
+- `packages/cli/src/tui/tool-adapter.ts`: multiple command receipt preservation.
+- `packages/orchestrator/src/terminalTaskReport.ts`: typed visible limits and successful observation outcomes.
+- Actual mocked Telegram conversation/final-selection tests and adapter tests.
+
+## Acceptance
+
+- [x] Actual conversation-mode execution retains typed command and observation evidence in both loops.
+- [x] Actual Telegram chat route delivers a useful report when no separately authored final exists, including failed checks.
+- [x] Task ledger/claims/todos/mission state remain absent; reporting does not change completion authority or tool permissions.
+- [x] New runs, epoch replacement, stale callbacks and scope mismatch cannot inherit earlier report evidence.
+- [x] Immutable persistence/recovery retains exact scoped evidence or reports an explicit gap; no fabricated restored facts.
+- [x] Multi-step diagnostic outcomes are recorded individually, preserving earlier passes and later failure/cancellation.
+- [x] Record full package verification, scoped commit and push.
+
+## Integration design and additional defects found
+
+Conversation reporting retains successful reads/searches and typed command outcomes without creating the task completion ledger. Report facts never enter task admission, claim reconciliation or completion readiness. An assessment can complete while truthfully reporting a failed project check. Run and epoch initialization clear earlier evidence, and each tool dispatch captures its report identity before any await so late callbacks cannot populate a replacement report.
+
+Multi-command results retain separate process outcomes. The aggregate keeps its own mutation/delivery success; an earlier passing child command cannot make a failed aggregate delivery or mutation successful. The CLI adapter carries every receipt through direct and streaming execution.
+
+Actual Telegram regressions exposed a second presentation path: verification-audit gap prose included the tool's raw stdout summary. The terminal report now derives visible gap details from typed commands, paths and stable gap categories. Raw evidence remains inspectable. Successful negative searches and normalized read-preview SIGPIPE outcomes are observations with their original exits retained, rather than invented failures or verification passes.
+
+Recovery storage uses immutable linked chunks plus a scoped selector, rather than rewriting the entire evidence history after every tool. Only new evidence is stored, avoiding quadratic use of the shared artifact-store quota on long runs. Recovery validates scope, ordering, identities, receipt shape and integrity before reconstructing report-only facts; it cannot deserialize task authority. Missing or rejected evidence becomes an explicit report limit. Final delivery requires the current evidence to be durably persisted.
+
+## Focused verification
+
+- 16 production-runner cases passed, covering both loops; mixed pass/failure/timeout; no task authority; new-run isolation; stale callbacks after epoch replacement; read/search observations; separate aggregate effects; malformed receipt fields with valid siblings; repeated identical attempts; and exact interrupted recovery or an explicit gap without replaying checks. Log: `/tmp/omnius-wo48-runner.log`.
+- 49 helper cases passed, including 100 receipts under a 256 KiB storage budget, immutable old-head recovery, malformed scope/receipt/task-authority rejection, corruption and missing ancestors, count/byte/cycle limits, and publication fault points. The three recovery-limit cases additionally prove that rejected count/byte bounds prevent CAS body reads. Logs: `/tmp/omnius-wo48-report-evidence-helper-tests.log`, `/tmp/omnius-wo48-report-recovery-limits-tests.log`.
+- 36 terminal report tests passed. Log: `/tmp/omnius-wo48-terminal-report.log`.
+- Six actual Telegram conversation cases, three adapter paths and three actual diagnostic-to-runner cases passed in the complete CLI suite. Final CLI: 2,575 passing tests across 274 suites with four workers; original unlimited concurrency hit five existing UI import timeouts. Log: `/tmp/omnius-remedies-cli-final.log`.
+- Clean all-workspace build and final orchestrator rebuild passed. Logs: `/tmp/omnius-remedies-clean-build.log`, `/tmp/omnius-remedies-orchestrator-final-build.log`.
+
+The strict receipt parser also exposed an older valid-verification mock missing required `pipefail`; the fixture now supplies the actual contract field, and all ten observed-authority cases pass without weakening readiness assertions (`/tmp/omnius-remedies-receipt-fixture.log`).
+
+The review additionally reproduced invalid nested receipt fields throwing before validation, and an incomplete aggregate disappearing behind its passed prerequisite. The recorder now validates before nested field access, preserves unverified evidence and valid siblings, and records the aggregate failure separately. Separate identical array receipts remain distinct executions; only a legacy singleton alias is deduplicated.
+
+Recovery is bounded by configured CAS and host recovery limits; it is not unlimited retention or a filesystem-effect transaction. An interruption before a tool observation is published still uses the existing interruption reconciliation. Publication and live validation remain with the user.
+
+## Repository acceptance and delivery
+
+- Source repair: `672bef53`, delivered to `origin/main`; coordinated changes: `a3c26eca and d4c37489 (shared command semantics and diagnostic receipts)`.
+- Clean rebuild of all workspace packages and final orchestrator rebuild passed.
+- Execution: 1,820 passed / 3 existing skips across 163 suites.
+- CLI: 2,575 passed across 274 suites. Rerun with `--maxWorkers=4 --minWorkers=1` cleared the original five UI import timeouts without changing those tests or their limits.
+- Orchestrator: full run covered 228 suites with 2,847 passed / 1 existing skip / 1 outdated fixture failure. The fixture lacked required `pipefail`; it was corrected, and all 10 tests in that suite then passed. No production source changed after the full run began. This is full-suite coverage plus the corrected suite rerun, not a claim that the initial command exited successfully.
+- Across these packages, all 7,243 distinct non-skipped tests have a passing result on the final implementation. Logs: `/tmp/omnius-remedies-execution-full.log`, `/tmp/omnius-remedies-orchestrator-full.log`, `/tmp/omnius-remedies-receipt-fixture.log`, `/tmp/omnius-remedies-cli-final.log`.
+
+Checks used hermetic backend/Telegram transport and synthetic local process/project fixtures. No live inference, service restart, installed-package replacement, Telegram sends or publication were performed. The existing publish staging and unrelated discovery changes were preserved.

package/npm-shrinkwrap.json

@@ -1,12 +1,12 @@
 {
   "name": "omnius",
-  "version": "1.0.697",
+  "version": "1.0.698",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "omnius",
-      "version": "1.0.697",
+      "version": "1.0.698",
       "bundleDependencies": [
         "image-to-ascii"
       ],

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "omnius",
-  "version": "1.0.697",
+  "version": "1.0.698",
   "description": "AI coding agent powered by open-source models (Ollama/vLLM) — interactive TUI with agentic tool-calling loop",
   "type": "module",
   "main": "./dist/library.js",