omnius 1.0.795 → 1.0.797

package/dist/index.js

@@ -1,4 +1,4 @@
 [diffend] Oversized file quarantined before diffing.
 name: package/dist/index.js
-size: 39183834 bytes
-sha256: f7f23898e576627ce93dab3197146494341cc1141e064dad36e55c352216201e
+size: 39269568 bytes
+sha256: addd7fca63e49ee84b631e268135c959c4c4c475228b4e649fc2dd20eb3382ca

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: post-1.0.794 scope and OMNIUS-continuation repairs implemented in the 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, ",
+      "summary": "Status: 1.0.796 Case Theory continuation regression confirmed live; REQ-TDT-014 implementation and validation in progress; 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",
       "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: post-1.0.794 scope and OMNIUS-continuation repairs implemented in the 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,  |
+| `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.796 Case Theory continuation regression confirmed live; REQ-TDT-014 implementation and validation in progress; 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 |
 | `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,8 +1,8 @@
 # WO-57: Telegram delivery truth, reminder authority, and bounded recovery
 
-**Status:** post-1.0.794 scope and OMNIUS-continuation repairs implemented in
-the working tree; focused validation green; full-suite, repository-delivery,
-and live acceptance gates remain open
+**Status:** 1.0.796 Case Theory continuation regression confirmed live;
+REQ-TDT-014 implementation and validation in progress; 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
@@ -73,6 +73,24 @@ logging data now.`, and was marked consumed without a retrieval run.
       direct addressee in the open-task thread, but the host boundary required
       a literal mention/reply edge and left it in quick chat. Message 5720 said
       `pulling it now. one sec.`; no action run or data result followed.
+- [x] Anchor the 1.0.795 continuation regression: the durable task remained
+      open under thread `5697`, while messages 5721 and 5723 arrived at the
+      chat root (`0`). Message 5721 (`pull it`) received an exact typed
+      direct-turn decision but escaped to quick chat because it elided the
+      data noun; message 5722 repeated `pulling it now. one sec.` with no
+      action. Message 5723 (`pull it and give me the fucking data`) then failed
+      the attention-router contract and received no reply or action at all.
+- [x] Anchor the 1.0.796 Case Theory batch-document regression: message 642
+      opened task `tgtask-3f98bf45a97a892330ae`, inspected four time cards,
+      retained a grounded partial reply candidate, and then stranded both the
+      candidate and the remaining document work when fresh terminal review
+      was unavailable.
+- [x] Anchor the exact 1.0.796 follow-up failure: message 644 directly
+      mentioned the bot and said `confirm you can see all of the above files,
+    please follow her instructions`, but the explicit-continuation grammar
+      did not recognize delegated task continuation. The same router decision
+      was retried three times and the intake was marked failed without an
+      action run or public reply.
 
 Runtime evidence:
 
@@ -90,6 +108,9 @@ Runtime evidence:
 - `/home/roko/Documents/Projects/Adjacent/telegram_test/.omnius/telegram-runner-state/84e4e6e5411c97531047/completion-finalizations/telegram-84e4e6e5411c9753-1790928285562-1.json`
 - `/home/roko/Documents/Projects/Adjacent/telegram_test/.omnius/telegram-turn-delivery-ledger/a607485959cb9f27313e04bd289eb590d3daa65cf8e751a6262246311ebe1463.json`
 - `/home/roko/Documents/Projects/Adjacent/telegram_test/.omnius/telegram-runner-state/84e4e6e5411c97531047/tool-results/b2fbc630.txt`
+- `/home/roko/Documents/Projects/Adjacent/telegram_test/.omnius/telegram-intake/f39b2cf564299c28fc81.jsonl`
+- `/home/roko/Documents/Projects/Adjacent/telegram_test/.omnius/telegram-social-events/f39b2cf564299c28fc81b388.jsonl`
+- `/home/roko/Documents/Projects/Adjacent/telegram_test/.omnius/telegram-runner-state/84e4e6e5411c97531047/tool-results/d1601e4c.txt`
 
 ## Requirements and implementation checklist
 
@@ -233,6 +254,9 @@ Primary anchors:
       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] When the host constructs a trusted reminder action from a rejected router
+      decision, replace even a nonempty stale router input ID with the exact
+      current evidence-packet input ID before the action reaches commit.
 - [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
@@ -344,6 +368,84 @@ Primary anchors:
   open-task data-continuation boundary.
 - `packages/cli/tests/telegram-steering-finalization.test.ts`
 
+### REQ-TDT-013 — elided task continuations survive reply-thread transitions
+
+- [x] Resolve an explicit retrieval/completion continuation against the exact
+      open task first, or against the sole unresolved task in the same public
+      chat only when the current message has no native topic ID; never bridge
+      from one explicit topic to another or choose among multiple open tasks.
+- [x] Put that bound task in the exact-current router evidence packet so the
+      router and action planner see the real objective rather than `none`.
+- [x] Treat an object-elided retrieval imperative such as `pull it` as action
+      work only when it is bound to that task and has exact typed direct-turn,
+      native address, or exact adjacent bot-turn authority.
+- [x] Preserve an adjacent bot reply to the same sender as deterministic
+      direct-turn evidence when router reconciliation fails; still require the
+      independent public reply-authority review before any group response.
+- [x] Keep another-topic, multiple-task, other-actor, non-adjacent, and
+      ordinary ambient-talk controls outside the repair.
+- [x] Replay exact OMNIUS messages 5721 and 5723 with the real task stored at
+      thread `5697`; assert neither can enter quick chat or disappear silently.
+
+Primary anchors:
+
+- `packages/cli/src/tui/telegram-bridge.ts` — explicit-continuation task
+  binding, exact evidence, and trusted action boundary.
+- `packages/cli/tests/telegram-steering-finalization.test.ts`
+
+### REQ-TDT-014 — durable arbitrary-depth intake, batch objectives, and terminal handoff
+
+- [ ] Treat a native direct mention/reply/private delivery as host-owned intake
+      authority. Invalid attention-router or action-plan JSON may not discard
+      that exact input; semantic interpretation belongs to the capable runner,
+      with ambient group traffic still using the attention router.
+- [ ] Present every exact-scope durable open objective to that runner as
+      structured state, so ordinary language can continue, delegate, amend,
+      replace, or query it without a host phrase dictionary. Any model-selected
+      continuation must cite one unambiguous task and preserve its boundaries.
+- [ ] Preserve the original task owner, task ID, objective, evidence, media
+      scope, and remaining work while binding the newer input as response
+      authority; do not create a second root task or silently replace the
+      original file-analysis objective.
+- [ ] Require explicit current-turn bot address plus a read-only retained task
+      for cross-actor delegation. Keep mutation tasks, ambiguous multiple
+      tasks, foreign chats/topics, unaddressed talk, and wait/defer language
+      outside deterministic repair.
+- [ ] Resume the retained objective without restoring a stale partial reply as
+      proof that the full batch is complete. A partial candidate may be used
+      only as evidence already gathered and must remain labelled partial until
+      every required file has been processed or a truthful blocker is sent.
+- [ ] When object work reaches a current, verified candidate and the only
+      missing effect is Telegram visibility, make the terminal handoff durable
+      across review failure without restarting completed file reads or losing
+      the response owner.
+- [ ] Persist the scoped action plan/capability set and terminal-review
+      checkpoint with the objective. Recovery must resume the last incomplete
+      state transition; it must not restart attention, planning, or completed
+      object work.
+- [ ] Derive itemized completion criteria for a selected attachment set. One
+      generic observation cannot satisfy a multi-document request, and
+      advisory no-delta review cannot turn a partial checklist into
+      `deliver_due`.
+- [ ] Prove all admitted attachments are durably enumerable and resolvable
+      from Telegram `file_id` metadata after process restart or local byte-cache
+      expiry. Enumeration must paginate beyond one bounded page, and each
+      successful inspection must receipt the exact message/file criterion.
+- [ ] Replay the exact 642 -> 644 Case Theory topology, including Mariana as
+      task owner and robitman as the directly addressing delegator, and assert
+      one continued action task, no quick-chat acknowledgement, no router-only
+      exhaustion, and one final exact-scope response.
+
+Primary anchors:
+
+- `packages/cli/src/tui/telegram-bridge.ts` — delegated-continuation shape,
+  retained-task handoff, candidate/evidence restoration, and terminal recovery.
+- `packages/cli/tests/telegram-steering-finalization.test.ts`
+- `packages/cli/tests/telegram-objective-resume.test.ts`
+- `packages/cli/tests/telegram-terminal-delivery.test.ts`
+- `packages/cli/tests/telegram-terminal-metacognition.test.ts`
+- `packages/cli/tests/telegram-media-admission.test.ts`
+
 ## Cross-surface validation gates
 
 - [x] Orchestrator focused tests pass for visible-response evidence, completion
@@ -381,6 +483,8 @@ Primary anchors:
 | REQ-TDT-010 | continuation + control-plane convergence         | 5717/612 + exact review contract                   | focused green |
 | REQ-TDT-011 | reminder read/write scope authorization          | group/DM/topic/foreign-ID isolation                | focused green |
 | REQ-TDT-012 | typed direct-turn action continuation            | exact OMNIUS 5719 + ambient controls               | focused green |
+| REQ-TDT-013 | elided cross-thread task continuation            | exact OMNIUS 5721/5723 + scope controls            | focused green |
+| REQ-TDT-014 | delegated batch continuation + terminal handoff  | Case Theory 642/644 + scope/batch controls         | in progress   |
 
 ## Evidence log
 
@@ -598,7 +702,7 @@ Primary anchors:
   Its exact typed decision identified the bot as direct addressee and cited the
   current message, but the host boundary recognized only literal mentions and
   Telegram reply edges. Quick chat delivered message 5720 (`pulling it now.
