omnius 1.0.591 → 1.0.592

package/docs/work-orders/hermes-architecture-deltas/INDEX.md

@@ -0,0 +1,38 @@
+# Hermes Architecture Deltas Workorder Index
+
+Status: ready for implementation planning. These documents are workorders only; they do not claim the features are implemented.
+
+Source baseline:
+- Omnius repository: `/home/robit/Documents/repositories/open-agents-1`
+- Hermes comparison checkout: `/home/robit/Documents/repositories/hermes-agent`
+- Hermes commit inspected: `6f6eb871d83415fe2980f3483cc41a435ba22196`
+- Hermes version inspected: `0.15.1`
+- AIWG framing used: `sdlc/architecture-evolution`, `sdlc/flow-handoff-checklist`, `sdlc/flow-requirements-evolution`
+
+## Feature Workorders
+
+| Folder | Workorder | Purpose | Current State |
+| --- | --- | --- | --- |
+| `01-public-scrutiny-provenance-control/` | [WORKORDER.md](01-public-scrutiny-provenance-control/WORKORDER.md) | Runtime public Telegram scrutiny modes with human and agent-controlled provenance escalation. | Planned |
+| `02-context-engine-plugin-boundary/` | [WORKORDER.md](02-context-engine-plugin-boundary/WORKORDER.md) | Extract context assembly, compaction, and evidence framing behind a pluggable context engine boundary. | Planned |
+| `03-typed-gateway-event-stream/` | [WORKORDER.md](03-typed-gateway-event-stream/WORKORDER.md) | Separate runner facts from Telegram/TUI rendering through typed events and adapter dispatch. | Planned |
+| `04-task-local-gateway-context/` | [WORKORDER.md](04-task-local-gateway-context/WORKORDER.md) | Add task-local gateway/session context using `AsyncLocalStorage` to prevent cross-chat and cross-run bleed. | Planned |
+| `05-process-lifecycle-monitoring-notifications/` | [WORKORDER.md](05-process-lifecycle-monitoring-notifications/WORKORDER.md) | Keep Omnius's lease registry as authority and add watcher, adoption, notification, and legacy kill-path cleanup. | Planned |
+| `06-vision-evidence-routing-ladder/` | [WORKORDER.md](06-vision-evidence-routing-ladder/WORKORDER.md) | Route visual evidence from cheap observation to OCR to auxiliary vision based on request-derived information need. | Planned |
+| `07-durable-multi-agent-kanban/` | [WORKORDER.md](07-durable-multi-agent-kanban/WORKORDER.md) | Add durable, inspectable work boards for long admin tasks and disputed public factual work. | Planned |
+| `08-completion-critic-reconciliation-ledger/` | [WORKORDER.md](08-completion-critic-reconciliation-ledger/WORKORDER.md) | Turn completion review into a durable claim/evidence ledger with critic reconciliation packets. | Planned |
+
+## Carryover Rules
+
+- Do not encode scenario-specific phrase filters as completion or scrutiny logic.
+- Any escalation or completion gate must be driven by the current request, proposed claims, observed tool results, and explicit human or agent-declared state.
+- Keep public Telegram bounded by default; strict review modes must be intentional, reversible, and time-limited.
+- Never let a renderer label backend `incomplete_verification` as completed.
+- Never authorize process termination from command-name matching alone; lease ownership and identity verification remain mandatory.
+
+## Global Completion Metrics
+
+- Every feature folder has an `INDEX.md` and `WORKORDER.md`.
+- Every workorder names code anchors in Omnius and Hermes.
+- Every workorder includes phases, file-by-file implementation notes, tests, rollout controls, and measurable completion criteria.
+- A future agent can update progress checkboxes without rereading this chat.

package/docs/work-orders/omnius-context-engineering-behavior-fixes.md

