omnius 1.0.790 → 1.0.792

package/dist/index.js

@@ -1,4 +1,4 @@
 [diffend] Oversized file quarantined before diffing.
 name: package/dist/index.js
-size: 39149911 bytes
-sha256: aabd198f653747f7bdcd71ff6b1ce9640993c278cce6dd7f76712f15490068f1
+size: 39174630 bytes
+sha256: 87ab8a29d4940490150f770d36324499523adc53185959f4fa334a600f9d7d79

package/docs/DISCOVERY.json

@@ -35902,6 +35902,46 @@
         }
       ]
     },
+    {
+      "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: implementation complete in working tree; focused validation green; full-suite and repository-delivery gates remain open Priority: P0 Incident: October 1, 2026, live Telegram reminder and illegal-logging non-responses Owner: Omnius orchestrator and Telegram runtime Depends on: WO-41, WO-44, WO-49, WO-52, WO-54, WO-55, WO-56 Completion rule: A checkbox",
+      "keywords": [
+        "work",
+        "orders",
+        "runtime",
+        "health",
+        "remediation",
+        "WO",
+        "57",
+        "telegram",
+        "delivery",
+        "truth",
+        "and",
+        "recovery",
+        "md"
+      ],
+      "maturity": "internal",
+      "audiences": [
+        "maintainer",
+        "large-context-agent"
+      ],
+      "layer": "documentation",
+      "interfaces": [
+        {
+          "type": "file",
+          "target": "docs/work-orders/runtime-health-remediation/WO-57-telegram-delivery-truth-and-recovery.md"
+        }
+      ],
+      "references": [
+        {
+          "type": "documentation",
+          "target": "docs/work-orders/runtime-health-remediation/WO-57-telegram-delivery-truth-and-recovery.md",
+          "relation": "canonical-artifact"
+        }
+      ]
+    },
     {
       "id": "guide.work-orders-telegram-dmn-wo-22-dmn-outreach-and-learning-uppercase",
       "kind": "guide",

package/docs/DISCOVERY.md

@@ -609,6 +609,7 @@ 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: implementation complete in working tree; focused validation green; full-suite and repository-delivery gates remain open Priority: P0 Incident: October 1, 2026, live Telegram reminder and illegal-logging non-responses Owner: Omnius orchestrator and Telegram runtime Depends on: WO-41, WO-44, WO-49, WO-52, WO-54, WO-55, WO-56 Completion rule: A checkbox |
 | `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/work-orders/runtime-health-remediation/TRACKER.md

@@ -4,6 +4,10 @@
 **Checked-item rule:** code, focused tests, and named evidence must all exist
 **Last reconciled:** 2026-09-27
 
+## October 1 Telegram delivery-truth follow-up
+
+- [ ] [WO-57: Telegram delivery truth, reminder authority, and bounded recovery](WO-57-telegram-delivery-truth-and-recovery.md): require transport-backed visible-response evidence, receipt-backed reminder mutations, non-circular inline research delivery, atomic steering, wrapped WebFetch receipt parsing, and evidence-preserving bounded recovery.
+
 ## September 27 evidence-driven objective loop and TUI responsiveness
 
 - [ ] [WO-56: Evidence-driven objective loop and nonblocking execution](WO-56-evidence-driven-objective-loop.md): reconcile every tool result against an immutable request-specific objective, prevent duplicate successful external effects, distinguish verifier failure from artifact failure, suspend and resume natural clarification durably, preserve verified Telegram delivery, and remove blocking privilege execution from the TUI event loop.

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

@@ -0,0 +1,374 @@
+# WO-57: Telegram delivery truth, reminder authority, and bounded recovery
+
+**Status:** implementation complete in working tree; focused validation green;
+full-suite and repository-delivery gates remain open
+**Priority:** P0
+**Incident:** October 1, 2026, live Telegram reminder and illegal-logging non-responses
+**Owner:** Omnius orchestrator and Telegram runtime
+**Depends on:** WO-41, WO-44, WO-49, WO-52, WO-54, WO-55, WO-56
+**Completion rule:** A checkbox may be marked complete only when the named code,
+deterministic regression, and validation evidence all exist. Generated model text
+is not a Telegram delivery receipt.
+
+## Objective
+
+Restore truthful, bounded delivery across Telegram action, quick-chat, steering,
+and recovery paths. A successful observation must reach the user exactly once;
+a mutation may be claimed only after its typed tool receipt; inline research must
+not require an impossible external-provider receipt; recovery must reuse current
+verified evidence instead of replaying the full reasoning loop.
+
+## Baseline and live evidence
+
+- [x] Record implementation baseline: `d654916274d9fb8dff696d0b04f6dd600d1f8a18`,
+      branch `main`, upstream `origin/main`.
+- [x] Preserve the pre-existing dirty orchestrator work listed in the evidence
+      log below; WO-57 must not revert or absorb unrelated changes.
+- [x] Confirm Telegram polling was healthy: live PID `1028538`, installed
+      `omnius@1.0.790`, zero consecutive poll failures, and no replay backlog.
+- [x] Anchor reminder-list failure: message 609 retrieved 29 reminders twice,
+      read the complete spill file, authored a valid roster, then completed with
+      `summary:"no_reply"` without a Telegram message.
+- [x] Anchor reminder-mutation failure: message 5698 delivered
+      `on it. deleting that reminder now.` through tool-free quick chat while
+      `rem-c7229d33` remained `pending` with active cancellation state.
+- [x] Anchor news failure: messages 5706/5707 performed PNG/Borneo research but
+      all terminal paths lacked a delivered `user_reply`; Borneo remained
+      search-only and the conversation ended at assistant message 5705.
+- [x] Anchor false-acknowledgement failure: OMNIUS message 5712 was routed to
+      zero-tool quick chat, delivered only `on it. pulling the Borneo illegal
+      logging data now.`, and was marked consumed without a retrieval run.
+- [x] Anchor follow-up router failure: Case Theory message 610 was a same-sender
+      reply to the failed reminder-list request 609, but router reconciliation
+      exhausted and the fallback lost its exact `inputId`, producing
+      `input missing input != telegram:chat:-1003960149435:0:610`.
+
+Runtime evidence:
+
+- `/home/roko/Documents/Projects/Adjacent/telegram_test/.omnius/telegram-runner-state/84e4e6e5411c97531047/debug-library/runs/telegram-84e4e6e5411c9753-1790885133822-1/events.jsonl`
+- `/home/roko/Documents/Projects/Adjacent/telegram_test/.omnius/telegram-runner-state/84e4e6e5411c97531047/completion-finalizations/telegram-84e4e6e5411c9753-1790885133822-1.json`
+- `/home/roko/Documents/Projects/Adjacent/telegram_test/.omnius/telegram-conversations/84e4e6e5411c97531047.json`
+- `/home/roko/Documents/Projects/Adjacent/telegram_test/.omnius/telegram-conversations/c34a3d7d53728329c081.json`
+- `/home/roko/Documents/Projects/Adjacent/telegram_test/.omnius/scheduled/reminders.json`
+
+## Requirements and implementation checklist
+
+### REQ-TDT-001 — transport-backed visible response
+
+- [x] Stop crediting `visible_response` when assistant text is generated inside
+      the runner but has not crossed a surface delivery boundary.
+- [x] Require typed visible-response/delivery evidence for readiness whenever
+      the objective contains `effect:visible_response`.
+- [x] Preserve non-surface agent behavior that legitimately treats authored
+      text as an in-process result.
+- [x] Add a regression reproducing message 609: internal roster text plus
+      `task_complete(summary:"no_reply")` cannot complete the visible-response
+      criterion.
+
+Primary anchors:
+
+- `packages/orchestrator/src/agenticRunner.ts` — expected-effect observation and
+  terminal `task_complete` handling.
+- `packages/orchestrator/src/completionReadiness.ts` — expected-effect readiness
+  projection.
+- `packages/orchestrator/tests/telegram-visible-response-authority.test.ts`
+- `packages/orchestrator/tests/terminal-finalization-runner.test.ts`
+- `packages/orchestrator/tests/agenticRunner.test.ts`
+
+### REQ-TDT-002 — Telegram task completion must carry the reply
+
+- [x] For a Telegram task that owns `visible_response`, reject successful
+      `task_complete` without a non-empty `user_reply` or an already recorded
+      current-input Telegram delivery receipt.
+- [x] Treat `summary` as internal metadata only; `summary:"no_reply"` must never
+      satisfy or suppress a required reply.
+- [x] Keep intentional no-reply behavior available only for contracts that do
+      not require a visible response.
+- [x] Test public group, private chat, and intentional-no-reply controls.
+
+Primary anchors:
+
+- `packages/cli/src/tui/telegram-bridge.ts` — task-complete adapter, terminal
+  selection, public incomplete-run suppression.
+- `packages/cli/tests/telegram-terminal-delivery.test.ts`
+- `packages/cli/tests/telegram-admin-incomplete.test.ts`
+
+### REQ-TDT-003 — reminder mutations require reminder receipts
+
+- [x] Classify create/update/delete/dismiss/snooze reminder imperatives as
+      action turns, including replies to reminder messages.
+- [x] Make reminder mutations ineligible for tool-free quick-chat completion
+      and semantic-review skip.
+- [x] Do not deliver success language until the reminder tool returns the
+      affected reminder ID and terminal state.
+- [x] Add replay regressions for messages 5652, 5653, 5698, and Case Theory
+      message 607; assert the registry changes or a truthful failure is sent.
+
+Primary anchors:
+
+- `packages/cli/src/tui/telegram-bridge.ts` — router normalization, quick-chat
+  eligibility, semantic review, reminder truth contract.
+- `packages/execution/src/tools/reminder.ts` — dismiss/cancellation receipt.
+- `packages/cli/tests/telegram-quick-chat-contract.test.ts`
+- `packages/cli/tests/telegram-reminder-contract.test.ts`
+
+### REQ-TDT-004 — inline research has no circular delivery gate
+
+- [x] Normalize inline Telegram research to `outcome:"read_only"` with required
+      effects `observation` and `visible_response`.
+- [x] Reserve `delivery` for a separately requested external-provider effect.
+- [x] Reject or repair router contracts that attach external delivery to a
+      same-chat answer.
+- [x] Reproduce PNG message 5706 and prove verified research can reach Telegram
+      without an impossible pre-send delivery receipt.
+
+Primary anchors:
+
+- `packages/cli/src/tui/telegram-bridge.ts` — router prompt, expected-outcome
+  validation/normalization, terminal dispatch.
+- `packages/orchestrator/src/agenticRunner.ts` — delivery receipt hard gate.
+- `packages/cli/tests/telegram-router-model-selection.test.ts`
+- `packages/cli/tests/telegram-terminal-delivery.test.ts`
+
+### REQ-TDT-005 — steering is one authoritative request
+
+- [x] Apply accepted steering to the current goal, authorization input, owner,
+      expected outcome, and model-visible prompt atomically.
+- [x] Prevent split state where finalization targets Borneo message 5707 while
+      the model remains authorized only for PNG message 5706.
+- [x] Require retrieval evidence for the steered topic before composing claims.
+- [x] Add a PNG-to-Borneo steering regression covering prompt projection,
+      ownership transfer, retrieval, and reply delivery.
+
+Primary anchors:
+
+- `packages/cli/src/tui/telegram-bridge.ts` — steering reconciliation and task
+  projection.
+- `packages/orchestrator/src/agenticRunner.ts` — current steering projection.
+- `packages/cli/tests/telegram-causal-consolidation.test.ts`
+- `packages/orchestrator/tests/agenticRunner-conversation-steering.test.ts`
+
+### REQ-TDT-006 — wrapped web receipts and semantic redirects
+
+- [x] Parse every well-formed `WEB_FETCH_RECEIPT` marker in a safety-wrapped
+      tool result, not only line one.
+- [x] Keep malformed, duplicated, or untrusted receipt-shaped page content from
+      becoming authority.
+- [x] Bind requested and final URLs and flag cross-topic redirects as unusable
+      evidence unless separately validated.
+- [x] Add wrapper, malformed-marker, duplicate-marker, canonical redirect, and
+      unrelated HTTP-200 redirect tests.
+
+Primary anchors:
+
+- `packages/cli/src/tui/telegram-safe-delivery.ts`
+- `packages/cli/tests/telegram-safe-delivery.test.ts`
+- `packages/cli/tests/telegram-tool-link-preview.test.ts`
+
+### REQ-TDT-007 — bounded evidence-preserving recovery
+
+- [x] When a current-input verified reply candidate already satisfies the
+      observation frontier, recovery must review/deliver that candidate rather
+      than restart tool discovery.
+- [x] A simple reminder list must not run the full repeated virtual-memory and
+      compilation pipeline after each deterministic tool result.
+- [x] Recovery must retain exact input/task epoch ownership and send at most one
+      reply.
+- [x] Add a regression matching message 609: one reminder observation, one
+      retained candidate, one bounded recovery, one delivery, no second list.
+
+Primary anchors:
+
+- `packages/cli/src/tui/telegram-bridge.ts` — terminal metacognitive review and
+  scheduler recovery.
+- `packages/orchestrator/src/agenticRunner.ts` — memory/compiler eligibility.
+- `packages/cli/tests/telegram-terminal-delivery.test.ts`
+- `packages/cli/tests/telegram-cognition-queue.test.ts`
+
+### REQ-TDT-008 — retrieval capability and exact router-failure ownership
+
+- [x] Promote a directly addressed, thread-referenced request to get/fetch/show
+      data from zero-tool chat into action planning before quick-chat admission.
+- [x] Promote an exact reminder-list request and a same-sender follow-up such as
+      message 610 to the reminder observation contract.
+- [x] Bind every router-unavailable decision to the host-owned exact input ID;
+      never repair a genuinely mismatched/stale ID inside the commit boundary.
+- [x] Attempt durable active-runner router recovery before any infrastructure-
+      authored no-reply disposition can be committed as social judgment.
+- [x] Keep ordinary addressed conversation and unaddressed human-to-human data
+      talk outside the action repair.
+
+Primary anchors:
+
+- `packages/cli/src/tui/telegram-bridge.ts` — trusted capability boundaries,
+  router-unavailable construction, and active-runner recovery ordering.
+- `packages/cli/tests/telegram-steering-finalization.test.ts` — exact 5712/610
+  replays and negative controls.
+- `packages/cli/tests/telegram-bot-api-10.test.ts` — exact fallback binding,
+  diagnostic preservation, and recovery-before-commit regression.
+- `packages/cli/tests/telegram-social-decision-binding.test.ts` — stale-input
+  negative control at the durable social commit boundary.
+
+## Cross-surface validation gates
+
+- [x] Orchestrator focused tests pass for visible-response evidence, completion
+      readiness, steering, and recovery.
+- [x] Telegram focused tests pass for public group, private chat, quick chat,
+      reminder mutation, research delivery, steering, receipts, and recovery.
+- [ ] Full `packages/orchestrator` tests pass.
+- [ ] Full `packages/cli` tests pass.
+- [x] Execution, orchestrator, and CLI builds pass from a clean package build
+      state.
+- [x] `git diff --check` passes.
+- [x] Traceability matrix below has no uncovered requirement.
+- [x] Independent review finds no path that can claim a mutation without its
+      typed receipt or bind a Telegram response without exact current reply or
+      provider-delivery authority.
+- [ ] Changes are committed in scoped, verified commits and pushed to the
+      tracked branch.
+- [ ] Live Telegram acceptance remains unchecked unless the exact deployed
+      runtime is rebuilt/restarted and validated under the hardware and service
+      gates.
+
+## Traceability matrix
+
+| Requirement | Production anchors | Regression anchors | Status |
+|---|---|---|---|
+| REQ-TDT-001 | orchestrator expected effects/readiness | terminal finalization + runner | focused green |
+| REQ-TDT-002 | Telegram task completion/delivery | public/private/no-reply | focused green |
+| REQ-TDT-003 | Telegram routing + reminder receipt | 5652/5653/5698/607 replay | focused green |
+| REQ-TDT-004 | expected-outcome normalization | PNG inline research | focused green |
+| REQ-TDT-005 | steering projection/ownership | PNG to Borneo steering | focused green |
+| REQ-TDT-006 | safe-delivery receipt parser | wrappers + redirects | focused green |
+| REQ-TDT-007 | terminal recovery/memory eligibility | retained-candidate recovery | focused green |
+| REQ-TDT-008 | capability admission + unavailable ownership | 5712/610 + recovery ordering | focused green |
+
+## Evidence log
+
+### 2026-10-01 — implementation start
+
+- Baseline head: `d654916274d9fb8dff696d0b04f6dd600d1f8a18`.
+- Tracked branch: `main` -> `origin/main`.
+- Pre-existing dirty scope preserved:
+  `packages/orchestrator/src/agenticRunner.ts`, eleven orchestrator tests,
+  `packages/orchestrator/src/reasoning-checkpoint-policy.ts`,
+  `packages/orchestrator/tests/fixtures/deferred-tool-policy.ts`, and
+  `packages/orchestrator/tests/reasoning-checkpoint.test.ts`.
+- No live inference, service restart, reminder mutation, or Telegram send is
+  authorized by this work order's repository implementation phase.
+
+### 2026-10-01 — REQ-TDT-006 wrapped receipt and redirect boundary
+
+- Test-first red phase reproduced exact-wrapper rejection, duplicate-marker
+  admission, changed-query admission, HTTPS downgrade, and the observed ABC
+  illegal-logging-to-Tasmania HTTP 200 redirect.
+- `telegram-safe-delivery.ts` now accepts a receipt only as the first line or
+  immediately after the exact host-authored public-web safety preamble. It
+  rejects arbitrary later/body markers and duplicates.
+- WebFetch evidence now fails closed when redirects change resource identity;
+  HTTP-to-HTTPS, optional leading `www`, trailing slash, and fragment-only
+  changes remain admissible.
+- Focused regression: 71/71 passed across `telegram-safe-delivery`,
+  `telegram-terminal-delivery`, and `telegram-working-indicator`.
+- CLI typecheck and build passed; `git diff --check` passed.
+
+### 2026-10-01 — REQ-TDT-001/002 transport and completion authority
+
+- Telegram model text is now a buffered candidate, not transport evidence.
+  Non-Telegram immediate-render surfaces retain their prior in-process
+  visible-response behavior.
+- A successful Telegram `task_complete` owns visibility only when the exact
+  accepted call carried `user_reply`, or a provider-authored Telegram delivery
+  receipt was recorded in the current run. `summary` has no reply authority.
+- `telegram-visible-response-authority.test.ts` covers summary-only rejection,
+  explicit reply acceptance, provider delivery, Telegram direct-answer mode,
+  and the non-Telegram control.
+
+### 2026-10-01 — REQ-TDT-003 reminder mutation truth
+
+- Trusted reminder imperatives and replies to bot-authored `Reminder:` messages
+  are normalized to action routing before quick-chat admission. Unaddressed
+  ambient group text remains a negative control.
+- `ReminderTool` now emits `omnius.reminder-mutation-receipt.v1` for set,
+  complete, dismiss, and snooze. The Telegram wrapper promotes a successful
+  typed receipt to mutation and verification evidence; prose alone cannot do
+  so.
+- Replays cover messages 5652, 5653, 5698, and Case Theory 607. The execution
+  registry regression verifies the stored ID/state/cancellation receipt.
+
+### 2026-10-01 — REQ-TDT-004/005 research and steering
+
+- Inline web research is normalized from external `delivery` to `read_only`
+  with `observation` and `visible_response`; actual external file/provider
+  delivery contracts remain unchanged.
+- Accepted same-task steering updates the durable goal, versioned amendment,
+  expected outcome, objective criteria, model-visible guidance, and exact
+  response authorization. Ownership transfers only after the first affected
+  action.
+- Updating the steered expected-outcome contract clears observed effects, so
+  PNG-era observation cannot satisfy the Borneo contract. The current
+  observation and terminal candidate must be re-established under the amended
+  run/epoch/frontier before delivery.
+
+### 2026-10-01 — REQ-TDT-007 bounded recovery
+
+- A settled current run may close only a sole `visible_response` gap using a
+  verified candidate whose task, run, epoch, contract revision, and frontier
+  still match. All non-visibility effects must already be observed.
+- The message-609 regression retains the 29-reminder roster, performs one
+  terminal review, sends it once, runs the object-level fixture once, and does
+  not schedule another recovery/list cycle.
+
+### 2026-10-01 — validation and delivery state
+
+- Focused orchestrator validation: 22/22 passed across Telegram response
+  authority, terminal finalization, and conversation steering. Orchestrator
+  typecheck passed.
+- Reminder execution validation: 72/72 `temporal-agency` tests passed.
+  Execution typecheck and build passed.
+- Focused Telegram validation: 319/319 passed across the receipt, delivery,
+  working-indicator, steering, attention, streamed-terminal, quick-chat,
+  reminder, router, cognition/recovery, incomplete-run, causal-consolidation,
+  and link-preview surfaces. CLI typecheck passed.
+- Clean package builds passed in dependency order for `@omnius/execution`,
+  `@omnius/orchestrator`, and `omnius` after each package's clean script.
+- Full CLI suite is not green in this restricted environment: 283 test files
+  passed and 29 failed; 2,674 tests passed, 94 failed, and 276 skipped. Dominant
+  failures are `listen EPERM`, `spawnSync ... EPERM`, and writes beneath the
+  read-only `/home/roko/.omnius*`; unrelated dirty-tree contract expectations
+  also fail. Every WO-57-focused regression passed within this run.
+- The full orchestrator suite was stopped after a bounded five-minute
+  diagnostic run. Its failures likewise clustered around blocked subprocesses,
+  read-only task state, todo-store lock contention, and unrelated pre-existing
+  tool-exposure changes. The focused WO-57 suite remained green.
+- `git diff --check` passed again after this evidence update.
+- Repository delivery is partial: work-order commit `9bf08824` and wrapped-web
+  receipt commit `31af726c` are already on `origin/main`. The remaining repair
+  cannot be staged or committed in this continuation because `.git` is
+  read-only (`index.lock: Read-only file system`).
+- No live inference, service restart, reminder mutation, or Telegram send was
+  performed. Live acceptance therefore remains open.
+
+### 2026-10-02 — messages 5712/610 follow-up repair
+
+- Read-only incident findings and SHA-256 evidence inventory are preserved at
+  `.aiwg/forensics/findings/telegram-2026-10-02-router-delivery.md`.
+- OMNIUS message 5712 is now structurally ineligible for quick chat. Its direct
+  mention plus explicit thread-data retrieval request is promoted to action;
+  the fresh action planner must select scoped tools before a reply can finish.
+- Case Theory message 610 is recognized as the same sender's bounded follow-up
+  to reminder-list request 609 and receives `reminder` with a `read_only`
+  observation/visible-response contract. Public reply authority is still
+  independently reviewed.
+- Router-unavailable decisions now retain the exact host input ID. The active-
+  runner path schedules recovery before social delivery/commit; an unavailable
+  diagnostic may still be displayed to the operator without becoming durable
+  social judgment.
+- Negative controls preserve ordinary addressed chat, unaddressed ambient data
+  talk, and rejection of a genuinely stale cross-input social decision.
+- Focused validation: 277/277 passed across Telegram Bot API, steering,
+  exact-binding, quick-chat, terminal delivery, reminder, attention, router,
+  cognition/recovery, and streamed-terminal surfaces.
+- CLI typecheck and build passed after the repair.
+- Live runtime remains `omnius@1.0.790`; no deployment, restart, inference
+  request, Telegram send, or live reminder mutation was performed.

package/npm-shrinkwrap.json

@@ -1,12 +1,12 @@
 {
   "name": "omnius",
-  "version": "1.0.790",
+  "version": "1.0.792",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "omnius",
-      "version": "1.0.790",
+      "version": "1.0.792",
       "bundleDependencies": [
         "image-to-ascii"
       ],
@@ -2361,9 +2361,9 @@
       }
     },
     "node_modules/@types/node": {
-      "version": "26.6.3",
-      "resolved": "https://registry.npmjs.org/@types/node/-/node-26.6.3.tgz",
-      "integrity": "sha512-dsqMQQoeTLqu9wynDD00q573mNzso3IdQOAfHRJqLCcmCFPoGo9A1bDpUcv/9tnKpErQWv9uKeGfl37EIS02Yg==",
+      "version": "26.6.4",
+      "resolved": "https://registry.npmjs.org/@types/node/-/node-26.6.4.tgz",
+      "integrity": "sha512-ldVPDCzj7fsaGZrLB0NuHuTvJcsNasysBAqMolr/cgxrLd1xbqxIr3XJiPnHHJUCxj5sNF1vnRj9aWnrVh5Jcg==",
       "license": "MIT",
       "dependencies": {
         "undici-types": "~8.9.0"
@@ -3412,9 +3412,9 @@
       "optional": true
     },
     "node_modules/follow-redirects": {
-      "version": "1.16.0",
-      "resolved": "https://registry.npmjs.org/follow-redirects/-/follow-redirects-1.16.0.tgz",
-      "integrity": "sha512-y5rN/uOsadFT/JfYwhxRS5R7Qce+g3zG97+JrtFZlC9klX/W5hD7iiLzScI4nZqUS7DNUdhPgw4xI8W2LuXlUw==",
+      "version": "1.16.1",
+      "resolved": "https://registry.npmjs.org/follow-redirects/-/follow-redirects-1.16.1.tgz",
+      "integrity": "sha512-FNvFGzoMLWmE6Yj9spb/zjd7yiNCHiAW9/Tg9CXrQ8wuu32HtlJOwWO11OJafl5FfY3DxTdQ0vj42zU1kvv5jg==",
       "funding": [
         {
           "type": "individual",
@@ -3795,9 +3795,9 @@
       "license": "BSD-3-Clause"
     },
     "node_modules/ignore": {
-      "version": "7.0.10",
-      "resolved": "https://registry.npmjs.org/ignore/-/ignore-7.0.10.tgz",
-      "integrity": "sha512-HpbUakT7xp5miBUywCHf36ZEuAJNklBJDDsGpUIjMzOSmM8ELSfA9Sa/QDPeNeqeoN31u+UTCkL4klCOVvRm4Q==",
+      "version": "7.0.11",
+      "resolved": "https://registry.npmjs.org/ignore/-/ignore-7.0.11.tgz",
+      "integrity": "sha512-YChdK5txDjwGUvgR7oCJcLGkwi3LDh8Zx8tS7ndYciLEg/oOCL26VUBSUEtgS7EjiybcBqFxh5j0rAdDX7/bbg==",
       "license": "MIT",
       "engines": {
         "node": ">= 4"

package/package.json

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