omnius 1.0.694 → 1.0.695

package/docs/DISCOVERY.json

@@ -32804,6 +32804,44 @@
         }
       ]
     },
+    {
+      "id": "guide.work-orders-runtime-health-remediation-telegram-longhaul-2026-09-04-uppercase",
+      "kind": "guide",
+      "title": "September 4 Telegram long-haul remediation",
+      "summary": "Status: complete; all five root repairs verified and delivered to origin/main Baseline: Omnius main 69c4a160; installed package 1.0.694 Incident run: telegram-64ac9937dc7647a8-1788572475259-1 Observation window: 2026-09-04 18:41–20:43 PDT Owner: repository repair; user owns publication and subsequent live testing",
+      "keywords": [
+        "work",
+        "orders",
+        "runtime",
+        "health",
+        "remediation",
+        "TELEGRAM",
+        "LONGHAUL",
+        "2026",
+        "09",
+        "04",
+        "md"
+      ],
+      "maturity": "internal",
+      "audiences": [
+        "maintainer",
+        "large-context-agent"
+      ],
+      "layer": "documentation",
+      "interfaces": [
+        {
+          "type": "file",
+          "target": "docs/work-orders/runtime-health-remediation/TELEGRAM-LONGHAUL-2026-09-04.md"
+        }
+      ],
+      "references": [
+        {
+          "type": "documentation",
+          "target": "docs/work-orders/runtime-health-remediation/TELEGRAM-LONGHAUL-2026-09-04.md",
+          "relation": "canonical-artifact"
+        }
+      ]
+    },
     {
       "id": "guide.work-orders-runtime-health-remediation-traceability-uppercase",
       "kind": "guide",
@@ -33982,6 +34020,200 @@
         }
       ]
     },
