omnius 1.0.800 → 1.0.801

package/dist/index.js

@@ -1,4 +1,4 @@
 [diffend] Oversized file quarantined before diffing.
 name: package/dist/index.js
-size: 39351823 bytes
-sha256: 812b782621e8e4b7fb2af446cd38684559e1ea1fa8c79c43345605a4084e24c8
+size: 39375009 bytes
+sha256: 90e931d1af7190d874d22d66a022df4a0a1c75565942a4db236a5e7a2298cf92

package/docs/DISCOVERY.json

@@ -31168,6 +31168,41 @@
         }
       ]
     },
+    {
+      "id": "guide.research-translation-model-routing-2026-10-03",
+      "kind": "guide",
+      "title": "Translation model routing note — 2026-10-03",
+      "summary": "Do not use the 9B general Omnius model as the unconditional translation lane. Keep it as the semantic fallback for translation requests that also require reasoning, terminology negotiation, long conversational context, or tool use. Route plain, typed translation requests to a smaller translation-specific model selected by language coverage and license.",
+      "keywords": [
+        "research",
+        "translation",
+        "model",
+        "routing",
+        "2026",
+        "10",
+        "03",
+        "md"
+      ],
+      "maturity": "internal",
+      "audiences": [
+        "maintainer",
+        "large-context-agent"
+      ],
+      "layer": "documentation",
+      "interfaces": [
+        {
+          "type": "file",
+          "target": "docs/research/translation-model-routing-2026-10-03.md"
+        }
+      ],
+      "references": [
+        {
+          "type": "documentation",
+          "target": "docs/research/translation-model-routing-2026-10-03.md",
+          "relation": "canonical-artifact"
+        }
+      ]
+    },
     {
       "id": "guide.rest-auth-and-scopes",
       "kind": "guide",
@@ -35906,7 +35941,7 @@
       "id": "guide.work-orders-runtime-health-remediation-wo-57-telegram-delivery-truth-and-recovery-uppercase",
       "kind": "guide",
       "title": "WO-57: Telegram delivery truth, reminder authority, and bounded recovery",
-      "summary": "Status: 1.0.798 live acceptance failed on Case Theory message 650; REQ-TDT-018 delivery-commit convergence and complete batch-scope repair are verified and pushed; full-suite, publication, redeployment, and live-acceptance gates remain open Priority: P0 Incident: October 1, 2026, live Telegram reminder and illegal-logging non-responses Owner: Omnius orchestr",
+      "summary": "Status: REQ-TDT-019 and the REQ-TDT-016 lease correction were delivered in cdf81ffd; the 23-file Case Theory acceptance run then exposed the terminal same-response contract mismatch tracked by REQ-TDT-020. Its source repair was delivered in 1b451bc8; publication, redeployment, live acceptance, and the pre-existing full-suite debt recorded below remain open. ",
       "keywords": [
         "work",
         "orders",
@@ -35942,6 +35977,84 @@
         }
       ]
     },
