omnius 1.0.794 → 1.0.796

package/dist/index.js

@@ -1,4 +1,4 @@
 [diffend] Oversized file quarantined before diffing.
 name: package/dist/index.js
-size: 39181622 bytes
-sha256: 54ef7bafed127f8a19146f9400d3123bc77d3f6d92914b0d97d19538cda7f938
+size: 39188965 bytes
+sha256: 57f79f926d323fe8b5febd27e8476071fa9dc33c1e0e4c76457050a474c489d2

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 and post-1.0.793 control-plane 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",
+      "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, ",
       "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 and post-1.0.793 control-plane 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 |
+| `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-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:** implementation and post-1.0.793 control-plane repair complete in
-working tree; focused validation green; full-suite, repository-delivery, and
-live acceptance gates remain open
+**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
@@ -17,7 +17,9 @@ 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.
+verified evidence instead of replaying the full reasoning loop. A scoped
+reminder tool must never read or mutate reminders owned by another chat, topic,
+surface, or unscoped/global context.
 
 ## Baseline and live evidence
 
@@ -61,6 +63,23 @@ logging data now.`, and was marked consumed without a retrieval run.
       29 reminders, reached `deliver_due` at `2026-10-02T08:06:58.242Z`, then
       admitted `tool_search` and `file_read`, completed with the full answer,
       rejected its terminal review, and started a whole-task recovery cycle.
+- [x] Anchor the 1.0.794 scope breach: recovered message 612 called the locked
+      Case Theory reminder tool with `action:"list", filter:"all"`; the tool
+      returned the shared 29-reminder registry even though only four records
+      belonged to chat `-1003960149435`. Telegram message 614 then disclosed
+      reminder IDs and titles from OMNIUS and the requester's private DM.
+- [x] Anchor the remaining 1.0.794 OMNIUS regression: message 5719 said
+      `please pull the data`; its exact typed decision identified the bot as
+      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.
 
 Runtime evidence:
 
@@ -76,6 +95,8 @@ Runtime evidence:
 - `/home/roko/Documents/Projects/Adjacent/telegram_test/.omnius/telegram-turn-delivery-ledger/0f3dd3a8bebe1933d1d468175da402e64138954fcc52a8126512426297641ddf.json`
 - `/home/roko/Documents/Projects/Adjacent/telegram_test/.omnius/telegram-runner-state/84e4e6e5411c97531047/debug-library/runs/telegram-84e4e6e5411c9753-1790928285562-1/events.jsonl`
 - `/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`
 
 ## Requirements and implementation checklist
 
@@ -219,6 +240,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
@@ -284,6 +308,77 @@ Primary anchors:
 - `packages/cli/tests/telegram-terminal-metacognition.test.ts`
 - `packages/cli/tests/telegram-reminder-contract.test.ts`
 
+### REQ-TDT-011 — reminder scope is a read/write authorization boundary
+
+- [x] Enforce a locked reminder scope before listing records; `filter:"all"`
+      means every status inside the authorized scope, never every reminder in
+      the shared store.
+- [x] Enforce the same scope before complete, dismiss, or snooze mutations.
+      A foreign reminder ID must return the ordinary not-found result without
+      revealing that the record exists and without changing it.
+- [x] Canonicalize access by surface, target chat, and exact topic identity.
+      A group root, one topic, another group, a private DM, another surface,
+      and an unscoped record are mutually inaccessible from a locked context.
+- [x] Treat `userId`, username, owner, and label as metadata rather than public
+      group visibility keys so reminders remain shared within their group/topic.
+- [x] Preserve deliberately unlocked/global reminder administration behavior.
+- [x] Add execution regressions for group/DM/topic/unscoped list isolation and
+      cross-scope complete/dismiss/snooze rejection, plus a Telegram adapter
+      regression proving Case Theory cannot observe OMNIUS or private reminders.
+
+Primary anchors:
+
+- `packages/execution/src/tools/reminder.ts` — authoritative scope predicate for
+  all reminder reads and mutations.
+- `packages/execution/tests/tools/temporal-agency.test.ts`
+- `packages/cli/src/tui/telegram-bridge.ts` — locked current-chat tool adapter.
+- `packages/cli/tests/telegram-reminder-contract.test.ts`
+
+### REQ-TDT-012 — typed direct-turn continuation cannot acknowledge object work
+
+- [x] Treat an exact-current typed decision as direct bot address when its
+      self role is `addressee`, reply basis is `direct_turn`, addressed actors
+      contain the bot, and evidence cites the current message.
+- [x] When that authority accompanies an explicit thread-data request, require
+      action planning even without a literal `@mention` or Telegram reply edge.
+- [x] Cite the exact durable open task when present and clear any chat plan so
+      the scoped action planner must select capabilities before replying.
+- [x] Keep ambient/unaddressed human data talk and decisions addressed to a
+      different actor outside this repair.
+- [x] Replay exact OMNIUS message 5719 and assert it cannot enter quick chat or
+      emit a progress acknowledgement without an action plan.
+
+Primary anchors:
+
+- `packages/cli/src/tui/telegram-bridge.ts` — typed direct-turn address and
+  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`
+
 ## Cross-surface validation gates
 
 - [x] Orchestrator focused tests pass for visible-response evidence, completion
@@ -319,6 +414,9 @@ Primary anchors:
 | 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 |
 | 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 |
 
 ## Evidence log
 
@@ -516,3 +614,81 @@ Primary anchors:
   CLI typecheck, build, and `git diff --check` passed.
 - The installed 1.0.793 runtime does not contain this REQ-TDT-010 repair. Live
   acceptance remains open until a rebuilt package is installed and restarted.
+
+### 2026-10-02 — live 1.0.794 scope breach and remaining OMNIUS regression
+
+- The user-owned runtime started globally installed `omnius@1.0.794`; installed
+  bundle SHA-256 was
+  `54ef7bafed127f8a19146f9400d3123bc77d3f6d92914b0d97d19538cda7f938`.
+- Case Theory message 612 recovered, observed the shared 29-reminder store, and
+  delivered Telegram message 614. Only four records belonged to Case Theory;
+  the tool result also contained three OMNIUS, one Po3 Clock, eighteen private
+  Telegram, and three private TUI records. The delivered reply exposed OMNIUS
+  and private reminder IDs/titles while showing no Case Theory record.
+- Root ownership was `ReminderTool`: `lockScope` constrained `set` but
+  `list`, `complete`, `dismiss`, and `snooze` selected from the global store.
+  The repair now applies one exact surface/target/topic authorization predicate
+  before every read and ID mutation. Foreign IDs return the ordinary not-found
+  result and remain unchanged; unlocked administration retains global access.
+- OMNIUS message 5719 (`please pull the data`) remained a separate regression.
+  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.
+- 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
+  replay is promoted to action, cites its open task, clears the chat plan, and
+  cannot use quick chat; an other-actor control remains unchanged.
+- Validation: 74/74 execution temporal-agency tests and 204/204 Telegram tests
+  passed across reminder scope, steering/finalization, and Bot API surfaces.
+  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.794",
+  "version": "1.0.796",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "omnius",
-      "version": "1.0.794",
+      "version": "1.0.796",
       "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.794",
+  "version": "1.0.796",
   "description": "AI coding agent powered by open-source models (Ollama/vLLM) — interactive TUI with agentic tool-calling loop",
   "type": "module",
   "main": "./dist/library.js",