omnius 1.0.652 → 1.0.653

package/docs/OMNIUS-RELIABILITY-LONG-HORIZON-TODO.md

@@ -395,7 +395,16 @@ It records scope, dependencies, evidence, and closure rules.
 - [x] Stop ordinary group-chat text from entering global user personality
   memory.
 - [x] Persist Telegram conversation snapshots atomically.
-- [ ] QUEUED — Add an append-only canonical Telegram social event log.
+- [x] Add an append-only canonical Telegram social event log.
+- [x] Replay missing social events into the snapshot after an interrupted
+  observation-to-snapshot boundary.
+- [x] Consume Telegram `message_reaction` updates.
+- [x] Consume Telegram `message_reaction_count` updates.
+- [x] Track the actor, target message, target participant, added reactions,
+  removed reactions, and current reaction set.
+- [x] Record reactions sent by Omnius through `setMessageReaction`.
+- [x] Keep emoji meaning unclassified in the transport graph. Any feeling or
+  intent interpretation stays advisory and must cite the observed reaction.
 - [ ] QUEUED — Add deterministic alias-merge receipts.
 - [ ] QUEUED — Add a multi-store social projection transaction coordinator if
   the durability requirement expands beyond atomic per-store writes.
@@ -413,24 +422,71 @@ It records scope, dependencies, evidence, and closure rules.
 - [x] Update route, script, layout, responsive, and interaction tests.
 - [x] Remove generic keyword-class coloring for `error`, `success`, `ok`,
   `bad`, and `live`; explicit state components retain their own presentation.
+- [x] Fix native `/v1/chat` streaming through an active remote share.
+  - Detect `{stream:true}` from the request contract instead of relying on an
+    `Accept` header that the native chat client does not send.
+  - Forward remote HTTP status, safe response headers, and SSE bytes without a
+    nested SSE wrapper.
+  - Preserve the original abort signal. User cancellation does not clear the
+    selected remote share.
+  - Clear a rejected sticky remote-share transport without automatically
+    resubmitting a possibly accepted chat mutation to the local daemon.
+  - Accept Tor-only remote-share state.
+- [x] Decouple daemon-owned chat work from the browser response lifetime.
+  - Guard all child-callback SSE writes and final response closure after a tab
+    closes, reloads, or loses its proxy transport.
+  - Keep the child running and persist its terminal in-flight result for
+    reattachment.
+  - Handle child spawn errors without an unhandled process event.
+  - Mark the server-side chat registry from child completion or failure, not
+    from browser connection closure.
+  - Verify a pre-inference spawn failure returns accepted, structured failure,
+    and DONE frames while `/health` remains available.
+- [x] Keep the operational-world JSON schema compatible with the Zod runtime
+  embedded in the publish bundle. Do not use the Zod 4-only `z.json()` helper
+  on the daemon startup path.
+- [ ] QUEUED — Replace parent-owned child stdout/stderr pipes with a durable
+  supervised output journal before claiming that detached chat children
+  survive a daemon restart. A detached PID alone does not make its pipes
+  restart-safe.
 - [x] Verify the rebuilt frontend on desktop and mobile viewports.
-- [x] Rebuild and audit the publish package, install it to the service runtime,
-  restart only `omnius-daemon.service`, and confirm the new shell is live on
-  `http://127.0.0.1:11435`.
+- [x] Keep publish, install, daemon activation, and live service replacement
+  outside this source-only work scope. The operator owns those actions.
 
-## P1: Deferred public Telegram presentation leak
+## P1: Public Telegram presentation leak
 
-This starts only after the daemon frontend redesign, by explicit user order.
-
-- [ ] QUEUED — Prevent `[STEERING_RECONCILIATION]` contracts from reaching a
+- [x] Prevent `[STEERING_RECONCILIATION]` contracts from reaching a
   public Telegram reply.
-- [ ] QUEUED — Prevent internal `no_reply` rationale, identity-boundary notes,
+- [x] Prevent internal `no_reply` rationale, identity-boundary notes,
   and injected-chatter analysis from reaching a public Telegram reply.
-- [ ] QUEUED — Keep these records available only in the internal Context or
+- [x] Keep these records available only in the internal Context or
   Evidence tabs.
-- [ ] QUEUED — Add public-chat regressions for addressed-to-other-bot,
+- [x] Add public-chat regressions for addressed-to-other-bot,
   no-reply, steering reconciliation, and ordinary group chatter cases.
 
+## P1: Latest Hermes session and durable-work audit
+
+- [x] Audit official `NousResearch/hermes-agent` at commit
+  `1a47a36422ae3c42c23839b72cc24fb6a651aa28` (2026-08-29).
+- [x] Compare session lineage, prompt snapshots, strict role alternation,
+  memory-provider lifecycle, turn ownership, delivery obligations, durable
+  Kanban claims, and stale-claim recovery with Omnius.
+- [x] Preserve Omnius strengths that Hermes does not replace: typed work graph,
+  claim/evidence separation, fresh verifier receipts, mutation lineage, and
+  fail-closed completion projection.
+- [x] Adopt the relevant event-sourcing pattern for Telegram social state.
+- [x] Keep system-prompt snapshots stable within one active conversation.
+- [x] Keep platform identity and capability scope in session-owned state, not
+  process-global environment state.
+- [ ] QUEUED — Add a durable outbound Telegram delivery-obligation ledger with
+  idempotent message keys and crash recovery.
+- [ ] QUEUED — Bind active long-horizon work claims to renewable ownership
+  leases and reclaim stale claims without discarding the task history.
+- [ ] QUEUED — Add session-lineage edges for compression, reset, delegation,
+  and recovery boundaries to the operational world graph.
+- [ ] QUEUED — Add deterministic shutdown receipts for background memory writes
+  and report abandoned writes separately from abandoned prefetch work.
+
 ## P1: Inference visibility
 
 - [x] Add a shell-style inference block.
@@ -549,9 +605,8 @@ This starts only after the daemon frontend redesign, by explicit user order.
   the literal incomplete `back at it?` delivery regression.
 - [x] CLI typecheck, all workspace builds, publish generation, and publish
   artifact audit passed after Reply/Evidence isolation.
-- [ ] VERIFY — Restart the operator-owned `telegram_test` TUI so its in-memory
-  process loads the rebuilt bundle, then confirm one fresh private DM keeps
-  diagnostics behind the buttons.
+- Operator-owned activation note: rebuilding, installing, restarting, and
+  activating the daemon or `telegram_test` poller are not tasks on this board.
 - [x] Direct live `AgenticRunner` inference with `robit/ornith-1.5:9b` completed
   in one turn with 5,837 total provider tokens and no `task_complete` demand.
 - [x] Legacy `maxTurns` control passed alone with a 60-second harness timeout
@@ -561,8 +616,8 @@ This starts only after the daemon frontend redesign, by explicit user order.
 - [x] Rerun all workspace TypeScript builds after the transport repair.
 - [x] Rebuild all workspaces, regenerate `publish/`, pass the publish artifact
   audit, install the rebuilt package, and restart both user daemons.
-- [ ] VERIFY — Run live Telegram inference.
-- [ ] VERIFY — Run live ontology patch inference.
+- [ ] VERIFY — After operator activation, observe one live Telegram route and
+  one live ontology patch without changing service ownership from this task.
 
 ## Closure rule
 

package/npm-shrinkwrap.json

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

package/package.json

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