omnius 1.0.696 → 1.0.697

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

@@ -4,6 +4,31 @@
 **Checked-item rule:** code, focused tests, and named evidence must all exist
 **Last reconciled:** 2026-09-05
 
+## September 5 terminal result and long-horizon follow-up
+
+Current terminal repair authority: [WO-44](WO-44-evidence-backed-terminal-results.md).
+
+- [x] Evidence-backed terminal report survives automatic completion and reaches Telegram.
+- [x] Genuine final answers retain source, task and receipt ownership.
+- [x] AIWG research-team mechanisms mapped into existing execution and recovery primitives.
+- [x] Native long-horizon feature implementation and 12-scenario acceptance: [workflow WO-01](../long-horizon-feature-delivery/WO-01-native-research-feature-workflow.md).
+- [x] Native Ollama tool request and response parity: [WO-45](WO-45-native-ollama-tool-contract.md).
+- [x] WO-44 regression verification, review and scoped Git delivery recorded.
+
+WO-44 repository acceptance: repair 691532df delivered to origin/main; orchestrator 2,650 passed / 1 skipped across 218 suites; CLI 2,550 passed across 269 suites; both package builds passed.
+
+Native feature workflow WO-01 and native Ollama transport WO-45 are complete in source commits 3c71f668 and 26d4cbed, delivered to origin/main. Final acceptance: 7,310 passed / 4 skipped across 671 suites in schemas, execution, orchestrator and CLI; clean workspace build and final workspace rebuild passed. The workflow workorder maps all twelve required scenarios to concrete assertions, including actual parent compaction in both loops and child Stop propagation. Publication and live acceptance remain with the user.
+
+## September 5 post-publication Telegram progress follow-up
+
+Current authority: [WO-43](WO-43-telegram-router-progress-boundary.md).
+
+- [x] Remove router failure prose from request-comprehension progress.
+- [x] Repair confirmed routing contract/correlation defects.
+- [x] Verify typing and delivery regressions, record review, build and scoped delivery.
+
+WO-43 repository acceptance: repair 3f3c37f1 delivered to origin/main; all 2,531 CLI tests passed across 268 suites; clean CLI rebuild passed. Publication and live acceptance remain with the user.
+
 ## September 5 tool-quality and live-behavior follow-up
 
 Current follow-up authority: [TOOL-QUALITY-2026-09-05.md](TOOL-QUALITY-2026-09-05.md).

package/docs/work-orders/runtime-health-remediation/WO-43-telegram-router-progress-boundary.md