@@ -0,0 +1,281 @@
+# Omnius Context Engineering Behavior Fixes
+
+Date: 2026-06-29
+
+Source observation: current Omnius behavior while supervising a noclip/earth sidebar cleanup task. The observed run mixed internal cognitive-agent artifacts with user-task artifacts, repeated stale edit attempts after the file had changed, and overclaimed completion despite stale or missing verification.
+
+## Work Order
+
+### 1. Isolate Internal Runners From User-Task Artifacts
+
+Status: implemented in this work session.
+
+Problem: DMN, emotion, and SNR evaluator runners instantiate `AgenticRunner` as normal task runners. Their internal prompts can write handoffs, reflections, completion ledgers, provenance, and task memory that later pollute user-task context.
+
+Implementation:
+- Add `artifactMode?: "user-task" | "internal"` to `AgenticRunnerOptions`.
+- Treat `subAgent: true` as isolated for backward compatibility, but use `artifactMode: "internal"` for cognitive helper runners.
+- Disable automatic cross-task handoff read/write in internal mode.
+- Disable task reflection read/write in internal mode.
+- Avoid creating completion contracts/ledgers for internal mode.
+- Avoid writing consolidation/provenance/task-summary artifacts for internal mode.
+- Pass `artifactMode: "internal"` from DMN, emotion, and SNR internal runners.
+
+Acceptance:
+- Internal runner prompts cannot become `.omnius/handoffs/latest.json`.
+- Internal zero-turn failures cannot become task reflections.
+- User-task runners continue writing normal artifacts.
+
+### 2. Replace Loop Escape Equals `task_complete`
+
+Status: implemented in this work session.
+
+Problem: the loop intervention still injects a mandatory `task_complete` directive after detecting repetition. This encourages partial or false completion.
+
+Implementation:
+- Remove the mandatory `task_complete` wording from loop intervention.
+- Instruct the model to stop repeating the implicated tool family.
+- Prefer verification when files changed, reread the exact target once for stale edits, ask the user if genuinely blocked, or report incomplete/blocking status.
+
+Acceptance:
+- Loop intervention text never says to call `task_complete` with whatever is available.
+- Existing `ask_user` circuit-breaker remains the high-tier escape path.
+
+### 3. Hard-Block Stale Edit Loops
+
+Status: implemented in this work session.
+
+Problem: exact duplicate detection does not catch stale edit families. The observed run repeatedly retried an old `file_edit` even after the target text was already absent.
+
+Implementation:
+- Add a stale edit fingerprint for `file_edit`, `file_patch`, and `batch_edit`.
+- Track repeated failed edit families by path, normalized target text, and error class.
+- After the threshold, block the edit before dispatch and provide a concrete recovery instruction.
+- When the tool output indicates the old text is absent or no replacement occurred, record the failure family.
+
+Acceptance:
+- A repeated `old_string not found` edit is blocked after repeated failures.
+- The block tells the model to read the current target once, verify if already satisfied, or choose a different patch.
+
+### 4. Make Completion State Truth-Based, Not Summary-Based
+
+Status: implemented in this work session.
+
+Problem: the completion ledger records tool evidence but only creates claims from model-proposed completion text. Timeout/open runs can end with evidence but no truth-state synthesis.
+
+Implementation:
+- Track mutation and verification evidence from tool results.
+- Add finalization helpers that derive unresolved items when mutations occur after the last successful verification.
+- Mark repeated stale edit blocks as unresolved evidence.
+- Finalize open ledgers as `incomplete_verification` when unresolved evidence exists.
+
+Acceptance:
+- A run with file mutations after its last verification cannot look cleanly complete.
+- A timeout/open run can still explain unresolved evidence without a `task_complete` summary.
+
+### 5. Stop Todo Chunker Overclaiming Completion
+
+Status: implemented in this work session.
+
+Problem: todo context chunks are marked `completed` even when summaries contain unresolved work, failed edit loops, or stale verification.
+
+Implementation:
+- Add `partial` and `unverified` chunk statuses.
+- Compute chunk status from unresolved and verification text instead of always setting `completed`.
+- Make heuristic fallback conservative: never invent completion when evidence is ambiguous.
+
+Acceptance:
+- A chunk containing unresolved failures is not marked `completed`.
+- A chunk lacking verification is `unverified` unless explicit verification evidence exists.
+
+### 6. Add Defensive Handoff and Reflection Quality Gates
+
+Status: implemented in this work session.
+
+Problem: even with internal isolation, stale/low-quality handoffs and reflections should be rejected at the storage boundary.
+
+Implementation:
+- Add handoff metadata for artifact mode and quality.
+- Reject handoffs for internal prompt families, zero-turn/no-tool runs, empty summaries with no files/tools, and known SNR/DMN/emotion evaluator prompts.
+- Reject task reflections for the same internal prompt families and zero-progress helper failures.
+- Fix duplicate `failedPaths` assignment in reflection serialization.
+
+Acceptance:
+- Internal prompt families cannot be persisted as user-task handoff/reflection artifacts.
+- Empty zero-tool helper failures are quarantined instead of injected into later user tasks.
+
+## Verification Plan
+
+- Add focused unit coverage for artifact isolation, stale edit blocking, loop intervention wording, handoff/reflection quality gates, completion ledger finalization, and todo chunk status.
+- Run the affected test files first:
+  - `packages/orchestrator/tests/critic.test.ts`
+  - `packages/orchestrator/tests/completionLedger.test.ts`
+  - `packages/orchestrator/tests/reflection.test.ts`
+  - `packages/cli/tests/task-handoff.test.ts`
+  - `packages/cli/tests/dmn-engine.test.ts`
+  - `packages/cli/tests/emotion-engine.test.ts`
+- Run the relevant package test command after focused tests pass.
+
+## Live Multimodal Regression Work Order
+
+Date: 2026-06-30
+
+Source observation: aggressive live testing surfaced visual-memory CLIP wrapper failures, active todo overclaiming after failed tool calls, JSON/headless lifecycle drift, and noisy global context recall. Follow-up correction: context selection must be semantic/vector/inference based, not hard-coded English keyword filters.
+
+### 7. Fix CLIP/SigLIP Feature Output Unwrapping
+
+Status: implemented.
+
+Problem: `visual_memory teach` and related multimodal CLIP paths failed when transformers returned `BaseModelOutputWithPooling` instead of a tensor, causing `.norm(...)` to crash.
+
+Implementation:
+- Add a shared Python helper that unwraps `image_embeds`, `text_embeds`, `pooler_output`, `last_hidden_state[:, 0]`, tuple/list outputs, or plain tensors before normalization.
+- Inject the helper into `visual_memory` object teach/recognize paths.
+- Inject the helper into multimodal episode image/text CLIP embedding paths.
+- Add source-level unit coverage for wrapper support.
+
+### 8. Make Vision Failures Actionable First
+
+Status: implemented.
+
+Problem: warnings and dependency noise could hide the actual traceback root cause from the model.
+
+Implementation:
+- Export and harden `summarizeProcessFailure`.
+- Put the final exception line first as `Root cause: ...`.
+- Preserve traceback context and tail output below it.
+
+### 9. Truth-Reconcile Active Todos From Tool Evidence
+
+Status: implemented.
+
+Problem: the live agent marked “Teach each object to visual_memory” completed even though every matching `visual_memory teach` call failed.
+
+Implementation:
+- Add `todoTruth` reconciliation.
+- Downgrade completed todos to `blocked` when matching tool-family evidence failed and no later same-family success exists.
+- Run reconciliation immediately after successful `todo_write`, before verification nudges and todo chunking.
+- Add a system message instructing the model to reconfigure the affected subtask instead of overclaiming.
+
+### 10. First-Class Nested Todo Decomposition
+
+Status: implemented.
+
+Problem: `parentId` existed in storage but was not an explicit task decomposition contract and parents could overclaim child completion.
+
+Implementation:
+- Expand `todo_write` instructions for stable ids, `parentId`, leaf-subtask work, and evidence-driven tree rewrites.
+- Add parent truth reconciliation: a parent cannot be completed while any child is pending, in progress, or blocked.
+- Render nested todos in the TUI with indentation.
+- Add tests for parent/child persistence and parent downgrade behavior.
+
+### 11. Semantic Context Selection, Not English Keyword Filters
+
+Status: implemented.
+
+Problem: persisted failure modes and preflight memories must not be admitted by hard-coded English regex/stopword heuristics.
+
+Implementation:
+- Remove semantic keyword filtering from `failureHandoff`.
+- Add runner-side task-to-failure-pattern selection using embedding batch cosine similarity.
+- Add inference fallback for failure-pattern relevance when embeddings are unavailable.
+- If neither vector nor inference scoring is available, inject no persisted failure patterns rather than guessing.
+- Convert preflight memory recall to async embedding retrieval and cosine scoring over stored episode embeddings.
+- Add source guards to prevent reintroducing the keyword matcher/internal-recall filter.
+
+### 12. Explicit Degraded Completion Contract
+
+Status: implemented.
+
+Problem: the resolution gate blocked completion even when the original user task explicitly allowed documenting a tool failure as the desired fallback outcome.
+
+Implementation:
+- Add an auxiliary inference verdict for degraded-completion allowance.
+- Accept degraded completion only when the inference verdict says the original request permits it, the summary discloses the failure, and fallback evidence exists.
+- Update the verifier prompt to understand explicitly permitted degraded fallback.
+
+### 13. Headless JSON Lifecycle
+
+Status: implemented.
+
+Problem: `omnius --json` could emit a final JSON object but keep running post-task trajectory/memory side effects and could report completed without the actual runner result.
+
+Implementation:
+- Add `onRunResult` callback to `runWithTUI`.
+- JSON mode uses runner `completed/status/summary/turns/toolCalls/filesEdited/testsRun`.
+- Headless mode skips non-critical post-run identity/archive/trajectory/cohere side effects.
+- Headless errors throw back to JSON mode instead of directly exiting inside `runWithTUI`.
+- Add controlled force-exit for JSON CLI with test opt-out.
+
+### 14. Model Resolution Telemetry
+
+Status: implemented.
+
+Problem: live testing showed ambiguity between requested visible model and models used by auxiliary/background calls.
+
+Implementation:
+- Emit status telemetry for main runner model resolution.
+- Emit status telemetry for completion-resolution and failure-pattern relevance inference calls.
+
+### 15. Crossmodal Self-Test Isolation
+
+Status: implemented.
+
+Problem: crossmodal self-test used the live repo `.omnius/memory.db`, printed false retrieval results, and still exited successfully.
+
+Implementation:
+- Use temporary isolated memory DBs.
+- Fail when image/text embeddings are unavailable or retrieval top result is false.
+- Close stores and remove temp directories.
+
+### 16. Truth-Based Terminal Completion After Verified Todo Closure
+
+Status: implemented in source; pending publish/live reinstall verification.
+
+Problem: live headless testing with `robit/ornith:35b` completed the nested todo tree, edited the requested files, ran the declared verification command successfully, and then stalled after the REG-31 "call task_complete" prompt. The runner had enough structured truth evidence but still depended on another model turn for the final terminal action.
+
+Implementation:
+- Add a pure truth-based completion decision module.
+- Require all todos completed, zero unresolved verification failures, and a fresh successful declared `verifyCommand`.
+- Prefer structural matching against `todo.verifyCommand` for validation success.
+- Move generic command-name completion detection behind `OMNIUS_ENABLE_GENERIC_COMPLETION_COMMAND_HEURISTIC=1`.
+- Synthesize terminal completion before another model request, while still running existing completion/provenance/backward-pass gates.
+
+Acceptance:
+- A fully verified todo tree can finish headless JSON without waiting on a final model-generated `task_complete`.
+- Partial work, open children, stale validation, or unresolved verification failures remain incomplete.
+- Completion automation is anchored to declared verification evidence, not English command-name filters.
+
+### 17. Keep Verify-Command Evidence Separate From Artifact Evidence
+
+Status: implemented in source; pending publish/live reinstall verification.
+
+Problem: a live local run marked a final todo completed with a combined `verifyCommand` it had not run exactly. REG-37 recorded the missing verifier, but REG-38 artifact inspection then cleared the same aggregate failure because the files existed. The model then called `task_complete` and overclaimed the combined verifier as proven.
+
+Implementation:
+- Add structural verification-command matching.
+- Accept exact verifier commands and reliable `verify && echo ...` suffixes.
+- Reject `verify && echo ok || echo failed` wrappers because they can mask failure with exit 0.
+- Allow a conjunctive verifier to be satisfied by separately successful reliable component commands.
+- Track verify-command failures and artifact-inspection failures separately, then combine them into the completion gate.
+- Block `task_complete` while any todo verification failure remains unresolved.
+- Replace todo-write verification nudge content regex with structured `verifyCommand` / `declaredArtifacts` evidence checks.
+
+Acceptance:
+- Artifact existence cannot clear a missing `verifyCommand`.
+- A `task_complete` call is held when the todo tree still has unresolved verification evidence.
+- Verification nudges are structural, not English content heuristics.
+
+### 18. Preserve Phase Archives in ESM Builds
+
+Status: implemented in source; pending publish/live reinstall verification.
+
+Problem: live local JSON runs emitted `Phase archive failed (non-fatal): require is not defined`. Phase archives are context-continuity artifacts for long tasks; losing them weakens later phase recall and forensic review.
+
+Implementation:
+- Replace runtime `require("node:fs")` and `require("node:path")` uses in `agenticRunner.ts` with existing ESM-safe top-level imports.
+- Cover phase archives, KG summary writes/pruning, and checkpoint persistence in the same pass.
+
+Acceptance:
+- ESM-built CLI runs can write `.omnius/phases/` archives without `require` failures.
+- Long-task context contraction keeps disk-backed phase recovery available.

