omnius 1.0.791 → 1.0.792

package/dist/index.js

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

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

@@ -35,6 +35,13 @@ verified evidence instead of replaying the full reasoning loop.
 - [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:
 
@@ -178,6 +185,30 @@ Primary anchors:
 - `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
@@ -210,6 +241,7 @@ Primary anchors:
 | 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
 
@@ -316,3 +348,27 @@ Primary anchors:
   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.791",
+  "version": "1.0.792",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "omnius",
-      "version": "1.0.791",
+      "version": "1.0.792",
       "bundleDependencies": [
         "image-to-ascii"
       ],

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "omnius",
-  "version": "1.0.791",
+  "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",