+    {
+      "id": "guide.work-orders-runtime-health-remediation-wo-25-memory-compiler-eligibility-and-audit-uppercase",
+      "kind": "guide",
+      "title": "WO-25: Memory compiler eligibility and outcome audit",
+      "summary": "Status: complete; implemented, verified, and pushed to origin/main Priority: P1 Incident date: 2026-09-04 PDT / 2026-09-05 UTC Program: September 4 Telegram long-haul repairs",
+      "keywords": [
+        "work",
+        "orders",
+        "runtime",
+        "health",
+        "remediation",
+        "WO",
+        "25",
+        "memory",
+        "compiler",
+        "eligibility",
+        "and",
+        "audit",
+        "md"
+      ],
+      "maturity": "internal",
+      "audiences": [
+        "maintainer",
+        "large-context-agent"
+      ],
+      "layer": "documentation",
+      "interfaces": [
+        {
+          "type": "file",
+          "target": "docs/work-orders/runtime-health-remediation/WO-25-memory-compiler-eligibility-and-audit.md"
+        }
+      ],
+      "references": [
+        {
+          "type": "documentation",
+          "target": "docs/work-orders/runtime-health-remediation/WO-25-memory-compiler-eligibility-and-audit.md",
+          "relation": "canonical-artifact"
+        }
+      ]
+    },
+    {
+      "id": "guide.work-orders-runtime-health-remediation-wo-26-admin-telegram-media-aliases-uppercase",
+      "kind": "guide",
+      "title": "WO-26: Admin Telegram media alias resolution",
+      "summary": "Status: complete; implemented, verified, and pushed to origin/main Priority: P1 Incident date: 2026-09-04 PDT / 2026-09-05 UTC Program: September 4 Telegram long-haul repairs",
+      "keywords": [
+        "work",
+        "orders",
+        "runtime",
+        "health",
+        "remediation",
+        "WO",
+        "26",
+        "admin",
+        "telegram",
+        "media",
+        "aliases",
+        "md"
+      ],
+      "maturity": "internal",
+      "audiences": [
+        "maintainer",
+        "large-context-agent"
+      ],
+      "layer": "documentation",
+      "interfaces": [
+        {
+          "type": "file",
+          "target": "docs/work-orders/runtime-health-remediation/WO-26-admin-telegram-media-aliases.md"
+        }
+      ],
+      "references": [
+        {
+          "type": "documentation",
+          "target": "docs/work-orders/runtime-health-remediation/WO-26-admin-telegram-media-aliases.md",
+          "relation": "canonical-artifact"
+        }
+      ]
+    },
+    {
+      "id": "guide.work-orders-runtime-health-remediation-wo-27-task-verification-authority-uppercase",
+      "kind": "guide",
+      "title": "WO-27: Separate mutation observations from task verification",
+      "summary": "Status: complete; implemented, verified, and pushed to origin/main Priority: P1 Incident date: 2026-09-04 PDT / 2026-09-05 UTC Program: September 4 Telegram long-haul repairs",
+      "keywords": [
+        "work",
+        "orders",
+        "runtime",
+        "health",
+        "remediation",
+        "WO",
+        "27",
+        "task",
+        "verification",
+        "authority",
+        "md"
+      ],
+      "maturity": "internal",
+      "audiences": [
+        "maintainer",
+        "large-context-agent"
+      ],
+      "layer": "documentation",
+      "interfaces": [
+        {
+          "type": "file",
+          "target": "docs/work-orders/runtime-health-remediation/WO-27-task-verification-authority.md"
+        }
+      ],
+      "references": [
+        {
+          "type": "documentation",
+          "target": "docs/work-orders/runtime-health-remediation/WO-27-task-verification-authority.md",
+          "relation": "canonical-artifact"
+        }
+      ]
+    },
+    {
+      "id": "guide.work-orders-runtime-health-remediation-wo-28-task-scope-evidence-retirement-uppercase",
+      "kind": "guide",
+      "title": "WO-28: Retire obsolete task evidence after explicit scope changes",
+      "summary": "Status: complete; implemented, verified, and pushed to origin/main Priority: P2 Incident date: 2026-09-04 PDT / 2026-09-05 UTC Program: September 4 Telegram long-haul repairs",
+      "keywords": [
+        "work",
+        "orders",
+        "runtime",
+        "health",
+        "remediation",
+        "WO",
+        "28",
+        "task",
+        "scope",
+        "evidence",
+        "retirement",
+        "md"
+      ],
+      "maturity": "internal",
+      "audiences": [
+        "maintainer",
+        "large-context-agent"
+      ],
+      "layer": "documentation",
+      "interfaces": [
+        {
+          "type": "file",
+          "target": "docs/work-orders/runtime-health-remediation/WO-28-task-scope-evidence-retirement.md"
+        }
+      ],
+      "references": [
+        {
+          "type": "documentation",
+          "target": "docs/work-orders/runtime-health-remediation/WO-28-task-scope-evidence-retirement.md",
+          "relation": "canonical-artifact"
+        }
+      ]
+    },
+    {
+      "id": "guide.work-orders-runtime-health-remediation-wo-29-retired-failure-projections-uppercase",
+      "kind": "guide",
+      "title": "WO-29: Exclude retired failures from active diagnostics",
+      "summary": "Status: complete; implemented, verified, and pushed to origin/main Priority: P2 Incident date: 2026-09-04 PDT / 2026-09-05 UTC Program: September 4 Telegram long-haul repairs",
+      "keywords": [
+        "work",
+        "orders",
+        "runtime",
+        "health",
+        "remediation",
+        "WO",
+        "29",
+        "retired",
+        "failure",
+        "projections",
+        "md"
+      ],
+      "maturity": "internal",
+      "audiences": [
+        "maintainer",
+        "large-context-agent"
+      ],
+      "layer": "documentation",
+      "interfaces": [
+        {
+          "type": "file",
+          "target": "docs/work-orders/runtime-health-remediation/WO-29-retired-failure-projections.md"
+        }
+      ],
+      "references": [
+        {
+          "type": "documentation",
+          "target": "docs/work-orders/runtime-health-remediation/WO-29-retired-failure-projections.md",
+          "relation": "canonical-artifact"
+        }
+      ]
+    },
     {
       "id": "guide.work-orders-telegram-dmn-wo-22-dmn-outreach-and-learning-uppercase",
       "kind": "guide",

package/docs/DISCOVERY.md

@@ -532,6 +532,7 @@ Daemon equivalents are `GET /v1/discovery/bootstrap`, `GET /v1/discovery?q=<inte
 | `guide.work-orders-runtime-health-remediation-h6-main-tui-wo-05-confirmation-evidence-uppercase` | H6 Main-TUI and WO-05 Confirmation Evidence | This closure wires the top-level TUI FullSubAgentTool to live parent-context headroom and the exact owning task cancellation signal. It also confirms the WO-05 completion authority after the interruption, safe-media, workboard, and canonical-context changes. |
 | `guide.work-orders-runtime-health-remediation-live-telegram-log-review-2026-09-03-uppercase` | Live Telegram Log Review, 2026-09-03 | This review is read-only. It examines the persisted Telegram conversation and intake lifecycle records in /home/roko/Documents/Projects/Adjacent/telegramtest/.omnius. The running global Omnius package reports version 1.0.687. This means the observations describe the deployed pre-publication runtime, not the newer source commits on this repository's main bran |
 | `guide.work-orders-runtime-health-remediation-readme-uppercase` | Runtime Health Remediation Program | Program ID: RHR-2026-09-02 Status: active, implementation authorized Owner: Omnius runtime, orchestration, execution, memory, and Telegram packages External dependency: /home/roko/Desktop/ollama-unify Last reconciled: 2026-09-03 |
+| `guide.work-orders-runtime-health-remediation-telegram-longhaul-2026-09-04-uppercase` | September 4 Telegram long-haul remediation | Status: complete; all five root repairs verified and delivered to origin/main Baseline: Omnius main 69c4a160; installed package 1.0.694 Incident run: telegram-64ac9937dc7647a8-1788572475259-1 Observation window: 2026-09-04 18:41–20:43 PDT Owner: repository repair; user owns publication and subsequent live testing |
 | `guide.work-orders-runtime-health-remediation-traceability-uppercase` | Runtime Health Remediation Traceability Matrix | Every completed row links to a deterministic test or operational receipt. A commit hash alone is not proof. A model statement is not proof. Live logs may support a canary only after the hermetic and deterministic gates pass. A status that names pending rollout or live work is intentionally not a completion claim. |
 | `guide.work-orders-runtime-health-remediation-tracker-uppercase` | Runtime Health Remediation Master Tracker | Authority: canonical granular tracker for RHR-2026-09-02 Checked-item rule: code, focused tests, and named evidence must all exist Last reconciled: 2026-09-04 |
 | `guide.work-orders-runtime-health-remediation-wo-00-hermetic-test-boundary-uppercase` | WO-00: Hermetic Test Boundary | Status: deterministic acceptance complete Evidence: inference network inventory and audit receipt for commit 8708e449 Risk: high, because current unit tests can contact the live broker Depends on: none |
@@ -563,6 +564,11 @@ Daemon equivalents are `GET /v1/discovery/bootstrap`, `GET /v1/discovery?q=<inte
 | `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-runtime-health-remediation-wo-23-long-horizon-control-plane-reconciliation-uppercase` | WO-23: Long-horizon control-plane reconciliation | The restored telegramtest run tui-3869250-mtlvp324-1788468819792-1 continued a large pentest-tooling frontend task across a process restart. It made real source mutations and advanced from the first implementation group to todo-p2a. The run was not dead and its model context had ample nominal capacity. |
 | `guide.work-orders-runtime-health-remediation-wo-24-telegram-logical-request-variant-identity-uppercase` | WO-24: Telegram logical request variant identity | Telegram follow-up requests could finish a streamed inference with no visible contract and then fail their one unary compatibility request with HTTP 409: logicalrequestconflict. The observed stream used all 300 completion tokens and ended with finish=length. |
+| `guide.work-orders-runtime-health-remediation-wo-25-memory-compiler-eligibility-and-audit-uppercase` | WO-25: Memory compiler eligibility and outcome audit | Status: complete; implemented, verified, and pushed to origin/main Priority: P1 Incident date: 2026-09-04 PDT / 2026-09-05 UTC Program: September 4 Telegram long-haul repairs |
+| `guide.work-orders-runtime-health-remediation-wo-26-admin-telegram-media-aliases-uppercase` | WO-26: Admin Telegram media alias resolution | Status: complete; implemented, verified, and pushed to origin/main Priority: P1 Incident date: 2026-09-04 PDT / 2026-09-05 UTC Program: September 4 Telegram long-haul repairs |
+| `guide.work-orders-runtime-health-remediation-wo-27-task-verification-authority-uppercase` | WO-27: Separate mutation observations from task verification | Status: complete; implemented, verified, and pushed to origin/main Priority: P1 Incident date: 2026-09-04 PDT / 2026-09-05 UTC Program: September 4 Telegram long-haul repairs |
+| `guide.work-orders-runtime-health-remediation-wo-28-task-scope-evidence-retirement-uppercase` | WO-28: Retire obsolete task evidence after explicit scope changes | Status: complete; implemented, verified, and pushed to origin/main Priority: P2 Incident date: 2026-09-04 PDT / 2026-09-05 UTC Program: September 4 Telegram long-haul repairs |
+| `guide.work-orders-runtime-health-remediation-wo-29-retired-failure-projections-uppercase` | WO-29: Exclude retired failures from active diagnostics | Status: complete; implemented, verified, and pushed to origin/main Priority: P2 Incident date: 2026-09-04 PDT / 2026-09-05 UTC Program: September 4 Telegram long-haul repairs |
 | `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/TELEGRAM-LONGHAUL-2026-09-04.md

@@ -0,0 +1,92 @@
+# September 4 Telegram long-haul remediation
+
+**Status:** complete; all five root repairs verified and delivered to origin/main
+**Baseline:** Omnius main 69c4a160; installed package 1.0.694
+**Incident run:** telegram-64ac9937dc7647a8-1788572475259-1
+**Observation window:** 2026-09-04 18:41–20:43 PDT
+**Owner:** repository repair; user owns publication and subsequent live testing
+
+## Work orders and dependency order
+
+| Work order | Finding | Status | Delivery |
+| --- | --- | --- | --- |
+| [WO-25](WO-25-memory-compiler-eligibility-and-audit.md) | Memory compiler eligibility and outcome audit | complete | cb316de6 |
+| [WO-26](WO-26-admin-telegram-media-aliases.md) | Admin Telegram media alias resolution | complete | bc494850 |
+| [WO-27](WO-27-task-verification-authority.md) | Separate mutation observations from task verification | complete | ce40bfca, cf966ea3, dc60e5bf |
+| [WO-28](WO-28-task-scope-evidence-retirement.md) | Retire obsolete task evidence after explicit scope changes | complete | 24321b30 |
+| [WO-29](WO-29-retired-failure-projections.md) | Exclude retired failures from active diagnostics | complete | 3a1731ad |
+
+WO-25 comes first on the shared request boundary. WO-26, WO-27, and WO-29
+can be implemented independently. WO-28 integrates task-scope retirement with
+WO-25 after the existing steering boundary is traced. Shared agenticRunner.ts
+changes are serialized by the primary implementer.
+
+## Cross-cutting invariants
+
+- Repair causes in Omnius; do not edit the active telegram_test workload or logs.
+- Preserve existing dirty publish/ and docs/DISCOVERY.* changes.
+- Retain graph-proven active evidence, user authority, valid tool transactions,
+  public Telegram isolation, and current explicit verifier contracts.
+- Add deterministic regressions for the observed failures, including tests that
+  assert useful outcomes rather than invocation alone.
+- Use the hermetic network boundary. No live inference, model load, CUDA/service
+  changes, package publication, or installed-package replacement.
+- Check work-order boxes only after implementation and named verification pass.
+- Commit each coherent verified repair using only its owned files; fetch and
+  push the tracked origin/main branch without rewriting history.
+
+## Delivery gates
+
+- [x] All five work orders have implemented root repairs and passing regressions.
+- [x] Compiler outcome telemetry survives final request projection.
+- [x] Affected package regression suites and typechecks pass.
+- [x] Clean workspace-package rebuild succeeds (without bundling publish/).
+- [x] Independent review findings are resolved.
+- [x] Work-order links and acceptance evidence are reconciled.
+- [x] Scoped commits are pushed to origin/main.
+- [x] Publication handoff records the final commit, verification, and operator
+      canaries for the user to run after publishing.
+
+## Verification ledger
+
+- WO-25: 46 compiler/audit/canonical regression tests passed; ineligible high-volume output replay made zero compiler calls. Outcome projection and error-cache tests passed.
+- WO-26: 71 media-focused regressions passed, including admin aliases, replies, OCR batch behavior, explicit paths, and public-chat isolation.
+- WO-27: initial 93 completion tests passed, then 168 broader authority/command-trust tests passed. Final parser/observability refinements passed 93 focused tests with actual declared-verifier receipts.
+- WO-29: 37 workboard and 10 continuity tests passed; superseded failures stay in audit history and leave active diagnostics.
+- WO-28: 13 runner scope tests, 11 pure-boundary tests, 25 interruption lifecycle tests, 10 archive-store tests, and two full mocked runner replays passed. The production replays exercise both primary and brute-force loops.
+- Clean rebuild: `pnpm -r clean`, removal of remaining workspace `tsconfig.tsbuildinfo` caches (excluding node_modules and publish), then `pnpm -r build`: **11 workspace projects passed**.
+- Final full execution suite: **1,511 passed, 3 skipped**, 141 test files.
+- Final full CLI suite: **2,480 passed**, 263 test files. This includes the mocked frontend transport lifecycle gate.
+- Final full orchestrator suite: **2,519 passed, 1 skipped**, 208 test files, with `OMNIUS_SQLITE_TESTS=1`.
+- Aggregate result: **6,510 tests passed, 4 skipped**. No test failed in the final full runs. The last directory-sync refinement passed another 15 scope tests and a workspace build.
+- Full suites use `vitest run --maxWorkers=4 --minWorkers=1` through each package and the existing hermetic network setup.
+- Initial aggregate run exposed the core-rule truncation regression, a parser snapshot loaded during active edits, and an obsolete observability fixture. Core rules now retain a separate typed policy slot; parser and fixture corrections passed fresh targeted replays before the final full run.
+- Local work-order links: **11 checked, zero broken**. Pre-existing publish/ and docs/DISCOVERY.* changes were excluded from every task commit.
+
+Historic checked claims in TRACKER.md are not acceptance evidence for these newly found defects.
+
+## Delivery handoff
+
+Code is delivered through `24321b30` on `origin/main`; each work-order table entry records its scoped repair commits. This document and the master tracker close the repository implementation boundary. The existing installed package, running Telegram workload, and publication files were not replaced by this repair.
+
+The workspace rebuild from clean compiled outputs passed. The user can now perform the normal publish-package bundling/publication procedure and run the following live canaries. Those canaries remain explicitly unexecuted here; deterministic test success is not represented as live-model validation.
+
+## Operator canaries after publication
+
+These are deferred to the user, not unfinished implementation steps:
+
+1. Send an admin-DM voice message and reference it by reply and message ID;
+   confirm immediate scoped resolution and correct transcription attribution.
+2. Resume long work with large tool outputs but ample headroom; confirm zero
+   ineligible compiler calls and inspect retained compiler outcome telemetry.
+3. Replace the task with a different project; confirm old raw source leaves the
+   active context while new instructions and media evidence remain available.
+4. Build a scaffold, install dependencies, then inspect completion; installation
+   alone must not claim behavioral verification. Run the declared checks and
+   confirm fresh verifier evidence permits completion.
+5. Let a bounded failure expire or supersede it; confirm active diagnostics
+   remove it while audit history remains.
+
+Any token-generating canary must first satisfy the repository endpoint/model
+and exact physical GPU preflight gate.
+

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

@@ -4,6 +4,21 @@
 **Checked-item rule:** code, focused tests, and named evidence must all exist
 **Last reconciled:** 2026-09-04
 
+## September 4 field-review follow-up: WO-25 through WO-29
+
+The active Telegram field review found new deterministic defects after the
+earlier acceptance runs. Prior checked sections remain historical evidence;
+they do not close these follow-up repairs. Current authority is
+[TELEGRAM-LONGHAUL-2026-09-04.md](TELEGRAM-LONGHAUL-2026-09-04.md).
+
+- [x] WO-25 memory compiler eligibility and outcome audit.
+- [x] WO-26 admin Telegram media alias resolution.
+- [x] WO-27 task verification authority separated from mutation observations.
+- [x] WO-28 obsolete task evidence retirement after explicit replacement.
+- [x] WO-29 retired failure diagnostics and active projections.
+- [x] Aggregate tests, clean build, independent review, and scoped Git delivery.
+- Publication and live validation are reserved to the user after handoff.
+
 ## Phase 0: durable program boundary
 
 - [x] Create the program directory.

package/docs/work-orders/runtime-health-remediation/WO-25-memory-compiler-eligibility-and-audit.md

@@ -0,0 +1,81 @@
+# WO-25: Memory compiler eligibility and outcome audit
+
+**Status:** complete; implemented, verified, and pushed to origin/main
+**Priority:** P1
+**Incident date:** 2026-09-04 PDT / 2026-09-05 UTC
+**Program:** [September 4 Telegram long-haul repairs](TELEGRAM-LONGHAUL-2026-09-04.md)
+
+## Observed failure
+
+In run telegram-64ac9937dc7647a8-1788572475259-1, 18 compiler operations consumed 5,371.58 seconds (89.53 minutes; 73.2% of 122.27 minutes). All 18 compiler prompts reported compactionEligible=false and only 20–30% occupancy of 262,144 tokens. A nineteenth was pending at the observation cutoff. These are completed operation durations, not inferred GPU compute or proven timeouts.
+
+## Evidence
+
+Paths are relative to /home/roko/Documents/Projects/Adjacent. Live files are
+observational references; sanitized deterministic fixtures must reproduce the
+failure without copying credentials or private conversation content.
+
+- `telegram_test/.omnius/interruptions/telegram-64ac9937dc7647a8.json`
+- `telegram_test/.omnius/context-window-dumps/2026-09-05T03-35-52-688Z-internal-3abab33a54.json`
+
+## Root cause
+
+_applyUnifiedMemoryCompilation bypasses context eligibility above 48,000 raw tool characters, synchronously requests a plan, and validateMemoryCompilationPlan rejects any such plan below the headroom threshold. Canonical projection subsequently changes the request fingerprint and drops the compiler audit.
+
+## Code locations
+
+- `packages/orchestrator/src/agenticRunner.ts — _applyUnifiedMemoryCompilation, _recordContextWindowDump`
+- `packages/orchestrator/src/memory-compiler.ts — validation and analysis`
+- `packages/orchestrator/src/contextWindowDump.ts — compilation audit contract`
+- `packages/orchestrator/tests/unified-memory-compilation.test.ts`
+- `packages/orchestrator/tests/memory-compiler.test.ts`
+- `packages/orchestrator/tests/contextWindowDump.test.ts`
+
+## Repair design
+
+- Use one eligibility contract before inference and validation; raw history volume alone must not invoke a plan that cannot be accepted.
+- Keep useful high-pressure compaction and graph/authority validation intact. Separate deterministic stale-evidence projection (WO-28) from semantic capacity compaction.
+- Record compiler outcome against its actual input fingerprint and explicitly relate it to the final projected request, rather than silently dropping the audit.
+- Preserve invalid-output/exception/hold outcomes as bounded body-free diagnostics without assuming every long request timed out.
+
+## Acceptance checklist
+
+- [x] A large raw-tool request with ample headroom makes zero compiler backend calls across changing turns.
+- [x] An eligible high-pressure request still applies a valid plan while retaining authority and active evidence.
+- [x] Invalid plans preserve the request and emit an inspectable outcome.
+- [x] Compiler outcome remains inspectable when downstream projection changes request fingerprint.
+- [x] Focused regression tests, affected typechecks, and integrated workspace build pass.
+
+## Implementation and verification log
+
+- Regression-first execution reproduced all three failures: four changing
+  low-pressure turns made four compiler calls, downstream projection lost the
+  outcome audit, and backend errors had no distinguishable cached outcome.
+- The runner now uses the validator's exact compaction eligibility before
+  candidate persistence or backend invocation. The former raw-character
+  environment override no longer bypasses capacity eligibility.
+- V2 analysis retains typed `plan`, `invalid_output`, and `backend_error`
+  outcomes without copying exception messages. Cached failures retain their
+  outcome and cache-hit status.
+- Stage receipts retain pre/post compiler fingerprints plus the final wire
+  fingerprint and whether subsequent projection changed the payload. This
+  preserves observability without claiming cross-payload validation.
+- `OMNIUS_SQLITE_TESTS=1 pnpm --filter @omnius/orchestrator exec vitest run
+  tests/unified-memory-compilation.test.ts tests/memory-compiler.test.ts
+  tests/contextWindowDump.test.ts tests/unified-memory-compilation-guard.test.ts
+  tests/agenticRunner-canonical-production.test.ts`: **46 tests passed**.
+- `pnpm --filter @omnius/orchestrator typecheck`: **passed**.
+- Source/test whitespace checks passed. Integrated build and independent review
+  will be recorded in the program verification ledger.
+
+## Delivery
+
+- Commits: `cb316de6` on `origin/main`.
+- Clean `pnpm -r build` passed for all 11 workspace packages/apps. Final aggregate suite evidence is in the linked program ledger.
+
+## Publication boundary
+
+Repository repair and deterministic verification are this order's completion
+boundary. The user will publish the package and then perform live validation.
+No package publication, installed-package replacement, runtime-state repair,
+or service restart is authorized by this order.

package/docs/work-orders/runtime-health-remediation/WO-26-admin-telegram-media-aliases.md

@@ -0,0 +1,93 @@
+# WO-26: Admin Telegram media alias resolution
+
+**Status:** complete; implemented, verified, and pushed to origin/main
+**Priority:** P1
+**Incident date:** 2026-09-04 PDT / 2026-09-05 UTC
+**Program:** [September 4 Telegram long-haul repairs](TELEGRAM-LONGHAUL-2026-09-04.md)
+
+## Observed failure
+
+The active run called transcribe_file(path='message_id:2747') at 19:03 PDT, received a literal filesystem-not-found error, and reached successful real-file transcription only at 19:58. Earlier aliases 'latest' and message_id:2744 failed similarly. The recovery delay overlaps WO-25 compiler time.
+
+## Evidence
+
+Paths are relative to /home/roko/Documents/Projects/Adjacent. Live files are
+observational references; sanitized deterministic fixtures must reproduce the
+failure without copying credentials or private conversation content.
+
+- `telegram_test/.omnius/completion-ledgers/telegram-64ac9937dc7647a8-1788572475259-1.json`
+
+## Root cause
+
+Telegram media descriptions advertise aliases to all callers, but applyTelegramScopedMemoryTools installs alias adapters only outside telegram-admin-dm. Raw transcription resolves the alias against the workspace as a filename.
+
+## Code locations
+
+- `packages/cli/src/tui/telegram-bridge.ts — media descriptions, tool assembly, scoped media resolver`
+- `packages/execution/src/tools/transcribe-tool.ts — filesystem path boundary (preserve generic tool semantics)`
+- `packages/cli/tests/telegram-media-cache.test.ts`
+- `packages/cli/tests/telegram-public-media.test.ts`
+- `packages/cli/tests/telegram-media-evidence.test.ts`
+- `packages/cli/tests/telegram-admin-media-aliases.test.ts`
+
+## Repair design
+
+- Separate Telegram reference resolution from public-chat filesystem/memory restrictions.
+- Resolve message_id, latest, and reply aliases in admin DMs using the current chat's cached media.
+- Preserve legitimate explicit admin filesystem paths and retain group/public isolation.
+- Apply the adapter consistently to advertised media tools affected by the same missing boundary; preserve media evidence attribution.
+
+## Acceptance checklist
+
+- [x] Admin-DM message_id, latest, and reply references reach the selected cached file, never a literal alias filename.
+- [x] Explicit permitted admin paths retain existing behavior.
+- [x] Missing and cross-chat references fail precisely without exposing unrelated media or initiating broad filesystem search.
+- [x] Public/group path restrictions and media-evidence attribution remain intact.
+- [x] Focused media/transport tests and CLI typecheck pass.
+
+## Implementation and verification log
+
+- Added an admin-only alias adapter for image reading, OCR, vision, PDF extraction,
+  transcription, video understanding, and audio analysis. It reuses the existing
+  chat/kind selection and bounded reply-chain resolver independently of public
+  memory and filesystem restrictions.
+- Added `video_understand`, `audio_analyze`, and `telegram_media_recent` to the
+  admin toolset because incoming-media instructions already advertise those
+  capabilities. Explicit tool-policy filtering remains in force.
+- Exact missing or foreign-chat message aliases fail before raw execution or
+  creative-workspace path fallback. Admin absolute/relative files remain raw
+  filesystem inputs; an existing local filename takes precedence over an equal
+  cached basename. Public/group adapters retain their scope and restrictions.
+- Preserved admin OCR batch/output arguments, URL-video operations, and explicit
+  microphone modes. Successful alias-based transcription and audio analysis use
+  the existing media-evidence attribution callbacks.
+- Independent review found that omitted OCR batch input could select a cached
+  image instead of preserving the raw required-directory error. Batch mode now
+  bypasses all alias/default-media selection. A regression test compares the
+  original missing-input error with the adapted result while cached images exist.
+- Regression evidence: the assembled-toolset test first executes the raw
+  transcription path with a nonexistent `message_id:10` filename and confirms
+  the former filesystem-not-found result. It then verifies that the repaired
+  real admin tool assembly sends the cached filename to a mocked executor.
+  The missing-file reproduction returns before any transcription/model request.
+- Final verification on 2026-09-04 PDT: **71 tests passed** across
+  `telegram-admin-media-aliases.test.ts` (33), `telegram-media-evidence.test.ts`
+  (9), `telegram-media-cache.test.ts` (7), `telegram-public-media.test.ts` (11),
+  and `telegram-transport-contract.test.ts` (11), with the CLI hermetic network
+  boundary enabled. This final run includes the raw alias-boundary and missing
+  OCR batch-input regressions. `pnpm --dir packages/cli typecheck` and
+  `git diff --check` passed after the batch-input follow-up.
+- No live inference, publication, installed-package replacement, runtime-state
+  change, or service restart was performed. Parent task owns the delivery commit.
+
+## Delivery
+
+- Commits: `bc494850` on `origin/main`.
+- Clean `pnpm -r build` passed for all 11 workspace packages/apps. Final aggregate suite evidence is in the linked program ledger.
+
+## Publication boundary
+
+Repository repair and deterministic verification are this order's completion
+boundary. The user will publish the package and then perform live validation.
+No package publication, installed-package replacement, runtime-state repair,
+or service restart is authorized by this order.