@@ -0,0 +1,71 @@
+# 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
+
+## User-visible failure
+
+The initial Telegram card displays Working / Understanding followed by internal typed-router failure, retry and admin-admission diagnostics. The user reports seeing this first on every interaction. This is generated by the host rather than an assistant-authored explanation.
+
+Read-only process inspection confirms the active Telegram workspace is using installed Omnius 1.0.696. No installed files or running services were changed.
+
+## Root cause and code locations
+
+The router's diagnostic reason is copied into subAgent.intakeComprehension when no explicit expected-outcome reason exists. The admin panel then renders that field as Understanding and publishes it during initial startup status handling.
+
+- [telegram-bridge.ts](../../../packages/cli/src/tui/telegram-bridge.ts): processTelegramMessageWork, buildTelegramRouterUnavailableDecision, ensureTelegramAdminLivePanel, renderTelegramAdminWorkingSummary.
+- [telegram-admin-live-panel.test.ts](../../../packages/cli/tests/telegram-admin-live-panel.test.ts) and [telegram-bot-api-10.test.ts](../../../packages/cli/tests/telegram-bot-api-10.test.ts): existing summary and router tests lack this production failure-to-progress boundary.
+- [telegram-working-indicator.test.ts](../../../packages/cli/tests/telegram-working-indicator.test.ts): ongoing three-second typing ownership must remain intact.
+
+An earlier persisted decision at 00:58 PDT on September 5 records router JSON admission rejected with logical_request_conflict, followed by a plain response and a strict retry rejected with direct_turn_conflicts_with_reply_target. Read-only source analysis reproduced the matching defects:
+
+- Generated broker request identity hashes only sessionKey plus an instance-local inf-N counter. Restarting the bridge resets the counter, so the same session and inference kind can reuse an old broker identity for different request content. A per-bridge cryptographic nonce must separate lifetimes while each admitted logical request retains its identity across transport retries.
+- The host evidence packet correctly marks private messages as directDeliveryToSelf. However, both the validator and routing prompt reject a direct turn when its reply edge targets another actor, without a private-delivery exception. An operator replying to their own earlier message in a DM is still speaking directly to the bot. The repair must honor that host-owned transport fact while preserving group reply-target checks and explicit self/evidence requirements.
+
+The historical receipt establishes concrete matching failure mechanisms, not a claim that every reported failure had the same cause. The latest running process is 1.0.696; no live inference was sent to reproduce it.
+
+## Repair plan and acceptance
+
+- [x] Trace the reported string to its exact construction and delivery path.
+- [x] Initialize request comprehension only from validated expected-outcome comprehension, never from routing reasons.
+- [x] Keep internal reasons and detailed failure receipts available in diagnostics; ordinary progress remains useful and plain.
+- [x] Cover unavailable and valid routers without outcome summaries, plus genuine outcome-summary display.
+- [x] Reproduce and resolve confirmed request-correlation or reply-evidence contradictions without weakening typed reply authorization.
+- [x] Preserve background typing, native draft lifecycle, cancellation and final delivery.
+- [x] Complete independent review, affected tests, build and scoped commit/push to origin/main.
+
+## Implementation and review
+
+Routing reasons remain in TUI and durable social decision diagnostics. The initial Telegram response panel uses only comprehension from a validated, identity-bound expected-outcome contract. Otherwise its existing Working / Intake / Accepted presentation remains available. Native drafts and the independently owned typing heartbeat retain their lifecycle.
+
+Generated inference identities include a cryptographic namespace for the bridge lifetime. Transport retries preserve the identity of the same request; a newly constructed bridge cannot reuse the previous bridge's inf-N identity in the same session.
+
+Both initial and recovery prompts distinguish private transport delivery from group reply edges. The validator accepts private current-message evidence for direct delivery, while retaining self-role, addressed-actor and citation validation. Group replies aimed at someone else still require the appropriate authorization basis.
+
+Independent review also found that failed normalization or rebinding could preserve a raw expected-outcome contract and stale matching decision IDs. This was found in synthetic boundary tests, not established as the live router failure. Invalid contracts are now cleared after safe effect augmentation/normalization, and failed trusted rebinding removes both the rejected contract and its stale decision ID. Presentation independently requires matching input and decision receipts. Existing implied visible-response effects are preserved.
+
+## Runtime and publication boundary
+
+Tests use temporary fixtures, mocked inference and mocked Telegram transport. No live inference, Telegram messages, GPU workloads, service restart or package publication is authorized by this repair. Existing publication staging and unrelated discovery changes are preserved. The user owns publication and subsequent live validation.
+
+## Verification and delivery
+
+- Baseline reproductions fail with the exact synthetic broker 409 identity conflict and with direct-turn conflicts for private replies to two different author identities. The initial recovery fixture had a separate mock setup error; it was corrected before final verification. No live request was involved.
+- Presentation: 35 tests passed across the new seven-case production intake presentation suite, admin live panel and working indicator; four selected Bot API regressions also passed. The tests assert actual mocked first-message payloads, retained TUI/durable diagnostics, nine seconds of typing refresh, final response and cleanup.
+- Routing: 29 tests passed across the ten new identity/private-reply cases, attention evidence and inference contracts. Coverage includes fresh bridge identity, stable queue retries, group rejection controls, strict recovery, malformed outcomes and stale outcome rebinding.
+- Independent review resolved the stale receipt counterexample and confirmed group authorization, supplied logical IDs, unary request variants and typing/native draft ownership remain intact. Parent review confirmed safe array-shape handling preserves the existing implied visible-response effect before final normalization.
+- CLI clean rebuild passed. The complete CLI suite passed all **2,531 tests across 268 suites**, with zero failures or skipped tests. This includes Telegram intake/typing/delivery and the daemon frontend transport regression suites.
+
+Local reproduction and focused logs: /tmp/omnius-telegram-router-roots-before.log and /tmp/omnius-telegram-router-roots-after.log. Final logs: /tmp/omnius-wo43-cli-build.log and /tmp/omnius-wo43-cli-verified.log.
+
+Scoped repair commit: **3f3c37f1**, delivered to **origin/main** with this workorder closure. The installed package and publication staging remain untouched; live acceptance follows the user's publication.
+
+Regression source: [telegram-intake-presentation.test.ts](../../../packages/cli/tests/telegram-intake-presentation.test.ts) and [telegram-router-identity-and-private-replies.test.ts](../../../packages/cli/tests/telegram-router-identity-and-private-replies.test.ts).
+
+## Field acceptance after user publication
+
+Start a DM task without an explicit outcome summary: the initial card may show Working / Intake / Accepted, but no routing reason or failure prose. Reply to an earlier own message and confirm direct delivery is accepted. Typing continues throughout silent work, and genuine task summaries can replace initial intake. Restart the bridge and confirm its next inference is admitted without a reused logical-request conflict. Group replies to other actors retain their normal authorization checks.
+
+These field checks remain pending user publication; repository tests use mocked transport.