+    {
+      "id": "guide.work-orders-runtime-health-remediation-wo-58-agent-scoped-footer-observability-uppercase",
+      "kind": "guide",
+      "title": "WO-58 — Agent-scoped footer observability",
+      "summary": "Status: source delivered in 8a81eab6; deployment acceptance pending",
+      "keywords": [
+        "work",
+        "orders",
+        "runtime",
+        "health",
+        "remediation",
+        "WO",
+        "58",
+        "agent",
+        "scoped",
+        "footer",
+        "observability",
+        "md"
+      ],
+      "maturity": "internal",
+      "audiences": [
+        "maintainer",
+        "large-context-agent"
+      ],
+      "layer": "documentation",
+      "interfaces": [
+        {
+          "type": "file",
+          "target": "docs/work-orders/runtime-health-remediation/WO-58-agent-scoped-footer-observability.md"
+        }
+      ],
+      "references": [
+        {
+          "type": "documentation",
+          "target": "docs/work-orders/runtime-health-remediation/WO-58-agent-scoped-footer-observability.md",
+          "relation": "canonical-artifact"
+        }
+      ]
+    },
+    {
+      "id": "guide.work-orders-runtime-health-remediation-wo-59-telegram-restart-edit-crash-uppercase",
+      "kind": "guide",
+      "title": "WO-59: Telegram restart edit crash and terminal-intake monotonicity",
+      "summary": "Status: COMPLETE — implemented, verified, and pushed in 9fadef51 Priority: P0 Incident: October 3, 2026, telegramtest TUI exits immediately while loading the OMNIUS Telegram session Owner: Omnius Telegram durable-intake runtime Depends on: WO-57 Completion rule: Mark a checkbox complete only when its code anchor and deterministic evidence exist. Do not delet",
+      "keywords": [
+        "work",
+        "orders",
+        "runtime",
+        "health",
+        "remediation",
+        "WO",
+        "59",
+        "telegram",
+        "restart",
+        "edit",
+        "crash",
+        "md"
+      ],
+      "maturity": "internal",
+      "audiences": [
+        "maintainer",
+        "large-context-agent"
+      ],
+      "layer": "documentation",
+      "interfaces": [
+        {
+          "type": "file",
+          "target": "docs/work-orders/runtime-health-remediation/WO-59-telegram-restart-edit-crash.md"
+        }
+      ],
+      "references": [
+        {
+          "type": "documentation",
+          "target": "docs/work-orders/runtime-health-remediation/WO-59-telegram-restart-edit-crash.md",
+          "relation": "canonical-artifact"
+        }
+      ]
+    },
     {
       "id": "guide.work-orders-telegram-dmn-wo-22-dmn-outreach-and-learning-uppercase",
       "kind": "guide",

package/docs/DISCOVERY.md

@@ -480,6 +480,7 @@ Daemon equivalents are `GET /v1/discovery/bootstrap`, `GET /v1/discovery?q=<inte
 | `guide.research-archived-readme-uppercase` | Archived design notes — unwired | Documents in this directory describe design proposals that were never wired into the runtime. They are kept for historical context only. |
 | `guide.research-k-splanifolds` | K Splanifolds | Bundled Omnius documentation artifact: docs/research/k-splanifolds.pdf. |
 | `guide.research-personality-verbosity-control` | LLM Personality Guidance &amp; Verbosity Control: Research Synthesis | Date: 2026-03-13 Purpose: Literature review and integration strategy for transient personality/verbosity steering in the Omnius framework |
+| `guide.research-translation-model-routing-2026-10-03` | Translation model routing note — 2026-10-03 | Do not use the 9B general Omnius model as the unconditional translation lane. Keep it as the semantic fallback for translation requests that also require reasoning, terminology negotiation, long conversational context, or tool use. Route plain, typed translation requests to a smaller translation-specific model selected by language coverage and license. |
 | `guide.rest-auth-and-scopes` | Auth And Scopes | Omnius can run without auth for local development, but shared deployments should use bearer keys. |
 | `guide.rest-endpoints-aims` | AIMS Governance Endpoints | Omnius exposes an ISO/IEC 42001-oriented AI Management System surface for audit-aligned deployments. |
 | `guide.rest-endpoints-aiwg` | AIWG Cascade Endpoints | AIWG endpoints expose a discover-then-expand documentation and workflow model for small and large context agents. |
@@ -609,7 +610,9 @@ Daemon equivalents are `GET /v1/discovery/bootstrap`, `GET /v1/discovery?q=<inte
 | `guide.work-orders-runtime-health-remediation-wo-54-case-theory-router-deferral-recovery-uppercase` | WO-54: Case Theory router deferral recovery | Status: complete Priority: P0 Incident: September 26, 2026, Case Theory messages 455–456 Runtime observed: globally installed Omnius 1.0.764 Owner: current implementation session |
 | `guide.work-orders-runtime-health-remediation-wo-55-telegram-pressure-recovery-uppercase` | WO-55: Telegram pressure recovery without silent terminal states | Status: complete Priority: P0 Incident: September 26, 2026, Case Theory messages 458-461 Owner: current implementation session |
 | `guide.work-orders-runtime-health-remediation-wo-56-evidence-driven-objective-loop-uppercase` | WO-56: Evidence-driven objective loop and nonblocking execution | Status: repository implementation complete; live Telegram acceptance remains an external gate Priority: P0 Incident: September 27, 2026, Telegram SSH-over-Cloudflare task spiral and TUI freeze Owner: Omnius orchestration, execution, and Telegram runtime Depends on: WO-05, WO-21, WO-27, WO-41, WO-44, WO-49, WO-54, WO-55 Completion rule: A checkbox may be mark |
-| `guide.work-orders-runtime-health-remediation-wo-57-telegram-delivery-truth-and-recovery-uppercase` | WO-57: Telegram delivery truth, reminder authority, and bounded recovery | Status: 1.0.798 live acceptance failed on Case Theory message 650; REQ-TDT-018 delivery-commit convergence and complete batch-scope repair are verified and pushed; full-suite, publication, redeployment, and live-acceptance gates remain open Priority: P0 Incident: October 1, 2026, live Telegram reminder and illegal-logging non-responses Owner: Omnius orchestr |
+| `guide.work-orders-runtime-health-remediation-wo-57-telegram-delivery-truth-and-recovery-uppercase` | WO-57: Telegram delivery truth, reminder authority, and bounded recovery | Status: REQ-TDT-019 and the REQ-TDT-016 lease correction were delivered in cdf81ffd; the 23-file Case Theory acceptance run then exposed the terminal same-response contract mismatch tracked by REQ-TDT-020. Its source repair was delivered in 1b451bc8; publication, redeployment, live acceptance, and the pre-existing full-suite debt recorded below remain open.  |
+| `guide.work-orders-runtime-health-remediation-wo-58-agent-scoped-footer-observability-uppercase` | WO-58 — Agent-scoped footer observability | Status: source delivered in 8a81eab6; deployment acceptance pending |
+| `guide.work-orders-runtime-health-remediation-wo-59-telegram-restart-edit-crash-uppercase` | WO-59: Telegram restart edit crash and terminal-intake monotonicity | Status: COMPLETE — implemented, verified, and pushed in 9fadef51 Priority: P0 Incident: October 3, 2026, telegramtest TUI exits immediately while loading the OMNIUS Telegram session Owner: Omnius Telegram durable-intake runtime Depends on: WO-57 Completion rule: Mark a checkbox complete only when its code anchor and deterministic evidence exist. Do not delet |
 | `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-telegram-reliability-consolidation-2026-09-28` | Telegram Reliability Consolidation — 2026-09-28 | Rule: check a box only after the named behavior is implemented and its listed verification passes. A parent box stays open until every child box is checked. |

package/docs/research/translation-model-routing-2026-10-03.md

@@ -0,0 +1,87 @@
+# Translation model routing note — 2026-10-03
+
+## Decision
+
+Do not use the 9B general Omnius model as the unconditional translation lane.
+Keep it as the semantic fallback for translation requests that also require
+reasoning, terminology negotiation, long conversational context, or tool use.
+Route plain, typed translation requests to a smaller translation-specific
+model selected by language coverage and license.
+
+Recommended evaluation order:
+
+1. **TranslateGemma 4B** for the supported 55-language set when quality is the
+   priority and the Gemma license is acceptable. Google reports that the 4B
+   translation-tuned model rivals its larger 12B Gemma baseline. It also
+   supports image-text translation and has published quantized deployment
+   paths. Its material constraint is a 2K-token input context and a strict
+   source/target-language template; it is not a drop-in conversational agent.
+2. **MADLAD-400 3B MT** as the broad, permissively licensed multilingual lane.
+   The published model card lists 419 languages, Apache-2.0 licensing, a 3B T5
+   architecture, and a 1.65 GB Q4K artifact versus 11.8 GB original weights.
+   It is the strongest first candidate when Omnius needs broad language
+   coverage under a production-compatible license.
+3. **OPUS-MT/Marian pair-specific models** for a small set of hot language
+   pairs where minimum residency and latency matter most. A representative
+   English-Maltese checkpoint is 294 MB and Apache-2.0. The tradeoff is model
+   and routing proliferation: every direction/pair needs explicit inventory,
+   health, and fallback management.
+4. **NLLB-200 distilled 600M** only for research/non-commercial evaluation or
+   an explicitly compatible use. It covers 196 listed languages at 600M
+   parameters, but its CC-BY-NC license and model-card limitations make it a
+   poor default production choice. Meta describes it as research-oriented,
+   single-sentence translation, not production/document translation, with
+   training inputs capped at 512 tokens.
+
+## Operational fit
+
+| Candidate | Best fit | Important constraint | Recommendation |
+| --- | --- | --- | --- |
+| TranslateGemma 4B | High-quality text/image translation in 55 languages | Gemma license, strict language-coded template, 2K context | Primary quality candidate |
+| MADLAD-400 3B MT | Very broad multilingual text under Apache-2.0 | General-domain research model; validate target pairs | Primary broad-production candidate |
+| OPUS-MT/Marian | Fixed high-volume language pairs | Pair/direction-specific fleet complexity | Lowest-footprint specialist lane |
+| NLLB-200 600M | Low-resource research and offline comparison | CC-BY-NC, 512-token training limit, not production/document use | Evaluation only |
+| Qwen3.5 9B Omnius lane | Mixed translation + reasoning/tools/context | Higher residency and latency; generic rather than MT-specific | Semantic fallback, not default MT |
+
+## Router contract
+
+A translation lane should be selected only when the request has a closed,
+typed contract:
+
+- source language and target language are explicit or detection has a receipt;
+- the requested operation is translation only—no hidden summarization,
+  extraction, browsing, or tool work;
+- source text, markup policy, glossary version, and source hash are retained;
+- chunking respects sentence/document boundaries and rejoins deterministically;
+- the selected model supports the pair, input length, script, and license;
+- terminology and protected tokens are validated after generation;
+- low confidence, unsupported pairs, glossary violations, or mixed reasoning
+  requirements fall back to the general Omnius lane.
+
+The lane lease should follow the same rule as the Telegram repair: a finite
+TTL that renews on model events, expires naturally when stale, and never stays
+resident merely because a request once existed.
+
+## Evaluation gate
+
+Before changing Mapsource or broker routing, build a representative corpus for
+the actual language pairs and text types. Compare the current 9B lane with the
+three license-compatible candidates on:
+
+- adequacy and named-entity/number preservation;
+- terminology and markup preservation;
+- p50/p95 first-token and completion latency;
+- peak/resident VRAM and cold-load time;
+- empty, truncated, wrong-language, and hallucinated-output rates;
+- long-input chunk/reassembly behavior.
+
+No live benchmark was run during this repair. Local model loading requires the
+repository's accelerator preflight and GPU lease protocol.
+
+## Primary sources
+
+- [Google TranslateGemma 4B model card](https://huggingface.co/google/translategemma-4b-it)
+- [Google TranslateGemma announcement and WMT24++ summary](https://blog.google/innovation-and-ai/technology/developers-tools/translategemma/)
+- [Google MADLAD-400 3B MT model card](https://huggingface.co/google/madlad400-3b-mt)
+- [Meta NLLB-200 distilled 600M model card](https://huggingface.co/facebook/nllb-200-distilled-600M)
+- [Helsinki-NLP OPUS-MT English-Maltese model inventory](https://huggingface.co/Helsinki-NLP/opus-mt-en-mt/tree/main)

package/docs/work-orders/runtime-health-remediation/WO-57-telegram-delivery-truth-and-recovery.md

@@ -1,9 +1,10 @@
 # WO-57: Telegram delivery truth, reminder authority, and bounded recovery
 
-**Status:** 1.0.798 live acceptance failed on Case Theory message 650;
-REQ-TDT-018 delivery-commit convergence and complete batch-scope repair are
-verified and pushed; full-suite, publication, redeployment, and live-acceptance
-gates remain open
+**Status:** REQ-TDT-019 and the REQ-TDT-016 lease correction were delivered in
+`cdf81ffd`; the 23-file Case Theory acceptance run then exposed the terminal
+same-response contract mismatch tracked by REQ-TDT-020. Its source repair was
+delivered in `1b451bc8`; publication, redeployment, live acceptance, and the
+pre-existing full-suite debt recorded below remain open.
 **Priority:** P0
 **Incident:** October 1, 2026, live Telegram reminder and illegal-logging non-responses
 **Owner:** Omnius orchestrator and Telegram runtime
@@ -138,6 +139,27 @@ please follow her instructions`, but the explicit-continuation grammar
       every retry reported `object work remains frozen`, no runner artifact
       changed after the false terminal commit, and typing ceased while the
       Telegram poller remained healthy.
+- [x] Anchor the 1.0.800 quick-chat commitment failure: OMNIUS message 5727 was
+      a native reply in topic 5712 saying `@omnius_agent_bot do it and provide
+      a report here`. The router understood the prior commitment but selected
+      zero-tool chat; message 5728 only promised to pull the Borneo data, the
+      intake was consumed, and no action task or retrieval run was created.
+- [x] Anchor the 1.0.800 Case Theory liveness risk: message 651 correctly
+      retained all 23 PDF criteria and advanced through 19 successful native
+      PDF reads, but Telegram configured `requestTimeoutMs:0` while the runner
+      watchdog exempted admitted inference. A backend promise that stopped
+      producing events could therefore retain the session forever.
+- [x] Anchor the message-651 terminal contract failure: all 23 PDFs were read,
+      the model authored the complete 23-row answer, and the objective frontier
+      reached `deliver_due` with only `effect:visible_response` open. The same
+      response called `task_complete(summary:...)` without duplicating that
+      long answer into `user_reply`; the bridge rejected it, no provider
+      delivery receipt was created, and the run ended
+      `incomplete_verification` at `2026-10-02T18:20:41-07:00`.
+- [x] Anchor convergence contamination: the first current-run completion
+      admission miss inherited 26 persisted rounds from the generic
+      `1:task_complete:no-target` family and immediately triggered forced
+      replanning for an unrelated objective.
 
 Runtime evidence:
 
@@ -352,8 +374,11 @@ Primary anchors:
 - [x] Renew the Telegram runner lease on every routed AgenticRunner lifecycle
       event, while excluding Telegram typing/UI timers that could otherwise
       keep an orphan alive indefinitely.
-- [x] Suppress lease expiry while an exact-session inference is admitted; the
-      inference operation retains its own bounded deadline.
+- [x] Suppress the outer runner lease only while an exact-session inference is
+      admitted and owns its own finite deadline. Telegram may not set
+      `requestTimeoutMs:0`; the configured/default inactivity lease is renewed
+      by every stream chunk, while unary auxiliary requests remain absolutely
+      bounded.
 - [x] On genuine event silence past the configured TTL, fence the generation,
       abort its runner/controller, release its session ownership, and requeue
       the exact retained intake through the existing durable recovery path.
@@ -674,6 +699,92 @@ Primary anchors:
 - `packages/cli/tests/telegram-lifecycle-leak.test.ts`
 - `packages/cli/tests/telegram-bot-api-10.test.ts`
 
+### REQ-TDT-019 — independent fulfillment and plan-before-promise transfer
+
+- [x] Separate transport/latency eligibility from fulfillment authority. A
+      router-approved conversational route may use the fast transport, but it
+      cannot certify that the generated candidate fulfilled the request.
+- [x] Run the independent typed fulfillment review for every quick-chat
+      candidate; remove the host branch that fabricated
+      `taskState:"fulfilled"` for low-risk group chat.
+- [x] Withhold every candidate classified `taskState:"continue"` from native
+      draft and Telegram message delivery. A future-work promise is local
+      untrusted text, not a provider-visible terminal response.
+- [x] Convert `continue` to action, obtain a complete input-bound plan with
+      nonempty scoped tool names, and only then create the durable open task and
+      action runner. Planning failure retains the exact intake for bounded
+      scheduler recovery without publishing the promise.
+- [x] Preserve true fulfilled conversation behavior: one independently
+      reviewed reply, one provider receipt, no action runner.
+- [x] Add the exact OMNIUS 5712 -> 5713 -> 5727 topology and assert that the
+      Borneo promise is withheld, action planning runs, and the open task exists
+      before object work begins.
+- [x] Pass focused quick-chat, working-indicator, steering, lifecycle,
+      inference-timeout, intake, and terminal-delivery suites plus CLI
+      typecheck and formatting.
+
+Primary anchors:
+
+- `packages/cli/src/tui/telegram-bridge.ts` — quick-chat semantic admission,
+  withheld-draft transfer, validated action planning, and finite inference TTL.
+- `packages/cli/tests/telegram-quick-chat-contract.test.ts`
+- `packages/cli/tests/telegram-working-indicator.test.ts`
+- `packages/cli/tests/telegram-stream-timeout.test.ts`
+- `packages/cli/tests/telegram-terminal-delivery.test.ts`
+
+### REQ-TDT-020 — same-response terminal binding and convergence isolation
+
+- [x] Let a Telegram answer and its sole `task_complete` operation in the same
+      model response share one host-bound visible-response candidate; do not
+      require the model to duplicate a long answer inside tool arguments.
+- [x] Bind that candidate only when run ID, task epoch, turn, objective scope,
+      and frontier fingerprint match and `visible_response` is the sole
+      remaining effect.
+- [x] Reject prior-turn drafts, intermediate answers, stale objectives, and
+      responses containing any sibling operation.
+- [x] When a visible candidate is followed by legitimate read-only refinement,
+      bind the exception to its exact run/task/response-turn identity, consume
+      it once, and fence any repeated operation unless a fresh candidate is
+      authored.
+- [x] Keep `task_complete` admission feedback in the current run, but exclude
+      the generic control-tool failure family from persistent cross-objective
+      convergence state.
+- [x] Add streaming/non-streaming positive controls plus stale-turn,
+      sibling-operation, repeated-read, and persistence-isolation regressions.
+
+Primary anchors:
+
+- `packages/orchestrator/src/agenticRunner.ts`
+- `packages/orchestrator/src/focusSupervisor.ts`
+- `packages/orchestrator/src/taskObjective.ts`
+- `packages/orchestrator/tests/telegram-visible-response-authority.test.ts`
+- `packages/orchestrator/tests/focusSupervisor.test.ts`
+- `packages/orchestrator/tests/task-objective.test.ts`
+- `packages/cli/tests/telegram-streamed-terminal-answer.test.ts`
+
+### Residual full-suite authority debt (not introduced by REQ-TDT-020)
+
+- [ ] Replace loop-detector `redirect` steering with an internal,
+      task-epoch/TTL-bound repetition directive. It may reject only the exact
+      repeated action fingerprint and must not impersonate new user authority.
+- [ ] Preserve schema-first rejection while invoking a tool's custom
+      `validateInput` once so typed domain diagnostics replace generic schema
+      errors without allowing invalid input.
+- [ ] Bring legacy Telegram conversation-evidence fixtures onto the selected
+      capability contract instead of asking a `route:"chat"` turn with no
+      `actionToolNames` to execute deferred `shell`/`diagnostic` tools.
+- [ ] Rerun the complete orchestrator and CLI suites and close only when their
+      previously red baseline is green without weakening production gates.
+
+Evidence anchors:
+
+- `packages/orchestrator/tests/evidenceBranch-runner.test.ts` — internal
+  loop-detector steering blocks a materially different ranged read.
+- `packages/cli/tests/diagnostic-boundary.test.ts` — generic schema rejection
+  currently bypasses the tool-specific validator.
+- `packages/cli/tests/telegram-conversation-evidence.test.ts` — fixture omits
+  the selected tool capability and is correctly denied by production dispatch.
+
 ## Cross-surface validation gates
 
 - [x] Orchestrator focused tests pass for visible-response evidence, completion
@@ -717,6 +828,8 @@ Primary anchors:
 | REQ-TDT-016 | event cadence + renewable runner lease            | lifecycle leak + steering/finalization             | delivered; redeploy pending     |
 | REQ-TDT-017 | exact Telegram forum-topic delivery               | final chunks + commands + artifacts                | focused green; redeploy pending |
 | REQ-TDT-018 | delivery commit + full batch recovery             | exact 23-file message-650 replay                   | focused green; deploy pending   |
+| REQ-TDT-019 | fulfillment review + plan-before-promise transfer | exact OMNIUS 5727 + fulfilled-chat control         | delivered in `cdf81ffd`         |
+| REQ-TDT-020 | same-response completion + convergence isolation  | message 651 terminal answer + stale/sibling controls | delivered in `1b451bc8`        |
 
 ## Evidence log
 
@@ -1185,3 +1298,70 @@ delivery controls`). Both scoped commits were pushed to tracked branch
 - No live inference, Telegram send, publication, installation, or service
   restart was performed. Deployment and live Case Theory/OMNIUS acceptance
   remain open.
+
+### 2026-10-03 — live 1.0.800 quick-chat transfer and inference-lease repair
+
+- OMNIUS message 5727 proved that social reply authority and task fulfillment
+  were still conflated. The router correctly understood the direct reply to a
+  prior bot commitment, but quick chat skipped independent fulfillment review,
+  fabricated `fulfilled`, delivered another promise as message 5728, and
+  consumed the intake without an action task.
+- Fast-path eligibility is now only a transport decision. Every candidate is
+  independently classified as fulfilled or continue. A continuation candidate
+  is never streamed or sent; it is converted to action, receives a validated
+  input-bound tool/outcome plan, and reaches durable task creation before any
+  object work begins. Invalid planning uses the bounded exact-intake recovery
+  path without exposing the promise.
+- Case Theory message 651 was progressing rather than file-I/O stalled: 19 of
+  23 PDFs had successful native text extraction and the itemized frontier kept
+  messages 639-642 plus visible response open. The remaining hard liveness gap
+  was `requestTimeoutMs:0`: an admitted backend promise was exempt from the
+  outer watchdog and had no deadline of its own.
+- Telegram action runners now use the existing configurable 300-second stream
+  inactivity lease. Each response chunk renews it; unary/auxiliary calls are
+  bounded by the same value; explicit stop remains immediate. This restores the
+  REQ-TDT-016 invariant without imposing a blind whole-task timer.
+- Focused validation passed 230/230 across quick-chat, working-indicator,
+  steering, intake, lifecycle, observability, inference-contract/timeout, and
+  terminal-delivery suites. CLI typecheck and build passed; Prettier and
+  `git diff --check` passed. Commit `cdf81ffd` was pushed to tracked branch
+  `origin/main`. No live inference, Telegram send, publication, installation,
+  or service restart was performed.
+
+### 2026-10-03 — message-651 terminal convergence repair
+
+- The live Case Theory runner successfully extracted all 23 PDFs and authored
+  the complete 23-row answer. Its frontier contained 26 evidence records and
+  reached `deliver_due`; `effect:visible_response` was the sole open criterion.
+  The answer and a summary-only `task_complete` occurred in the same model
+  response, but the adapter required `user_reply` even though the tool schema
+  made it optional. The answer was discarded and the run ended
+  `incomplete_verification` with no delivery receipt.
+- The runner now host-binds same-response visible text to a sole
+  `task_complete` operation. Admission requires exact run, task epoch, turn,
+  objective scope, frontier fingerprint, and a sole remaining
+  `visible_response` effect. It cannot reuse an earlier draft or bind when any
+  sibling operation remains.
+- A following read-only refinement can invalidate an exact buffered candidate
+  through a one-shot run/task/response-turn lease. The lease is consumed on
+  admission; a second read is fenced unless a new candidate is authored. This
+  preserves bounded refinement without reopening the Case Theory runaway.
+- `task_complete` admission failures remain available to same-run focus
+  guidance but no longer enter the persistent convergence breaker. This
+  prevents the observed generic `1:task_complete:no-target` family from
+  carrying 26 unrelated rounds into a new objective.
+- Focused validation passed 219/219: 72 orchestrator objective/authority/focus
+  regressions and 147 CLI terminal-delivery, streamed-answer, lifecycle, and
+  agent-observability regressions. Orchestrator and CLI typechecks/builds plus
+  `git diff --check` passed. Source commit `1b451bc8` was pushed to tracked
+  branch `origin/main`.
+- The complete CLI suite reached 3,136 passing and 19 failing tests. The
+  failures reproduce outside this change and include stale capability fixtures,
+  source-shape assertions, and older validation/authority-domain regressions.
+  The complete orchestrator suite likewise exposed pre-existing deterministic
+  reds and one long-lived worker, so it was stopped after the gate was already
+  red. Those failures remain explicitly unchecked above; they were not hidden
+  or converted into weaker assertions.
+- Publication, installation, restart, and a fresh provider delivery receipt
+  remain open. The observed Case Theory 651 and OMNIUS 5727 runs predate this
+  source deployment and are not acceptance evidence for the repair.

package/docs/work-orders/runtime-health-remediation/WO-58-agent-scoped-footer-observability.md

@@ -0,0 +1,69 @@
+# WO-58 — Agent-scoped footer observability
+
+Status: source delivered in `8a81eab6`; deployment acceptance pending
+
+## Problem
+
+The TUI's agent selector changes the visible scrollback, but the stage block,
+context gauge, token/model/SNR/cost pages, uptime, and activity signal continue
+to describe the base session. Telegram child events also lose their view ID at
+the bridge callback boundary, and completed views are immediately discarded.
+This makes an active or stalled child look indistinguishable from the base
+agent and removes the evidence needed to inspect a just-finished run.
+
+## Invariants
+
+- Selecting an agent selects one coherent observability scope: scrollback,
+  stage, context, token metrics, model/backend, SNR, cost, runtime, and status.
+- Unknown child metrics render as `--`; base-session values must never leak into
+  a child view.
+- The base agent remains a selectable scope.
+- Agent indicators use terminal-cell widths, remain inside the footer, and do
+  not overlap other footer content on narrow terminals.
+- Completed views remain inspectable for a bounded history and are pruned after
+  a 30-minute TTL or when the 12-view cap is exceeded.
+- Structured telemetry is attributed by immutable view ID, never inferred from
+  display text or the currently selected view.
+
+## Implementation checklist
+
+- [x] Define a canonical per-view telemetry snapshot beside each agent view.
+- [x] Preserve the existing global metrics as the explicit `main` scope.
+- [x] Ingest structured token, context, tool, stream, and status events into the
+      matching view snapshot.
+- [x] Forward Telegram runner events across the bridge with their view ID.
+- [x] Drive the footer stage block and every metrics page from the selected
+      view.
+- [x] Render honest `--` values when a child backend does not expose a metric.
+- [x] Add stable, status-colored agent dots adjacent to the metrics page
+      indicator, including the base agent.
+- [x] Make each visible dot a precise mouse hit target that selects its view.
+- [x] Show the selected agent name beside the `[n/6]` page indicator.
+- [x] Bound dot overflow with `+N`, cap the selected label, and verify narrow
+      terminal layout does not overlap.
+- [x] Retain and prune a bounded set of completed/failed/stopped view snapshots.
+- [x] Keep Ctrl-Left/Ctrl-Right and the agents command center synchronized with
+      the same selected view.
+
+## Validation checklist
+
+- [x] Unit-test per-agent metric isolation and unknown-value rendering.
+- [x] Unit-test structured event attribution and Telegram callback forwarding.
+- [x] Unit-test dot rendering, status changes, click selection, overflow, and
+      narrow-terminal width.
+- [x] Unit-test completed-view retention and bounded pruning.
+- [x] Run affected TUI and Telegram test suites.
+- [x] Run CLI typecheck and build.
+- [x] Run `git diff --check`.
+- [x] Commit the scoped repair, fetch the tracked branch, and push it.
+- [ ] Validate dot selection and per-agent footer pages in the published TUI.
+
+## Delivery evidence
+
+- Commit: `8a81eab6` (`feat(tui): scope footer telemetry by agent`)
+- Remote branch: `origin/main`
+- Tests: 108/108 focused TUI/Telegram observability tests; 147/147 when
+  combined with Telegram terminal and streamed-answer regressions; CLI
+  typecheck/build and `git diff --check` passed.
+- Live acceptance: pending publication/installation; the currently running
+  `telegram_test` process predates this build.

package/docs/work-orders/runtime-health-remediation/WO-59-telegram-restart-edit-crash.md

@@ -0,0 +1,112 @@
+# WO-59: Telegram restart edit crash and terminal-intake monotonicity
+
+**Status:** COMPLETE — implemented, verified, and pushed in `9fadef51`
+**Priority:** P0
+**Incident:** October 3, 2026, `telegram_test` TUI exits immediately while
+loading the OMNIUS Telegram session
+**Owner:** Omnius Telegram durable-intake runtime
+**Depends on:** WO-57
+**Completion rule:** Mark a checkbox complete only when its code anchor and
+deterministic evidence exist. Do not delete or rewrite live Telegram state to
+make startup appear healthy.
+
+## Objective
+
+Make edited Telegram messages retain one logical input identity across process
+restart. A later `edited_message` envelope for a terminal input must be stored
+as evidence and transport-terminalized without reopening cognition, scheduling
+work, or allowing a stale nonterminal transition to terminate the TUI.
+
+## Live failure anchors
+
+- [x] Confirm the foreground TUI PID `2136726` exited while the independently
+      supervised `omnius-daemon.service` stayed healthy.
+- [x] Correlate the exact exit at `2026-10-03T07:11:40.465Z` with
+      `TelegramUpdateConflictError: Telegram input
+telegram:chat:-1003888256865:5719:5726 is already terminal as consumed`
+      in `~/.omnius/crash.log`.
+- [x] Confirm the global `unhandledRejection` boundary converted the escaped
+      background lifecycle rejection into `process.exit(1)`.
+- [x] Confirm conversation temp files owned by PID `2136726` were truncated
+      mid-write at the same timestamp; they are consequences of immediate
+      process exit, not malformed canonical conversation input.
+- [x] Confirm durable spool identity: original update `666869361` and edited
+      update `666869375` bind to the same immutable input, message `5726`, and
+      topic `5719`; the logical intake was already `consumed`.
+- [x] Locate the restart gap: the early edited-message gate checks only the
+      process-local `telegramIntakeRecords` map, so an edit arriving after
+      restart bypasses consolidation, rehydrates a terminal durable intake,
+      and attempts an illegal `consumed -> deferred` transition.
+
+## Repair checklist
+
+### REQ-TERC-001 — restart-safe edit identity
+
+- [x] Consult the durable intake store when an edited message is absent from
+      process-local memory.
+- [x] Rehydrate and consolidate the persisted logical intake without starting
+      a second cognition/reply run.
+- [x] Keep the edited raw envelope transport-terminal and preserve the
+      original logical intake owner.
+
+Primary anchors:
+
+- `packages/cli/src/tui/telegram-bridge.ts` — edited-message ingress gate and
+  durable intake registration.
+- `packages/cli/tests/telegram-durable-intake-integration.test.ts`
+
+### REQ-TERC-002 — terminal intake monotonicity
+
+- [x] Treat an exact-binding terminal durable state as authoritative when a
+      stale asynchronous nonterminal transition arrives.
+- [x] Do not mutate the process-local record before the durable transition is
+      accepted.
+- [x] Continue throwing immutable identity/binding conflicts; do not weaken
+      the spool contract or global crash handler.
+- [x] Journal the rejected stale transition as reconciliation evidence.
+
+Primary anchors:
+
+- `packages/cli/src/tui/telegram-bridge.ts` — `transitionTelegramIntake()` and
+  `settleTelegramUpdateFromIntake()`.
+- `packages/cli/tests/telegram-durable-intake-integration.test.ts`
+
+### REQ-TERC-003 — validation and delivery
+
+- [x] Regression: a terminal input followed by an edited envelope after
+      restart does not call `scheduleTelegramSessionWork()` and does not throw.
+- [x] Regression: a stale nonterminal transition cannot regress a terminal
+      durable intake or its in-memory projection.
+- [x] Run focused Telegram durable-intake and update-spool tests.
+- [x] Run CLI typecheck and build.
+- [x] Replay the exact live `telegram_test` WAL-backed spool snapshot and
+      edited envelope in an offline temporary project without model inference;
+      confirm terminal state, original owner, and zero scheduler calls.
+- [x] Commit only WO-59-owned files, fetch the tracked branch, and push the
+      verified repair.
+
+## Non-goals and safety constraints
+
+- Do not delete or rewrite the 8.9 GB `.omnius` state tree.
+- Do not discard the 3.3 GB deferred-memory spool; its TTL/rotation concern is
+  separate from this exact crash fingerprint.
+- Do not catch every unhandled rejection globally or convert durable identity
+  conflicts into generic warnings.
+- Do not send live inference while validating startup.
+
+## Evidence log
+
+- Runtime crash log: `/home/roko/.omnius/crash.log`
+- Durable spool:
+  `/home/roko/Documents/Projects/Adjacent/telegram_test/.omnius/telegram-runner-state/bot-8929483195.updates.sqlite`
+- Consequence temp files:
+  `/home/roko/Documents/Projects/Adjacent/telegram_test/.omnius/telegram-conversations/*.2136726.*.tmp`
+  and
+  `/home/roko/Documents/Projects/Adjacent/telegram_test/.omnius/telegram-runner-state/*.2136726.*.tmp`
+- Focused validation: 7 test files, 162 tests passed; CLI typecheck and build
+  passed.
+- Live-state offline replay: input
+  `telegram:chat:-1003888256865:5719:5726`, memory and durable lifecycle
+  `consumed`, owner update `666869361`, scheduler calls `0`.
+- Delivery: implementation commit `9fadef51` pushed to `origin/main` after a
+  clean tracked-branch fetch (`origin/main...HEAD = 0/0`).

package/npm-shrinkwrap.json

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

package/package.json

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