omnius 1.0.701 → 1.0.702

package/docs/DISCOVERY.json

@@ -35352,6 +35352,44 @@
         }
       ]
     },
+    {
+      "id": "guide.work-orders-runtime-health-remediation-wo-53-deferred-reflection-churn-uppercase",
+      "kind": "guide",
+      "title": "WO-53: Stop duplicate deferred reflection writes",
+      "summary": "Status: scoped source repair verified; publication remains with the operator. Issue: https://github.com/robit-man/open-agents/issues/3",
+      "keywords": [
+        "work",
+        "orders",
+        "runtime",
+        "health",
+        "remediation",
+        "WO",
+        "53",
+        "deferred",
+        "reflection",
+        "churn",
+        "md"
+      ],
+      "maturity": "internal",
+      "audiences": [
+        "maintainer",
+        "large-context-agent"
+      ],
+      "layer": "documentation",
+      "interfaces": [
+        {
+          "type": "file",
+          "target": "docs/work-orders/runtime-health-remediation/WO-53-deferred-reflection-churn.md"
+        }
+      ],
+      "references": [
+        {
+          "type": "documentation",
+          "target": "docs/work-orders/runtime-health-remediation/WO-53-deferred-reflection-churn.md",
+          "relation": "canonical-artifact"
+        }
+      ]
+    },
     {
       "id": "guide.work-orders-telegram-dmn-wo-22-dmn-outreach-and-learning-uppercase",
       "kind": "guide",

package/docs/DISCOVERY.md

@@ -599,6 +599,7 @@ Daemon equivalents are `GET /v1/discovery/bootstrap`, `GET /v1/discovery?q=<inte
 | `guide.work-orders-runtime-health-remediation-wo-50-embedding-unavailability-uppercase` | WO-50: Recover honestly from missing embeddings | Status: repository repair complete; delivered as a3375c63 to origin/main. Requested Nomic re-pull completed and passive server recovery observed. Publication and live acceptance of source changes remain with the user. |
 | `guide.work-orders-runtime-health-remediation-wo-51-large-telegram-attachments-uppercase` | WO-51: Receive and unpack large Telegram attachments | Status: source repair complete and verified. Publication and Local Bot API live acceptance remain with the operator. |
 | `guide.work-orders-runtime-health-remediation-wo-52-steering-projection-preservation-uppercase` | WO-52: Preserve required steering instructions in the actual model request | Status: source repair complete; verified and ready for publication. Live acceptance follows the user's publication. |
+| `guide.work-orders-runtime-health-remediation-wo-53-deferred-reflection-churn-uppercase` | WO-53: Stop duplicate deferred reflection writes | Status: scoped source repair verified; publication remains with the operator. Issue: https://github.com/robit-man/open-agents/issues/3 |
 | `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 |

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

@@ -4,6 +4,10 @@
 **Checked-item rule:** code, focused tests, and named evidence must all exist
 **Last reconciled:** 2026-09-05
 
+## September 5 runtime 1.0.701 rapid churn repair
+
+- [x] [WO-53: deferred reflection churn](WO-53-deferred-reflection-churn.md): persistent scoped revision receipts prevent repeated unchanged reflection appends; seven regressions and workspace build passed. [Issue #3](https://github.com/robit-man/open-agents/issues/3) retains the separate context-recovery investigation and corrected budget findings. Existing backlog and live runtime are unchanged.
+
 ## September 5 runtime 1.0.700 large attachment follow-up
 
 - [x] [WO-51: large Telegram attachments](WO-51-large-telegram-attachments.md): fixed inbound/cache byte caps removed; streamed download, Local Bot API transport, exact archive aliases and responsive durable Stop verified. Archive implementation `dec18c74` and CLI integration `40a76cea` delivered to `origin/main`.

package/docs/work-orders/runtime-health-remediation/WO-53-deferred-reflection-churn.md

@@ -0,0 +1,27 @@
+# WO-53: Stop duplicate deferred reflection writes
+
+Status: scoped source repair verified; publication remains with the operator.
+Issue: https://github.com/robit-man/open-agents/issues/3
+
+## Finding
+
+Runtime 1.0.701 repeatedly upserted unchanged retained Telegram messages. The deferred branch computed an episode ID but unconditionally appended and returned `reused: false`. A captured 1.2 MB tail contained 138 copies of one message with identical content; the complete spool was 3,275,565,579 bytes. That sample does not attribute every byte of the backlog to this producer. Evidence and hashes: `/tmp/omnius-rapid-issues-a6e37rk0/manifest.json`.
+
+## Repair
+
+- `packages/cli/src/tui/telegram-reflection-corpus.ts`: fingerprint scoped message identity plus projected content and metadata; return the actual deferred reuse receipt. Preserve edits to text, mode, media and reply context.
+- `packages/cli/src/tui/memory-paths.ts`: persist content-addressed revision receipts after a flushed JSONL append. Receipts survive process reload and maintenance rotation without opening episode or graph databases inline. Unkeyed callers retain their existing append behavior.
+- Existing bot ownership serializes the producer. This is an at-least-once crash boundary: interruption between append and receipt can cause one replay; the receipt must never acknowledge an unwritten record. No global multi-writer exactly-once claim is made. The existing large spool is preserved for maintenance, not deleted or rewritten.
+
+## Verification
+
+- [x] 138 repeated unchanged upserts add exactly one record and return reuse.
+- [x] Fresh module state plus rotated spool still reuses the persistent revision receipt.
+- [x] Changed text/mode/media and different chat scope remain separate records.
+- [x] Failed append does not create an acknowledgment; retry succeeds.
+- [x] All seven cases in `memory-paths.test.ts` and `telegram-reflection-corpus.test.ts` passed: `/tmp/omnius-issue3-churn-tests.log`.
+- [x] All-workspace build passed: `/tmp/omnius-issue3-build.log`.
+
+## Remaining issue scope
+
+The repeated context-snapshot recovery behavior remains in issue #3. The read-headroom comparison was refined: the first zero-headroom receipts occurred with 39,615/40,000 canonical input tokens, requesting another 4,718 and 3,203 tokens. Physical model free space is a different budget; the subtraction was not shown incorrect. Do not increase only the read ceiling, which could violate subsequent canonical admission. Neither behavior is claimed repaired by this scoped churn patch. No live inference, service restart, model change or backlog mutation was performed.

package/npm-shrinkwrap.json

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

package/package.json

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