omnius 1.0.775 → 1.0.776

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/index.js CHANGED
@@ -1,4 +1,4 @@
1
1
  [diffend] Oversized file quarantined before diffing.
2
2
  name: package/dist/index.js
3
- size: 38986047 bytes
4
- sha256: dfcea3ec5e2e13ad022ee0c49daa95bc87809fbcf6ad7134c5a62111617274c0
3
+ size: 39016717 bytes
4
+ sha256: c7caf242ceb7df7ccd5327413f4c3103dfcec2a84a84ba81c6eb6477e8f80db9
@@ -35901,6 +35901,42 @@
35901
35901
  }
35902
35902
  ]
35903
35903
  },
35904
+ {
35905
+ "id": "guide.work-orders-telegram-reliability-consolidation-2026-09-28",
35906
+ "kind": "guide",
35907
+ "title": "Telegram Reliability Consolidation — 2026-09-28",
35908
+ "summary": "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.",
35909
+ "keywords": [
35910
+ "work",
35911
+ "orders",
35912
+ "telegram",
35913
+ "reliability",
35914
+ "consolidation",
35915
+ "2026",
35916
+ "09",
35917
+ "28",
35918
+ "md"
35919
+ ],
35920
+ "maturity": "internal",
35921
+ "audiences": [
35922
+ "maintainer",
35923
+ "large-context-agent"
35924
+ ],
35925
+ "layer": "documentation",
35926
+ "interfaces": [
35927
+ {
35928
+ "type": "file",
35929
+ "target": "docs/work-orders/telegram-reliability-consolidation-2026-09-28.md"
35930
+ }
35931
+ ],
35932
+ "references": [
35933
+ {
35934
+ "type": "documentation",
35935
+ "target": "docs/work-orders/telegram-reliability-consolidation-2026-09-28.md",
35936
+ "relation": "canonical-artifact"
35937
+ }
35938
+ ]
35939
+ },
35904
35940
  {
35905
35941
  "id": "guide.work-orders-wo-am-gaps-uppercase",
35906
35942
  "kind": "guide",
package/docs/DISCOVERY.md CHANGED
@@ -610,6 +610,7 @@ Daemon equivalents are `GET /v1/discovery/bootstrap`, `GET /v1/discovery?q=<inte
610
610
  | `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 |
611
611
  | `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. |
612
612
  | `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. |
613
+ | `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. |
613
614
  | `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 |
614
615
  | `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 |
615
616
  | `guide.work-orders-world-class-memory-compiler-tracker-uppercase` | Memory Compiler Implementation Tracker | Last reconciled: 2026-07-13 Authority: This file is the granular program tracker. The work-order documents define the contract and acceptance criteria; neither test output nor a model claim may check an item without the named evidence. |
@@ -0,0 +1,178 @@
1
+ # Telegram Reliability Consolidation — 2026-09-28
2
+
3
+ Status: complete
4
+
5
+ Rule: check a box only after the named behavior is implemented and its listed
6
+ verification passes. A parent box stays open until every child box is checked.
7
+
8
+ ## Failure classification
9
+
10
+ - [x] **R1 — Response identity split (correctness, P0).** A runner can retain
11
+ one input/task identity while visible reply ownership moves to a later input.
12
+ - [x] Define one response binding containing `inputId`, `messageId`,
13
+ `decisionId`, `taskEpoch`, `runId`, generation, reply target, and route.
14
+ - [x] Use that binding for social-decision commit.
15
+ - [x] Use that binding for visible reply ownership.
16
+ - [x] Use that binding for final Telegram reply targeting.
17
+ - [x] Use that binding for delivery-ledger attribution.
18
+ - [x] Reject delivery when any binding identity differs.
19
+ - [x] Prevent a materially new request from inheriting an older objective.
20
+ - [x] Cover the message-496/message-499 production shape with a regression
21
+ test.
22
+
23
+ - [x] **R2 — Active-runner authority bypass (correctness/safety, P0).** Public
24
+ group steering can bypass the group reply-authority review used by new work.
25
+ - [x] Apply equivalent input-bound reply-authority validation to active-runner
26
+ routing.
27
+ - [x] Fail closed when active-runner authority is unavailable or invalid.
28
+ - [x] Test a human-to-human active-runner turn that must remain silent.
29
+ - [x] Test a direct active-runner address that remains reply-capable.
30
+
31
+ - [x] **R3 — Conversational admin DM misclassified as mutation (correctness,
32
+ P0).** Metaphorical or conversational reset language enters the full action
33
+ pipeline and creates an unfulfillable mutation obligation.
34
+ - [x] Add a conversational/internal-control execution class before action
35
+ planning.
36
+ - [x] Ensure metaphorical reset/acknowledgement requests do not require a
37
+ mutation effect.
38
+ - [x] Avoid engineering workboard creation for a simple acknowledgement.
39
+ - [x] Avoid `tool_search`/`todo_write` for the acknowledgement fast path.
40
+ - [x] Preserve the natural assistant answer as the delivered reply.
41
+ - [x] Test `clear your slate ... mentally and proverbially` end to end.
42
+
43
+ - [x] **R4 — Completion verifier replaces valid replies with bookkeeping
44
+ (correctness/UX, P0).** A host-side contract mismatch can discard a current,
45
+ evidence-bound `task_complete.user_reply`.
46
+ - [x] Separate conversational reply delivery from action verification status.
47
+ - [x] Keep a valid current user reply deliverable when only the generated
48
+ expected-effect contract is unsatisfied.
49
+ - [x] Keep genuine mutation failures fail-closed for completion claims.
50
+ - [x] Put verification gaps in diagnostics/evidence rather than substituting
51
+ them for a valid conversational reply.
52
+ - [x] Replace tests that encode the undesirable canned admin response.
53
+
54
+ - [x] **R5 — Admin control-plane leakage (UX, P1).** Steering reconciliation is
55
+ rendered as `Plan update` on the primary admin response surface.
56
+ - [x] Remove reconciliation blocks from the admin response page.
57
+ - [x] Retain reconciliation evidence under Tasks/Logs/Context diagnostics.
58
+ - [x] Ensure final admin reply composition does not prepend plan telemetry.
59
+ - [x] Test that ordinary admin replies contain no `Plan update` block.
60
+
61
+ - [x] **R6 — Serial inference multiplication (latency, P1).** Router,
62
+ authority, generation, semantic review, and repair retries stack on the
63
+ critical path.
64
+ - [x] Split minimal social authority/route output from action planning fields.
65
+ - [x] Run action planning only for an accepted action route.
66
+ - [x] Bound malformed-router repair to one compact repair attempt.
67
+ - [x] Avoid an unconditional semantic review for low-risk conversational chat.
68
+ - [x] Run the second-pass public authority review only for positive group
69
+ candidates; do not spend that call on already-silent decisions.
70
+ - [x] Add an operation-level routing deadline that includes broker admission
71
+ and retries.
72
+ - [x] Test bounded inference-call counts for no-reply, private chat, group
73
+ chat, and action routes.
74
+
75
+ - [x] **R7 — Oversized context for trivial turns (latency/cost, P1).** A simple
76
+ acknowledgement consumed five turns and 110,433 cumulative tokens.
77
+ - [x] Define a strict context budget for conversational/admin fast paths.
78
+ - [x] Exclude workspace tree, work graph, mutation receipts, and engineering
79
+ contracts when the execution class does not need them.
80
+ - [x] Stop repeating no-plan reminders on conversational turns.
81
+ - [x] Add a regression ceiling for prompt size and runner turns.
82
+
83
+ - [x] **R8 — Durable spool replay churn (durability/performance, P0).** A raw
84
+ update remains reclaimable after it has been durably transferred to intake,
85
+ producing repeated dispatch attempts.
86
+ - [x] Define the transport-terminal state for an update durably bound to
87
+ intake.
88
+ - [x] Mark the raw spool row transport-terminal atomically when the first
89
+ durable intake lifecycle record commits.
90
+ - [x] Let the intake lifecycle, not raw update replay, own deferred work.
91
+ - [x] Preserve raw-envelope restart recovery before the durable intake
92
+ handoff commits.
93
+ - [x] Rehydrate nonterminal logical intake after restart without reclaiming
94
+ the raw transport envelope.
95
+ - [x] Recover the newest edited-message revision while preserving the
96
+ original logical intake owner.
97
+ - [x] Test that deferred active-runner intake is not replay-claimed.
98
+ - [x] Test production restart recovery through the real replay entry point,
99
+ with one logical scheduling and one raw dispatch attempt.
100
+
101
+ - [x] **R9 — Head-of-line route blocking (latency, P1).** One global active
102
+ route slot lets a slow/retried chat delay unrelated chats.
103
+ - [x] Replace the global single route slot with bounded fair concurrency.
104
+ - [x] Preserve per-chat inference serialization and exact input binding.
105
+ - [x] Prioritize direct messages, direct mentions, and known reply-capable
106
+ chats.
107
+ - [x] Test that a stalled route does not block an unrelated direct address.
108
+
109
+ - [x] **R10 — Terminal review duplication (latency, P1).** Identical unchanged
110
+ evidence can receive repeated inline reviews and recovery cycles.
111
+ - [x] Key terminal review results by input, objective-frontier hash, and
112
+ evidence digest.
113
+ - [x] Reuse a review when its evidence identity is unchanged.
114
+ - [x] Do not immediately retry an identical malformed review inline.
115
+ - [x] Keep simple conversation replies out of action recovery; reuse an
116
+ unchanged evidence review for read-only research instead of reviewing it
117
+ again at each stalled/terminal phase.
118
+ - [x] Test bounded review/recovery counts.
119
+
120
+ - [x] **R11 — Normal-mode event noise (observability, P2).** Sequential router
121
+ and reply-phase cards obscure the user-visible critical path.
122
+ - [x] Bind every inference phase to the exact input and reuse one TUI block
123
+ for sequential phases of that input only.
124
+ - [x] Label group inference with the group name rather than a generic title.
125
+ - [x] Collapse completed control-plane JSON while keeping it available in
126
+ the block's explicit read mode.
127
+ - [x] Keep periodic queue diagnostics behind an explicit debug flag.
128
+ - [x] Preserve the underlying segments and durable forensic evidence.
129
+ - [x] Test that normal mode omits raw completed router JSON and repeated
130
+ queue chatter.
131
+
132
+ - [x] **R12 — Todo-state path override ignored (testability/configuration,
133
+ P2).** The todo store wrote only to `~/.omnius`, so restricted environments
134
+ reported a false lock timeout instead of exercising Telegram context tests.
135
+ - [x] Make the todo store honor the existing `OMNIUS_HOME` state-root
136
+ override used by the other execution stores.
137
+ - [x] Make its disk-layout assertion derive the path from `todoDir()`.
138
+ - [x] Run the todo-store and task-completion guard suites under an isolated
139
+ `OMNIUS_HOME` (42/42 passing).
140
+
141
+ ## Verification and delivery
142
+
143
+ - [x] Run focused Telegram routing and authority tests.
144
+ - [x] Run active-runner steering tests.
145
+ - [x] Run admin live-panel and terminal-delivery tests.
146
+ - [x] Run completion-readiness/orchestrator tests.
147
+ - [x] Run durable update spool and restart-replay tests.
148
+ - [x] Run Telegram queue/priority tests.
149
+ - [x] Run the complete Telegram CLI test subset affected by these changes.
150
+ - [x] Build every changed workspace package.
151
+ - [x] Inspect the diff for unrelated files and generated artifacts.
152
+ - [x] Commit each coherent verified repair with scoped paths only.
153
+ - [x] Fetch the tracked branch and push without rewriting shared history.
154
+ - [x] Record commit hashes, branch, and verification results here.
155
+
156
+ ## Evidence log
157
+
158
+ - Live admin-DM run:
159
+ `telegram-64ac9937dc7647a8-1790575905415-1`.
160
+ - Live Case Theory mismatch: source task message 496, transferred visible reply
161
+ owner message 499, delivered message 500.
162
+ - No completion boxes were pre-checked when this work order was created.
163
+ - Focused Telegram routing/authority/UI verification: 106/106 passing.
164
+ - Integrated affected Telegram CLI verification: 426/426 passing across 21
165
+ files, including `telegram-bot-api-10.test.ts` at 155/155.
166
+ - Orchestrator completion authority verification: 30/30 passing.
167
+ - Execution todo-store override and completion-guard verification: 42/42
168
+ passing under an isolated `OMNIUS_HOME`.
169
+ - Workspace builds: `@omnius/execution`, `@omnius/orchestrator`, and `omnius`
170
+ all passing.
171
+ - `git diff --check`: passing. Unrelated pre-existing changes in
172
+ `docs/DISCOVERY.json`, `docs/DISCOVERY.md`, `publish/npm-shrinkwrap.json`,
173
+ and `publish/package.json` are intentionally excluded from delivery.
174
+ - Scoped delivery commits: `21134195` (todo-state override), `d489e4ca`
175
+ (Telegram/orchestrator reliability), and `8d594887` (verification record).
176
+ - Fetched `origin/main` with zero remote-only commits, then pushed without
177
+ rewriting history. Remote `main` was verified at
178
+ `8d594887e87364ecf3e6d7475ca1cda24cde9852`.
@@ -1,12 +1,12 @@
1
1
  {
2
2
  "name": "omnius",
3
- "version": "1.0.775",
3
+ "version": "1.0.776",
4
4
  "lockfileVersion": 3,
5
5
  "requires": true,
6
6
  "packages": {
7
7
  "": {
8
8
  "name": "omnius",
9
- "version": "1.0.775",
9
+ "version": "1.0.776",
10
10
  "bundleDependencies": [
11
11
  "image-to-ascii"
12
12
  ],
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "omnius",
3
- "version": "1.0.775",
3
+ "version": "1.0.776",
4
4
  "description": "AI coding agent powered by open-source models (Ollama/vLLM) — interactive TUI with agentic tool-calling loop",
5
5
  "type": "module",
6
6
  "main": "./dist/library.js",