package/docs/work-orders/runtime-health-remediation/WO-44-evidence-backed-terminal-results.md

@@ -0,0 +1,56 @@
+# 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 telegram_test; read-only inspection
+
+## Reported failure
+
+After applying the operator's continuation of boutique-agent-services, Telegram ended with: “The run reached its completion boundary, but it did not produce a user-facing result. Open Evidence for the recorded outcome.”
+
+Run telegram-64ac9937dc7647a8-1788624121778-1 finalized at 09:27:18 PDT on September 5 with status completed, disposition ready, and task epoch 1. Its host summary records four changed files (payment.ts, solana.ts, signature.ts and boutique.test.ts) and a successful post-mutation TypeScript check. The preceding tool output reports 21 passing tests; its piped shell receipt is classified as observation, so it must not be silently upgraded into typed verifier authority.
+
+## Confirmed root causes
+
+- Truth-based automatic completion emits assistant_text with source task_complete_summary and finishes without a separately authored user_reply. Telegram intentionally discards untyped runner summaries to avoid exposing bookkeeping. No structured result crosses that gap.
+- A typed model_visible_text answer delivered without stream events can also be lost: the retention helper considers stream/accumulated content, and completion then excludes uncommitted assistant text.
+- Auxiliary handoff grounding occurs after terminal commit and writes memory handoff state; its advisory outcome is not a user-facing terminal result.
+- Finalization's selected command evidence excludes failed observations, while testsRun is attempted-command metadata. Neither can independently establish a complete, truthful check report.
+
+## Code and contracts
+
+- [completionAutoFinalize.ts](../../../packages/orchestrator/src/completionAutoFinalize.ts): implicit completion from direct file and validation evidence.
+- [agenticRunner.ts](../../../packages/orchestrator/src/agenticRunner.ts): terminal commit, emitted events, AgenticResult and auxiliary handoff.
+- [completionFinalization.ts](../../../packages/orchestrator/src/completionFinalization.ts): immutable terminal receipt and selected projections.
+- [telegram-bridge.ts](../../../packages/cli/src/tui/telegram-bridge.ts): selectTelegramFinalResponse, runSubAgent, task_complete adapter and all final delivery paths.
+
+## Accepted design and work plan
+
+- [x] Reconstruct the reported terminal path from live receipts and source.
+- [x] Build a bounded host-owned terminal report from current-epoch typed ledger evidence at commit, bound to run, epoch and terminal receipt.
+- [x] Preserve actual file effects, check outcomes/freshness, failures and explicit gaps. Report truncation rather than implying complete coverage.
+- [x] Deliver the typed report when no accepted user-facing answer exists; retain explicit user replies and genuine non-stream model answers.
+- [x] Reject stale reports, unaccepted completion replies and arbitrary bookkeeping/old streams.
+- [x] Replace opaque final fallbacks with a useful result or a clear account of missing evidence and the next required action.
+- [x] Preserve typing, Stop, authenticated delivery, artifact receipts and inert-link validation.
+- [x] Complete production-path mocked regressions, independent review, build and scoped commit/push.
+
+Completion authority and verification audit remain separate. A generic mutation does not manufacture mandatory checks. The final result reports the evidence that exists, including uncertainty; it does not promote attempted commands or model claims to verified outcomes.
+
+## Relationship to long-horizon work
+
+The user additionally requested adaptation of AIWG's research-team mechanism for feature specification, creation, integration and testing across very long runs. Its source mechanisms and fit with existing Omnius workboard/recovery are recorded in [the research mapping](../../research/aiwg-long-horizon-feature-workflow.md), with native implementation tracked in [workflow WO-01](../long-horizon-feature-delivery/WO-01-native-research-feature-workflow.md). This terminal report provides the durable, evidence-bound handoff those longer workflows need; it does not by itself close that broader request.
+
+## Verification and delivery
+
+Implementation: 691532df, delivered to origin/main with this closure record.
+
+- Full orchestrator regression: 218 suites passed; 2,650 tests passed and one intentionally skipped with OMNIUS_SQLITE_TESTS=1.
+- Full CLI regression: 269 suites and 2,550 tests passed. An initial run found one source-regex fixture expecting the prior event guard; the expectation was updated for the stronger terminal-settled guard, its 51 focused tests passed, and the full CLI suite was rerun successfully.
+- Orchestrator and CLI builds passed; git diff --check passed. Independent review covered actual mutation attribution, typed command role and freshness, failed or missing checks, held completion replies, epoch/receipt isolation, and bounded Telegram payloads.
+- Production runner tests in accepted-terminal-reply.test.ts cover accepted replies, held attempts, terminal readiness rejection and runner reuse. terminal-task-report-runner.test.ts covers report commit and event/result identity. telegram-terminal-delivery.test.ts exercises actual mocked bridge delivery, explicit/model/report precedence, stale ownership, missing evidence and long-result truncation with full Evidence detail.
+
+The report is generated from the committed ledger without another model request. Telegram receives concrete changed paths, recorded checks, limitations and next actions; untyped piped command output is never upgraded to a verification pass.
+
+Tests use mocked inference/Telegram and temporary fixtures. No live inference, service restart, installed package replacement, external messaging or publication occurred. Existing publication staging and discovery changes remain untouched. The installed runtime remains unchanged until the user publishes.