-  one sec.`) without an action run or data result.
+one sec.`) without an action run or data result.
 - Typed exact-current direct-turn authority now counts as bot address only when
   a real decision ID, non-unavailable source, self actor key, addressee role,
   direct-turn basis, and current-message evidence all agree. The exact 5719
@@ -609,3 +713,50 @@ Primary anchors:
   Execution and CLI typechecks/builds passed; `git diff --check` passed.
 - These repairs are not in installed 1.0.794. No publish, install, restart,
   Telegram send, or live inference was performed by this session.
+
+### 2026-10-02 — live 1.0.795 OMNIUS continuation regression and repair
+
+- Installed `omnius@1.0.795` remained healthy in polling with replay backlog
+  zero, but OMNIUS task `tgtask-8942677c856ffedaa509` was still open under
+  thread `5697` while follow-ups arrived at root thread `0`.
+- Message 5721 (`pull it`) received exact-current direct-turn decision
+  `tgdec-31270552314194f33fce`, entered zero-tool quick chat, and delivered
+  message 5722 (`pulling it now. one sec.`) without action or data.
+- Message 5723 (`pull it and give me the fucking data`) then exhausted its
+  typed attention contract and was marked failed with no reply or action.
+- The repair resolves only an exact task or the sole unresolved same-chat task
+  from a root turn, includes it in the router packet, accepts an elided
+  retrieval referent, and uses the immediately preceding bot reply to that
+  same sender as bounded direct-turn evidence. Explicit other topics,
+  ambiguous multi-task chats, and other-actor decisions remain excluded.
+- A continuation reuses the cited task identity and current action contract
+  without restoring its stale verified reply candidate or stale effects; this
+  prevents the repaired first turn from creating a second ambiguous root task.
+- Validation: 221/221 focused CLI tests passed across steering/finalization,
+  attention evidence, reminder scope, and Bot API surfaces. CLI typecheck and
+  build passed; `git diff --check` passed. The exact 5721/5723 replay tests use
+  the live `5697 -> 0` topology.
+- The live runtime is still installed 1.0.795. No publish, install, restart,
+  Telegram send, or live inference was performed by this session.
+
+### 2026-10-02 — Case Theory message 610 stale-input root repair
+
+- The reminder-list action repair previously preserved a rejected router
+  `input_id` whenever it was nonempty. For message 610 that retained the stale
+  or malformed identity through semantic repair, so the exact-input commit
+  guard correctly rejected the otherwise valid action and the chat went
+  silent.
+- Host-authored reminder action repair now always takes identity from the
+  current host evidence packet. Router-unavailable decisions are likewise
+  constructed with the exact host input; the commit boundary remains strict
+  and does not accept or normalize arbitrary model identities.
+- Reminder authorization remains exact by surface, target chat, and topic for
+  both reads and mutations. Foreign complete/dismiss/snooze IDs fail as
+  ordinary not-found records, while members of the same group/topic retain
+  their intended shared view.
+- Independent validation: 51/51 focused CLI tests passed across social binding,
+  steering/finalization, and reminder contracts; 74/74 execution temporal-
+  agency tests passed; CLI and execution typechecks plus `git diff --check`
+  passed.
+- No publish, install, service restart, Telegram send, or live inference was
+  performed by this validation.