package/docs/work-orders/telegram-dropbear-context-rca-workorder.md

@@ -0,0 +1,202 @@
+# Telegram Dropbear Context Engineering RCA Work Order
+
+Date: 2026-07-01
+
+Observed run: `/home/roko/Documents/Projects/Adjacent/telegram_test/.omnius`, run id `1782873796963-i5r7mv`.
+
+Task under observation: get a meaningful gear-sonic training run with observed progress on the Dropbear MJCF/URDF after addressing closed-loop knee components.
+
+## Evidence Snapshot
+
+- The run made one successful mutation: `dropbear_mjcf/dropbear_mjcf.xml` changed `RL_Revolute28` to `<joint name="RL_Revolute28" type="weld" />`.
+- Immediately afterward, the model retried the pre-mutation `old_string` and received repeated `old_string not found` failures.
+- The focus supervisor then forced `required_next_action=update_todos`, which blocked useful recovery reads, patches, and verification attempts.
+- The run kept emitting blocked edits, sed/python rewrites, a partial `task_complete`, and more blocked reads through at least turn 28.
+- Main context grew from about 73k estimated tokens after the successful edit to about 92.7k estimated tokens by turn 28.
+- System prompt content grew from about 142k chars to about 230k chars.
+- The final main dump had dozens of `[RUN EVIDENCE]` and focus-supervisor system messages, including repeated synthetic failures.
+- The workboard existed but had no cards, decisions, or diagnostics.
+- The completion ledger remained `open`; no meaningful gear-sonic training verification was run.
+
+## Work Orders
+
+### WO-TD-01: Stale Edit Recovery Must Read Current Truth, Not Replan Forever
+
+Status: implemented
+
+Root cause: repeated stale edit failures currently force `update_todos` for non-shell tools. For an `old_string not found` family, this is the wrong recovery state.
+
+Anchors:
+- `packages/orchestrator/src/focusSupervisor.ts`
+- `packages/orchestrator/src/agenticRunner.ts`
+- `packages/orchestrator/tests/focusSupervisor.test.ts`
+
+Implementation:
+- Classify stale edit failure samples in the focus supervisor.
+- Repeated stale `file_edit`, `file_patch`, or `batch_edit` failures must set `requiredNextAction=read_authoritative_target`.
+- After the authoritative read succeeds, clear that directive and permit a fresh target-specific edit or verification.
+- Do not use `update_todos` as the default escape hatch for stale edit families.
+
+Acceptance:
+- Two `old_string not found` failures produce a `read_authoritative_target` directive.
+- A `file_read` of the target satisfies the directive.
+- A different edit target in the same file is not blocked just because an old edit target failed.
+
+Verification:
+- Covered by `tests/focusSupervisor.test.ts`.
+
+### WO-TD-02: Directive Escalation Must Terminate Cleanly After Repeated Ignoring
+
+Status: implemented
+
+Root cause: the observed run ignored 27 focus directives and kept accumulating blocked tool calls. The supervisor continued asking for the same action without forcing a terminal incomplete/blocker path.
+
+Anchors:
+- `packages/orchestrator/src/focusSupervisor.ts`
+- `packages/orchestrator/src/agenticRunner.ts`
+- `packages/orchestrator/tests/focusSupervisor.test.ts`
+
+Implementation:
+- Add an ignored-directive escalation threshold.
+- Once the threshold is crossed with no satisfying mutation/read/verification, force `requiredNextAction=report_incomplete`.
+- In terminal incomplete state, permit `task_complete` only as an incomplete/blocker report.
+- Stop appending broad blocked-family lists indefinitely.
+
+Acceptance:
+- Repeatedly ignoring a recovery directive transitions to `terminal_incomplete`.
+- After terminal incomplete, edit/read/shell variants are blocked.
+- A reporting tool is allowed so the run can end truthfully.
+
+Verification:
+- Covered by `tests/focusSupervisor.test.ts`.
+
+### WO-TD-03: Focus Action Families Must Be Target-Specific For Edits
+
+Status: implemented
+
+Root cause: focus supervisor action families collapse all edits to `tool:path`. In the observed run, a stale `RL_Revolute28` edit contaminated later distinct joint edits and line patches in the same XML.
+
+Anchors:
+- `packages/orchestrator/src/focusSupervisor.ts`
+- `packages/orchestrator/src/agenticRunner.ts`
+- `packages/orchestrator/tests/focusSupervisor.test.ts`
+
+Implementation:
+- Build edit action families from tool name, path, normalized edit target, patch mode/offset/limit, and error class where available.
+- Keep shell action families command-based, but trim and hash long commands rather than injecting huge command prefixes.
+- Preserve a separate coarse path lock only for full-file overwrite repair blocks.
+
+Acceptance:
+- A repeated stale edit for `RL_Revolute28` blocks only that edit family.
+- A fresh `file_patch` for a different offset/target in the same XML can pass after the required authoritative read.
+- The directive frame no longer grows with long sed/python command bodies.
+
+Verification:
+- Covered by `tests/focusSupervisor.test.ts`.
+
+### WO-TD-04: Context Evidence Must Fold Repeats And Demote Synthetic Failures
+
+Status: implemented
+
+Root cause: the context engine injects every recorded tool event as high-authority `[RUN EVIDENCE]`, including repeated focus blocks and stale discovery reads.
+
+Anchors:
+- `packages/orchestrator/src/contextEngine.ts`
+- `packages/orchestrator/src/agenticRunner.ts`
+- `packages/orchestrator/tests/contextEngine.test.ts`
+
+Implementation:
+- Fold tool evidence by family before rendering system evidence.
+- Keep successes, latest mutations, latest verification results, and first/last unresolved failures.
+- Collapse repeated focus-supervisor synthetic failures into one counted summary.
+- Cap evidence injection separately from raw conversation/tool results.
+
+Acceptance:
+- Repeated identical focus blocks render as one summary with a repeat count.
+- Evidence diagnostics report retained and dropped/folded counts.
+- Large early discovery listings do not stay as repeated high-authority system evidence once more specific evidence exists.
+
+Verification:
+- Covered by `tests/contextEngine.test.ts`.
+
+### WO-TD-05: Context Engine Compaction Must Affect Live Requests
+
+Status: implemented
+
+Root cause: `AgenticRunner` calls `contextEngine.compact()` but discards its output, while `contextEngine.build()` still prepends extra evidence to the live request.
+
+Anchors:
+- `packages/orchestrator/src/agenticRunner.ts`
+- `packages/orchestrator/src/contextEngine.ts`
+- `packages/orchestrator/tests/agenticRunner-context-behavior.test.ts`
+- `packages/orchestrator/tests/contextEngine.test.ts`
+
+Implementation:
+- Apply context-engine compaction output to the live message list when it actually compacts.
+- Avoid duplicating engine-added evidence already present in the active context.
+- Carry latest SNR/evidence metrics into focus-supervisor proposed-call snapshots.
+
+Acceptance:
+- A compacted context-engine output reduces the live message list before backend calls.
+- `_buildFocusContextSnapshot()` includes raw discovery chars, active evidence chars, active frame chars, and signal-to-noise ratio.
+- Context dumps and focus decisions see the same pressure/noise picture.
+
+Verification:
+- Covered by `tests/contextEngine.test.ts`, `tests/agenticRunner-context-behavior.test.ts`, and package build.
+
+### WO-TD-06: Completion Ledger Must Finalize Open Failure Runs Truthfully
+
+Status: implemented
+
+Root cause: the ledger contained evidence of mutation, stale edit failures, and no final verification, but stayed `open`.
+
+Anchors:
+- `packages/orchestrator/src/completionLedger.ts`
+- `packages/orchestrator/src/agenticRunner.ts`
+- `packages/orchestrator/tests/completionLedger.test.ts`
+
+Implementation:
+- Finalize open ledgers using evidence when a run exits or hits a terminal incomplete state.
+- Treat unresolved stale edit families, mutations after last verification, and missing verification after code mutations as incomplete verification.
+- Record focus terminal-incomplete events as unresolved ledger evidence.
+
+Acceptance:
+- A ledger with an unverified code mutation finalizes as `incomplete_verification`.
+- A ledger with unresolved stale edit blocks finalizes as `incomplete_verification`.
+- A run that reaches terminal incomplete writes the ledger status before exit.
+
+Verification:
+- Covered by `tests/completionLedger.test.ts`; runner bridge typechecked by package build.
+
+### WO-TD-07: Complex Tasks Must Seed A Durable Workboard Or Todo Tree
+
+Status: implemented
+
+Root cause: this robotics/training task had an empty workboard despite requiring discovery, model repair, integration, training, and verification.
+
+Anchors:
+- `packages/orchestrator/src/agenticRunner.ts`
+- `packages/execution/src/tools/workboard.ts`
+- `packages/execution/tests/workboard.test.ts`
+- `packages/orchestrator/tests/agenticRunner-context-behavior.test.ts`
+
+Implementation:
+- Detect complex implementation/training tasks and seed a minimal board or nested todo skeleton before freeform tool use.
+- Require cards or nested todos for repair, integration, training run, and observed verification.
+- Attach tool evidence to active cards so completion review has structured state.
+
+Acceptance:
+- A multi-step training/robotics task starts with non-empty durable decomposition.
+- Workboard cards or nested todos update as evidence is collected.
+- Completion review sees unresolved cards/blockers when verification has not happened.
+
+Verification:
+- Runner seed-card path guarded by `tests/agenticRunner-context-behavior.test.ts`.
+
+## Verification Checklist
+
+- [x] `pnpm --filter @omnius/orchestrator test -- tests/focusSupervisor.test.ts`
+- [x] `pnpm --filter @omnius/orchestrator test -- tests/contextEngine.test.ts`
+- [x] `pnpm --filter @omnius/orchestrator test -- tests/completionLedger.test.ts`
+- [x] `pnpm --filter @omnius/orchestrator test -- tests/agenticRunner-context-behavior.test.ts`
+- [x] `pnpm --filter @omnius/orchestrator build`