omnius 1.0.690 → 1.0.692

package/docs/DISCOVERY.json

@@ -33864,6 +33864,82 @@
         }
       ]
     },
+    {
+      "id": "guide.work-orders-runtime-health-remediation-wo-22-autocomplete-footer-geometry-uppercase",
+      "kind": "guide",
+      "title": "WO-22: Autocomplete Footer Geometry Integrity",
+      "summary": "Scope: CLI TUI footer, DirectInput redraw scheduling, active content writes",
+      "keywords": [
+        "work",
+        "orders",
+        "runtime",
+        "health",
+        "remediation",
+        "WO",
+        "22",
+        "autocomplete",
+        "footer",
+        "geometry",
+        "md"
+      ],
+      "maturity": "internal",
+      "audiences": [
+        "maintainer",
+        "large-context-agent"
+      ],
+      "layer": "documentation",
+      "interfaces": [
+        {
+          "type": "file",
+          "target": "docs/work-orders/runtime-health-remediation/WO-22-autocomplete-footer-geometry.md"
+        }
+      ],
+      "references": [
+        {
+          "type": "documentation",
+          "target": "docs/work-orders/runtime-health-remediation/WO-22-autocomplete-footer-geometry.md",
+          "relation": "canonical-artifact"
+        }
+      ]
+    },
+    {
+      "id": "guide.work-orders-telegram-dmn-wo-22-dmn-outreach-and-learning-uppercase",
+      "kind": "guide",
+      "title": "WO-22: DMN outreach, DM sharing, and outcome learning",
+      "summary": "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.",
+      "keywords": [
+        "work",
+        "orders",
+        "telegram",
+        "dmn",
+        "WO",
+        "22",
+        "dmn",
+        "outreach",
+        "and",
+        "learning",
+        "md"
+      ],
+      "maturity": "internal",
+      "audiences": [
+        "maintainer",
+        "large-context-agent"
+      ],
+      "layer": "documentation",
+      "interfaces": [
+        {
+          "type": "file",
+          "target": "docs/work-orders/telegram-dmn/WO-22-dmn-outreach-and-learning.md"
+        }
+      ],
+      "references": [
+        {
+          "type": "documentation",
+          "target": "docs/work-orders/telegram-dmn/WO-22-dmn-outreach-and-learning.md",
+          "relation": "canonical-artifact"
+        }
+      ]
+    },
     {
       "id": "guide.work-orders-telegram-dropbear-context-rca-workorder",
       "kind": "guide",

package/docs/DISCOVERY.md

@@ -560,6 +560,8 @@ Daemon equivalents are `GET /v1/discovery/bootstrap`, `GET /v1/discovery?q=<inte
 | `guide.work-orders-runtime-health-remediation-wo-19-clean-build-reproducibility-uppercase` | WO-19: Clean Build and Optional-Dependency Reproducibility | Status: deterministic acceptance complete Risk: medium Depends on: WO-00 |
 | `guide.work-orders-runtime-health-remediation-wo-20-exact-session-continuation-uppercase` | WO-20: Exact session continuation across exit and restart | On 2026-09-03, the telegramtest TUI displayed the latest pentest task during startup, but the first restored model context combined a completed breach.py handoff with an unrelated, older page.tsx todo tree. The user then entered continue, and Omnius continued the stale tree instead of the task that was active before /quit. |
 | `guide.work-orders-runtime-health-remediation-wo-21-task-convergence-and-todo-scope-uppercase` | WO-21: Task convergence and todo scope | On 2026-09-03, a user reported that Omnius remained at task 2/8 for about 40 turns. The report did not include a screenshot or run artifact, so the exact label remains unverified. Omnius has two similar counters: |
+| `guide.work-orders-runtime-health-remediation-wo-22-autocomplete-footer-geometry-uppercase` | WO-22: Autocomplete Footer Geometry Integrity | Scope: CLI TUI footer, DirectInput redraw scheduling, active content writes |
+| `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-wo-am-gaps-uppercase` | Associative Memory Gap Work Orders | Generated: 2026-04-13 Source: Deep audit of multimodal associative memory systems Status: READY FOR IMPLEMENTATION |
 | `guide.work-orders-world-class-memory-compiler-readme-uppercase` | World-Class Memory Compiler Program | Status: active implementation program Owner: Omnius orchestration and memory packages Last updated: 2026-07-13 |

package/docs/work-orders/runtime-health-remediation/TRACKER.md

@@ -320,6 +320,15 @@ deterministically repaired P0 or P1 defect.
   - [x] Latch an advisory convergence review when the leaf frontier is static.
   - [x] Make loop, reminder, budget, and workboard progress semantics truthful.
   - [x] Pass deterministic race, stasis, display, typecheck, and build tests.
+- [x] WO-22 autocomplete footer geometry uses the last painted layout as its
+  terminal authority and clears all released rows during idle and active-stream
+  contraction.
+  - [x] Trace the deferred DirectInput repaint and content-write ordering race.
+  - [x] Confirm existing tests do not model final terminal cells in this path.
+  - [x] Unify idle and streaming geometry transitions around deterministic
+    replay.
+  - [x] Cover precommitted multi-match to fewer-match and zero-match contraction.
+  - [x] Pass focused footer tests, CLI typecheck, and CLI build.
 - [x] A recovered pause no longer strands its session. Submitting a new task
   retires the superseded generation instead of refusing every later prompt,
   while unreconciled external effects still fence admission.

package/docs/work-orders/runtime-health-remediation/WO-22-autocomplete-footer-geometry.md

@@ -0,0 +1,93 @@
+# WO-22: Autocomplete Footer Geometry Integrity
+
+**Status:** complete
+
+**Observed:** 2026-09-03
+
+**Scope:** CLI TUI footer, DirectInput redraw scheduling, active content writes
+
+## Failure
+
+When slash-command autocomplete expands and then contracts, rows from the old
+footer can remain visible above the current input box. The captured failure
+occurred while `file_read` content was active. A complete old input box and old
+suggestion rows remained in the content viewport after the live footer moved
+down.
+
+## Root cause
+
+DirectInput emits a change and schedules footer painting with `setImmediate`.
+If content output starts before that callback, `beginContentWrite()` recomputes
+and stores the new footer height. The later renderer reconstructs the supposed
+old footer top from that already-mutated height. It therefore observes no
+height change and skips the transition clear.
+
+The terminal's last painted geometry and the logical layout are separate
+states. `_lastFooterPaintTop` is the authority for the former. A mutable
+`_currentFooterHeight` cannot be used to infer what remains on screen.
+
+The streaming renderer also uses incremental line-feed and reverse-index
+compensation when the footer moves. That path depends on terminal scroll-region
+semantics and does not deterministically rebuild released rows from Omnius's
+scrollback model.
+
+## Invariants
+
+- Every footer renderer compares the new top with the last successfully painted
+  footer top.
+- A changed logical height or changed painted top is a geometry transition.
+- Geometry transitions update DECSTBM, clear the complete old/new footer union,
+  replay content from the virtual scrollback, repaint tasks, and then paint the
+  new footer.
+- Active content writes do not use line feed, reverse index, or cursor-offset
+  guesses to compensate for footer growth or shrinkage.
+- After a geometry transition, token chunks enter the bounded 33 ms replay
+  scheduler. They do not cause synchronous full-viewport repainting per token.
+- Replay-consumed stdout writes preserve callback completion, and stream close
+  paints any final coalesced line before returning ownership to the idle footer.
+- Cursor-preserving animation and metrics frames cannot accept a precomputed
+  footer position before the transition is cleared.
+- Footer chrome writes bypass the buffered content layer.
+- The native streaming cursor is restored by content replay, while the input
+  cursor remains owned by the idle path.
+- Repeated expansion and contraction is idempotent and cannot accumulate rows.
+
+## Work items
+
+- [x] Trace DirectInput change ordering and scheduled redraw ownership.
+- [x] Trace `beginContentWrite()` layout mutation and terminal paint ordering.
+- [x] Confirm the idle source-level regression test does not cover active writes.
+- [x] Confirm the PTY helper does not interpret final terminal cells.
+- [x] Make last-painted footer geometry authoritative in the idle renderer.
+- [x] Route active-stream geometry transitions through deterministic replay.
+- [x] Preserve the direct terminal bypass for chrome paints.
+- [x] Add a test for a precommitted logical shrink before idle paint.
+- [x] Add a test for a precommitted logical shrink during active content output.
+- [x] Cover multi-match to fewer-match and multi-match to zero-match transitions.
+- [x] Prove no reverse-index compensation remains in the streaming transition.
+- [x] Run the focused footer and DirectInput suite.
+- [x] Run CLI typecheck and build.
+- [x] Inspect the scoped diff and record acceptance evidence.
+
+## Acceptance evidence
+
+- `StatusBar.paintedFooterTop()` uses `_lastFooterPaintTop` as physical screen
+  authority, with a logical-height fallback only before the first paint.
+- Both footer render paths treat either a height change or a painted-top change
+  as a geometry transition.
+- Active-stream transitions update DECSTBM, clear the old/new footer union, fill
+  and replay the viewport, refresh tasks, and repaint the footer. Later chunks
+  stay in a coalesced virtual replay until the stream closes.
+- `footer-suggestion-shrink-render.test.ts` executes five-to-one and one-to-zero
+  contraction after precommitting the logical height. Its ANSI framebuffer
+  confirms that prior suggestion text is absent from final terminal cells.
+- The same test executes the five-to-one race with `writeDepth > 0` and confirms
+  the replay path. A following token does not trigger an immediate repaint, its
+  write callback completes, and stream close performs the final replay.
+- A cursor-preserving-frame regression proves that a precomputed logical layout
+  cannot overwrite the last-painted geometry before cleanup.
+- The focused footer/DirectInput suite passed: 6 files, 44 tests.
+- The complete CLI suite passed: 262 files, 2,446 tests.
+- `pnpm --filter omnius typecheck` passed.
+- `pnpm --filter omnius build` passed.
+- No live inference or CUDA workload was used.

package/docs/work-orders/telegram-dmn/WO-22-dmn-outreach-and-learning.md

@@ -0,0 +1,85 @@
+# WO-22: DMN outreach, DM sharing, and outcome learning
+
+## Incident
+
+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.
+
+It was not. The post was reactive to two inbound messages (5680, 5681) and
+authorized as `direct_turn`. The stated router reason — *"Sender reacts to
+bot's recent output in active thread"* — was false: the cited self-bearing
+evidence was `turn:5678`, a bot reply from **09-01**, to a different user,
+about a different topic.
+
+Two independent defects produced that:
+
+- `buildTelegramInteractionEvidencePacket` selects causal history with
+  `.slice(-8)` and **no time bound**. In a quiet room the last 8 messages
+  reach back days.
+- The `direct_turn` validator requires a cited self-bearing evidence entry but
+  checks only *kind* and *actor*, never *recency*. A two-day-old turn satisfied
+  it.
+
+Investigating that surfaced the larger finding below.
+
+## The real finding: reflection could not speak
+
+Omnius reflects constantly — **465 daydream artifacts on 2026-09-03 alone** —
+and roughly two thirds of recent artifacts proposed a same-group follow-up.
+None were ever sent. Across 639 committed routing decisions in this workspace,
+`social_intervention` fired exactly **once**; the other 432 replies were all
+`direct_turn`.
+
+Root cause was ID plumbing, not judgement:
+
+- The extraction schema advertised `reply_to_message_id: 1` and
+  `source_message_ids: [1]` as examples. **78.6% of live follow-up proposals
+  echoed a placeholder-like id**, `1` being the single most common value.
+- Those ids never matched real Telegram ids, so `candidateMessageIds` was
+  almost always empty.
+- The discretion prompt then instructed the model to *"cite at least one
+  current eligible Telegram message ID"* **without ever listing which ids were
+  eligible**, while the host discarded any follow-up citing an id outside that
+  undisclosed set.
+
+Silence was the only reachable outcome.
+
+## Changes
+
+| Area | Change |
+| --- | --- |
+| Extraction prompt | Schema example ids replaced with non-numeric sentinels; explicit rule that ids must appear literally in the corpus; the valid id set is now stated. |
+| Extraction result | `runTelegramReflectionExtraction` drops any `source_message_ids` / `reply_to_message_id` absent from the corpus, so a copied or hallucinated anchor cannot reach the follow-up gate. |
+| Discretion prompt | Now supplies `Eligible evidence message IDs`, the exact set the host validates against. |
+| DM reflection | Idle reflection and outreach admitted for private chats **only after that chat opts in** via `/reflect auto on`. Default remains off. |
+| Outcome learning | New `telegram-outreach-outcomes.ts` records every autonomous send and settles it as engaged / ignored from subsequent room traffic. Settled history is fed back into the next discretion call. |
+
+## Design notes
+
+- **DMs are opt-in, not default.** A DM is one person's inbox. The capability
+  exists; the host does not enable it on the recipient's behalf.
+- **Silence is recorded as a real signal.** An unanswered outreach settles to
+  `engaged: false` after 45 minutes rather than staying unknown, so the
+  calibration block cannot mistake absence of data for success.
+- **The bot's own traffic never counts as engagement.** Only a human message
+  inside the window closes an outcome positively.
+- **Calibration is neutral before it is negative.** With no settled history the
+  prompt says so and asks the model to judge on merit; it raises the bar only
+  once every settled attempt was ignored.
+
+## Not addressed
+
+The evidence-packet recency defect that produced the original false
+`direct_turn` remains open. Bounding causal history by time would push honest
+unaddressed interjections onto the `social_intervention` path, where they are
+visible and tunable — but `social_intervention` currently has **no validation
+rules at all** (compare five checks for `direct_turn`). Both should be done
+together so interjection becomes a governed capability rather than an
+unvalidated fallback.
+
+## Verification
+
+CLI suite: 2442 passed, 0 failed (261 files). Typecheck clean; `pnpm -r build`
+clean. 14 new tests covering id anchoring, corpus allow-list enforcement,
+outcome settlement, calibration wording, torn-ledger recovery, and bridge
+wiring.

package/npm-shrinkwrap.json

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

package/package.json

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