package/npm-shrinkwrap.json

@@ -1,12 +1,12 @@
 {
   "name": "omnius",
-  "version": "1.0.795",
+  "version": "1.0.797",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "omnius",
-      "version": "1.0.795",
+      "version": "1.0.797",
       "bundleDependencies": [
         "image-to-ascii"
       ],
@@ -3795,9 +3795,9 @@
       "license": "BSD-3-Clause"
     },
     "node_modules/ignore": {
-      "version": "7.0.11",
-      "resolved": "https://registry.npmjs.org/ignore/-/ignore-7.0.11.tgz",
-      "integrity": "sha512-YChdK5txDjwGUvgR7oCJcLGkwi3LDh8Zx8tS7ndYciLEg/oOCL26VUBSUEtgS7EjiybcBqFxh5j0rAdDX7/bbg==",
+      "version": "7.0.12",
+      "resolved": "https://registry.npmjs.org/ignore/-/ignore-7.0.12.tgz",
+      "integrity": "sha512-/8UvqAPU9DGTI9k4mxtf49U37Isfwr8Uts96+SBHIkFxPJnHS0Ew4f00sM4Scd8V8EjM0jUNtVDdv1kPdt35lg==",
       "license": "MIT",
       "engines": {
         "node": ">= 4"
@@ -5741,16 +5741,16 @@
       }
     },
     "node_modules/sharp/node_modules/tar-stream": {
-      "version": "3.2.1",
-      "resolved": "https://registry.npmjs.org/tar-stream/-/tar-stream-3.2.1.tgz",
-      "integrity": "sha512-nqsEO8zLZJvrOMdEwkA0QdCLFbetHMn95Zqu4fKwX+hkaTWJPZZOrxx/PwtxoK0MMGQmBQNRW3CPs8IFYQz4cQ==",
+      "version": "3.2.2",
+      "resolved": "https://registry.npmjs.org/tar-stream/-/tar-stream-3.2.2.tgz",
+      "integrity": "sha512-+8NeqHRjQWH9nYlwo2gamAMImZCVzI4UoEgDpWorBt9OEfppiZn+uSkskzQKPWIZyji/C8fpWO7u69G0DX0tbg==",
       "license": "MIT",
       "optional": true,
       "dependencies": {
-        "b4a": "^1.6.4",
-        "bare-fs": "^4.5.5",
-        "fast-fifo": "^1.2.0",
-        "streamx": "^2.15.0"
+        "b4a": "^1.9.0",
+        "bare-fs": "^4.8.2",
+        "fast-fifo": "^1.3.2",
+        "streamx": "^2.28.1"
       }
     },
     "node_modules/simple-concat": {

package/package.json

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