package/docs/work-orders/runtime-health-remediation/WO-45-native-ollama-tool-contract.md

@@ -0,0 +1,33 @@
+# 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
+
+## Finding
+
+Tracing the new feature workflow schema through the actual backend found that its definitions and references survive the ordinary OpenAI-compatible and Ollama-v1 transports. The separate native Ollama unary and streaming request builders in `packages/orchestrator/src/agenticRunner.ts` omit the request's tools entirely.
+
+This is a transport contract defect for native-chat callers, not evidence that the normal v1 feature-workflow path loses its schema. A tool-capable request cannot work reliably if the adapter silently removes every tool before sending it.
+
+## Repair and acceptance
+
+- [x] Reproduce the native unary and streaming omissions with mocked HTTP responses.
+- [x] Preserve the exact advertised tools, including nested definitions and references, in both native request bodies.
+- [x] Preserve returned native tool calls and their arguments through the normalized runner response and stream lifecycle.
+- [x] Retain direct-answer/tool thinking policy, cancellation and ordinary text-only behavior.
+- [x] Run focused transport regressions, package checks and scoped Git delivery; record the implementation and verification here.
+
+The actual host runner and HTTP encoders are in scope. No live model loading, inference, service restart, installed-package replacement or publication is authorized by this verification task.
+
+## Verification and delivery — 2026-09-05
+
+Commit **26d4cbed** is delivered to **origin/main**. The repair adds the original nonempty `request.tools` to both native request bodies in `agenticRunner.ts`; existing native response decoders already preserve typed tool calls and required no change.
+
+`packages/orchestrator/tests/feature-workflow-transport.test.ts` contributes eight mocked transport cases. Exact tool schemas, including definitions and references, are compared at the actual HTTP boundary for ordinary compatible requests and native unary/streaming requests; native tool responses retain their names and arguments. The focused transport set passed **38 tests**. The final orchestrator suite passed **2,736 tests**, with **one skipped**, across **224 suites**; the clean workspace build and final workspace rebuild passed. Full cross-package acceptance is recorded in [workflow WO-01](../long-horizon-feature-delivery/WO-01-native-research-feature-workflow.md).
+
+Publication and live model compatibility testing remain with the user.
+
+## Related work
+
+Discovered while verifying production tool delivery for [native feature workflow WO-01](../long-horizon-feature-delivery/WO-01-native-research-feature-workflow.md). The preceding Telegram final-result repair is [WO-44](WO-44-evidence-backed-terminal-results.md).

package/npm-shrinkwrap.json

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

package/package.json

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