omnius 1.0.791 → 1.0.793

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: 39178099 bytes
+sha256: 77c9e3b8094d90a3f91db155f9e28ee0a3dfad588bb03538608f284fbc768c27

package/docs/DISCOVERY.json

@@ -35906,7 +35906,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: 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",
+      "summary": "Status: implementation and post-1.0.792 recovery repair complete in working tree; focused validation green; full-suite, repository-delivery, and live acceptance 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-",
       "keywords": [
         "work",
         "orders",

package/docs/DISCOVERY.md

@@ -609,7 +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-runtime-health-remediation-wo-57-telegram-delivery-truth-and-recovery-uppercase` | WO-57: Telegram delivery truth, reminder authority, and bounded recovery | Status: implementation and post-1.0.792 recovery repair complete in working tree; focused validation green; full-suite, repository-delivery, and live acceptance 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- |
 | `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/WO-57-telegram-delivery-truth-and-recovery.md

@@ -1,7 +1,8 @@
 # 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
+**Status:** implementation and post-1.0.792 recovery repair complete in working
+tree; focused validation green; full-suite, repository-delivery, and live
+acceptance gates remain open
 **Priority:** P0
 **Incident:** October 1, 2026, live Telegram reminder and illegal-logging non-responses
 **Owner:** Omnius orchestrator and Telegram runtime
@@ -35,6 +36,22 @@ 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`.
+- [x] Anchor the partial 1.0.792 result: the runtime restarted at
+      `2026-10-02T06:57:21.994Z` with healthy polling, but the recovered Case
+      Theory message 611 retained its pre-update `outcome:"delivery"`
+      contract, read all 29 reminders, authored the complete answer, then
+      rejected itself for missing the Telegram delivery effect.
+- [x] Anchor bounded-recovery exhaustion: message 611 repeated `reminder`,
+      `tool_search`, and unrelated `file_read` work, ended
+      `incomplete_verification` twice, and was terminally failed at
+      `2026-10-02T07:19:30.188Z` after three cycles with no public reply.
 
 Runtime evidence:
 
@@ -43,6 +60,10 @@ Runtime evidence:
 - `/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`
+- `/home/roko/Documents/Projects/Adjacent/telegram_test/.omnius/telegram-runner-state/84e4e6e5411c97531047/debug-library/runs/telegram-84e4e6e5411c9753-1790924323167-1/events.jsonl`
+- `/home/roko/Documents/Projects/Adjacent/telegram_test/.omnius/telegram-runner-state/84e4e6e5411c97531047/completion-finalizations/telegram-84e4e6e5411c9753-1790924323167-1.json`
+- `/home/roko/Documents/Projects/Adjacent/telegram_test/.omnius/telegram-runner-state/84e4e6e5411c97531047/debug-library/runs/telegram-84e4e6e5411c9753-1790925147229-1/events.jsonl`
+- `/home/roko/Documents/Projects/Adjacent/telegram_test/.omnius/telegram-runner-state/84e4e6e5411c97531047/completion-finalizations/telegram-84e4e6e5411c9753-1790925147229-1.json`
 
 ## Requirements and implementation checklist
 
@@ -178,6 +199,53 @@ 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.
+
+### REQ-TDT-009 — recovered-contract migration and convergence
+
+- [x] Prefer a current deterministic host-repaired contract over a stale
+      persisted contract when recovering the exact same Telegram input.
+- [x] Preserve fail-closed external file/media delivery contracts; only typed
+      `host-contract-repair` authority can migrate an exact recovered task.
+- [x] Do not consume the one-shot `deliver_due` synthesis instruction before a
+      required grounded observation exists.
+- [x] Make `bounded_review` authoritative in deferred external-effect mode so
+      a no-delta plateau cannot continue into unrelated tool families.
+- [x] Add regressions for exact contract migration, grounded synthesis timing,
+      and bounded no-delta enforcement.
+
+Primary anchors:
+
+- `packages/cli/src/tui/telegram-bridge.ts` — exact recovery contract selection
+  and evidence-gated synthesis.
+- `packages/orchestrator/src/agenticRunner.ts` — objective admission at bounded
+  review.
+- `packages/cli/tests/telegram-objective-resume.test.ts`
+- `packages/cli/tests/telegram-bot-api-10.test.ts`
+- `packages/orchestrator/tests/agenticRunner-objective-control.test.ts`
+
 ## Cross-surface validation gates
 
 - [x] Orchestrator focused tests pass for visible-response evidence, completion
@@ -201,15 +269,17 @@ Primary anchors:
 
 ## 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 |
+| 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 |
+| REQ-TDT-009 | recovered-contract migration + convergence gates | exact recovery + synthesis timing + bounded review | focused green |
 
 ## Evidence log
 
@@ -316,3 +386,65 @@ 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.
+- At this checkpoint the live runtime remained `omnius@1.0.790`; no deployment,
+  restart, inference request, Telegram send, or live reminder mutation was
+  performed by this repair session.
+
+### 2026-10-02 — live 1.0.792 recovery finding and follow-up repair
+
+- The user-owned runtime updated to `omnius@1.0.792` and restarted at
+  `2026-10-02T06:57:21.994Z`. Its health record remained in `polling` with zero
+  consecutive poll failures and no replay backlog. This session did not start,
+  stop, or send through that process.
+- Version 1.0.792 contains the fresh-request boundary for message-5712-shaped
+  thread-data retrieval, so a new request cannot complete as a zero-tool
+  progress acknowledgement. A bare follow-up cannot reconstruct work already
+  orphaned by the pre-update runtime.
+- Restart recovery exposed a separate exact-task migration bug. Message 611's
+  current host boundary selected reminder `read_only` semantics, but
+  `telegramExpectedOutcomeContractForRun` preferred the persisted pre-update
+  `delivery` contract. Both post-restart attempts observed 29 reminders and
+  authored the roster, then failed readiness solely on missing `delivery`.
+- The recovery attempts also consumed `deliver_due` guidance before grounded
+  evidence and admitted `tool_search`/`file_read` after the useful reminder
+  result. The final intake state was `failed` after three bounded cycles with
+  no public reply.
+- Exact-input recovery now treats a current `host-contract-repair` contract as
+  the migration authority over the retained legacy contract. Real external
+  delivery contracts retain their receipt requirement.
+- `deliver_due` synthesis now waits for a successful non-control action result,
+  and the orchestrator enforces `bounded_review` even while external-effect
+  enforcement is deferred.
+- Focused validation after the follow-up patch: 200/200 CLI tests passed across
+  objective recovery, terminal delivery, and Telegram Bot API 10; 7/7
+  orchestrator objective-control tests passed; CLI and orchestrator typechecks
+  passed.
+- Broader affected-surface validation: 332/332 tests passed across 16 Telegram
+  suites, and 29/29 passed across four orchestrator completion, steering,
+  response-authority, and objective-control suites. Orchestrator and CLI builds
+  passed after formatting.
+- The follow-up patch is not in the installed 1.0.792 runtime. A new build,
+  version, install, and restart are required before live acceptance can be
+  checked.

package/npm-shrinkwrap.json

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

package/package.json

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