@herjarsa/omo-meta-governor 0.19.3 → 0.19.5

package/README.md

@@ -43,7 +43,7 @@ The plugin registers 15 tools the LLM can invoke. All available immediately on i
 
 | Tool | What it does | Use case |
 |------|-------------|----------|
-| `omo_search` | Semantic code search via codegraph/graphify with AFT fallback | Architecture questions, finding features — USE THIS FIRST |
+| `omo_search` | Semantic code search via codegraph/graphify with AFT fallback | Architecture questions, finding features — USE THIS FIRST |
 | `omo_find` | Exact symbol lookup (definition + direct callers) via codegraph node | "Find the function `validateToken`" |
 | `omo_impact` | Impact analysis: callers, transitive callers, test files, doc files | Run BEFORE modifying a function |
 | `omo_path` | Shortest conceptual path between two concepts via graphify | "How does auth connect to database?" |
@@ -90,11 +90,11 @@ Structured JSONL logs at `~/.config/opencode/meta-governor.log` with size-based
 ## Persistence
 
 Lessons learned by the plugin persist in **SQLite** at `~/.omo-meta-governor/meta-governor.db`
-with full-text search (FTS5) for fast recall. Zero dependencies needed — uses Bun's built-in
+with full-text search (FTS5) for fast recall. Zero dependencies needed — uses Bun's built-in
 `bun:sqlite`.
 
-Optionally, the Opción A tools (`omo_remember`, `omo_recall_mcp`, `omo_rule`, `omo_history`,
-`omo_note`) can bridge to AgentMemory and Magic Context via `session.prompt()` — the LLM
+Optionally, the Opción A tools (`omo_remember`, `omo_recall_mcp`, `omo_rule`, `omo_history`,
+`omo_note`) can bridge to AgentMemory and Magic Context via `session.prompt()` — the LLM
 receives a structured instruction to call the appropriate MCP tool.
 
 ## Graph Sync (v0.11.0)
@@ -167,39 +167,39 @@ only when the **entire** plan is verified done by Oracle. The new markers:
 | Marker | Effect |
 |--------|--------|
 | `<promise>DONE</promise>` | Per-phase hint. Logged but does NOT latch intervention (when `phaseAwareDoneSignal: true`). |
-| `<promise>PHASE-N-COMPLETE</promise>` | Per-phase hint (e.g. `<promise>PHASE-1-COMPLETE</promise>`). Same as DONE — logged, does NOT latch. |
+| `<promise>PHASE-N-COMPLETE</promise>` | Per-phase hint (e.g. `<promise>PHASE-1-COMPLETE</promise>`). Same as DONE — logged, does NOT latch. |
 | `<promise>PLAN-COMPLETE</promise>` | Terminal. Latches intervention when Oracle has verified. |
 
-**Migration**: existing v0.10.0–v0.14.x users keep working without changes (default
+**Migration**: existing v0.10.0–v0.14.x users keep working without changes (default
 `phaseAwareDoneSignal: false` preserves the legacy single-task behavior). Set the
 flag to `true` and switch your terminal marker to `PLAN-COMPLETE` to enable
 multi-phase governance.
 
-## v0.16.0 — Audit remediation: memory hygiene, dead code, tool coverage, CI
+## v0.16.0 — Audit remediation: memory hygiene, dead code, tool coverage, CI
 
-v0.16.0 closes the 50+ findings from the multi-front audit at `.omo/ulw-research/20260727-000530/plan-audit-v0.15.0.md`. The release is **additive in behavior, no breaking API changes** for users — only internal cleanup, dead code removal, and CI hardening.
+v0.16.0 closes the 50+ findings from the multi-front audit at `.omo/ulw-research/20260727-000530/plan-audit-v0.15.0.md`. The release is **additive in behavior, no breaking API changes** for users — only internal cleanup, dead code removal, and CI hardening.
 
 ### Highlights
 
 #### Memory hygiene (F1)
 
-- **`AuditStateCache`** (`src/audit-state-cache.ts`) — TTL+LRU bounded cache (100 entries, 1h TTL) replaces the bare `Map` that accumulated audit state without bounds. Stale sessions are evicted automatically.
-- **`TTLQueue`** (`src/ttl-queue.ts`) — TTL-based expiration for `pendingBotFeedback` and `pendingViolations` queues. Previously unbounded.
-- Removed dynamic `require("node:fs")` inside `shouldInjectPlanReminder` — replaced with static ESM imports (no more runtime module resolution failures).
+- **`AuditStateCache`** (`src/audit-state-cache.ts`) — TTL+LRU bounded cache (100 entries, 1h TTL) replaces the bare `Map` that accumulated audit state without bounds. Stale sessions are evicted automatically.
+- **`TTLQueue`** (`src/ttl-queue.ts`) — TTL-based expiration for `pendingBotFeedback` and `pendingViolations` queues. Previously unbounded.
+- Removed dynamic `require("node:fs")` inside `shouldInjectPlanReminder` — replaced with static ESM imports (no more runtime module resolution failures).
 
 #### Dead code elimination (F2)
 
-- `takeAnyDecision()` — deprecated; removed from the active governance pipeline.
-- `systemInjection` — now awaited eagerly instead of fire-and-forget, eliminating a silent failure route.
-- `logToFile` in `graph-sync.ts` — wired to the real JSONL file logger (was a no-op stub).
-- Plugin version — derived from `package.json` at runtime instead of hardcoded "0.13.0" (closes the version-drift bug where `omo_health` reported stale versions).
+- `takeAnyDecision()` — deprecated; removed from the active governance pipeline.
+- `systemInjection` — now awaited eagerly instead of fire-and-forget, eliminating a silent failure route.
+- `logToFile` in `graph-sync.ts` — wired to the real JSONL file logger (was a no-op stub).
+- Plugin version — derived from `package.json` at runtime instead of hardcoded "0.13.0" (closes the version-drift bug where `omo_health` reported stale versions).
 
 #### Tool bug fixes (F3)
 
 - **AFT checkpoint/undo**: args split on whitespace broke names with spaces. Rewrote arg construction with proper quoting.
 - **AFT subcommand**: now uses `options.projectDir` instead of `process.cwd()`.
 - **graphify binary override**: `omo_path` / `omo_explain` honored the `graphifyBin` option (was hardcoded).
-- **`as never` cast** on `setClient` → proper runtime guard that validates client shape.
+- **`as never` cast** on `setClient` → proper runtime guard that validates client shape.
 - **`session-bridge`**: replaced module-level `_client` with `AsyncLocalStorage` for per-request isolation. Concurrent sessions no longer race on the same client reference.
 
 #### Test coverage (F4)
@@ -215,18 +215,18 @@ v0.16.0 closes the 50+ findings from the multi-front audit at `.omo/ulw-research
 #### CI matrix (F6)
 
 - `bun run typecheck` now runs on **macos-latest** and **windows-latest** (was Ubuntu-only).
-- Removed `package-lock.json` (bun project — canonical is `bun.lock`).
+- Removed `package-lock.json` (bun project — canonical is `bun.lock`).
 - Secret redaction layer in `logToFile` (JWT, OpenAI keys, Bearer tokens, GitHub PATs, generic key:value patterns).
-- Implementation plan renamed `IMPLEMENTATION_PLAN.md` → `ARCHITECTURE.md`.
+- Implementation plan renamed `IMPLEMENTATION_PLAN.md` → `ARCHITECTURE.md`.
 
 #### Final refactors (F7)
 
 - Score formula documented (header doc with full formula spec).
-- **NaN guard** in `score()` — defaults to neutral continue when `iterationRatio` or `ambient.iteration/maxIterations` produce NaN.
+- **NaN guard** in `score()` — defaults to neutral continue when `iterationRatio` or `ambient.iteration/maxIterations` produce NaN.
 - `ACTION_SEVERITY` keyed by `DecisionHandlerOutput["action"]` union literal (was bare `Record<string, number>`).
 - `projectHasCodegraph` / `projectHasGraphify` IIFE booleans replaced with lookup-time calls to `graphRetrieval.hasCodegraphDir(cwd)`.
 - `extractConcepts` includes file basename for FTS lookup by tool/file name.
-- Backup graph-sync uses `triggerReindex` (was `triggerCodegraphSync`) — reindexes both codegraph AND graphify backends.
+- Backup graph-sync uses `triggerReindex` (was `triggerCodegraphSync`) — reindexes both codegraph AND graphify backends.
 
 ### Test & build status
 
@@ -241,47 +241,47 @@ No user action required. All changes are internal. The default `phaseAwareDoneSi
 
 ### Deferred to v0.17.0
 
-- F5.1 — wiring `escalate` action to a real dispatcher (Oracle is recommended but not yet wired).
-- F5.4 — `maxLessonsPerSession` enforcement (config field exists but is not enforced).
-- F3.6 — Bridge tools lying about delivery (5 tools still return "dispatched" without polling). Recommend the user explicitly request this if delivery verification is critical.
+- F5.1 — wiring `escalate` action to a real dispatcher (Oracle is recommended but not yet wired).
+- F5.4 — `maxLessonsPerSession` enforcement (config field exists but is not enforced).
+- F3.6 — Bridge tools lying about delivery (5 tools still return "dispatched" without polling). Recommend the user explicitly request this if delivery verification is critical.
 
 
 
 
-## v0.17.0 — Wire escalate to Oracle, enforce lesson cap, verify bridge delivery
+## v0.17.0 — Wire escalate to Oracle, enforce lesson cap, verify bridge delivery
 
-v0.17.0 closes the 3 deferred items from the v0.16.0 audit: **F5.1** (escalate → Oracle), **F5.4** (`maxLessonsPerSession` enforcement), and **F3.6** (bridge tool delivery verification).
+v0.17.0 closes the 3 deferred items from the v0.16.0 audit: **F5.1** (escalate → Oracle), **F5.4** (`maxLessonsPerSession` enforcement), and **F3.6** (bridge tool delivery verification).
 
 ### Highlights
 
-#### F5.1 — Escalate action now fires Oracle (v0.17.0)
+#### F5.1 — Escalate action now fires Oracle (v0.17.0)
 
 When the scoring engine produces an `escalate` action with target `oracle`, the plugin's `tool.execute.after` hook now fires a `session.prompt()` instructing the LLM to invoke `task(subagent_type=oracle)`. The prompt includes the decision reasoning, evidence count, and a verification pass directive. New `buildEscalationPrompt()` function in `session-bridge.ts` is the pure prompt builder (testable in isolation). User-targeted escalations get a separate prompt asking the LLM to summarize for human input.
 
 ```ts
 // Decision flow when score lands in escalate band:
-score ≤ -escalateThreshold (default -0.6)
-  → decision.action = "escalate"
-  → decision.shouldEscalateTo = "oracle" (or "user" for grave deviations)
-  → plugin fires session.prompt with buildEscalationPrompt(...)
-  → LLM invokes Oracle (or summarizes for user)
-  → Oracle verifies → oracleInvoked=true → governance continues
+score ≤ -escalateThreshold (default -0.6)
+  → decision.action = "escalate"
+  → decision.shouldEscalateTo = "oracle" (or "user" for grave deviations)
+  → plugin fires session.prompt with buildEscalationPrompt(...)
+  → LLM invokes Oracle (or summarizes for user)
+  → Oracle verifies → oracleInvoked=true → governance continues
 ```
 
-#### F5.4 — `maxLessonsPerSession` is now enforced
+#### F5.4 — `maxLessonsPerSession` is now enforced
 
 The cap (default 20) was a config field that was never enforced. v0.17.0 adds:
 - `currentLessonCount` on `LearnFromOutcomeInput` and `MetaGovernorInput`
 - `lessonCount` tracked in per-session `AuditState`
 - `observeAndLearn()` short-circuits when `currentLessonCount >= maxLessonsPerSession`
 - The orchestrator increments `sessionState.lessonCount` after each successful save
-- **Cap semantics: inclusive** — when count equals cap, no more lessons are saved
+- **Cap semantics: inclusive** — when count equals cap, no more lessons are saved
 
-#### F3.6 — Bridge tool delivery verification
+#### F3.6 — Bridge tool delivery verification
 
-The 5 bridge tools (`omo_remember`, `omo_recall_mcp`, `omo_rule`, `omo_history`, `omo_note`) previously returned "dispatched" after the `session.prompt()` was queued — without verifying the LLM actually called the MCP tool. v0.17.0 adds:
+The 5 bridge tools (`omo_remember`, `omo_recall_mcp`, `omo_rule`, `omo_history`, `omo_note`) previously returned "dispatched" after the `session.prompt()` was queued — without verifying the LLM actually called the MCP tool. v0.17.0 adds:
 
-- **New `PendingDeliveryRegistry` module** (`src/delivery-registry.ts`) — tracks pending dispatches per session with TTL-based cleanup.
+- **New `PendingDeliveryRegistry` module** (`src/delivery-registry.ts`) — tracks pending dispatches per session with TTL-based cleanup.
 - **`tool.execute.after` hook** marks deliveries when a matching MCP tool call is observed.
 - **All 5 bridge tools** now report `deliveryStatus: "delivered" | "pending"` in their tool result and metadata, and briefly poll (1.5s) for fast deliveries.
 - When the LLM follows the prompt, the tool returns immediately with `"delivered"`. When it doesn't, the tool returns `"pending"` and the entry expires silently after 10s.
@@ -300,7 +300,7 @@ The 5 bridge tools (`omo_remember`, `omo_recall_mcp`, `omo_rule`, `omo_history`,
 
 ### Test & build status
 
-- **514/514 tests pass** (up from 495 in v0.16.0 — 5 + 4 + 10 new tests across F5.4, F5.1, F3.6).
+- **514/514 tests pass** (up from 495 in v0.16.0 — 5 + 4 + 10 new tests across F5.4, F5.1, F3.6).
 - `bun run typecheck` clean.
 - `bun build.ts` clean (0.34 MB dist).
 - `npm pack --dry-run` validated.
@@ -308,23 +308,23 @@ The 5 bridge tools (`omo_remember`, `omo_recall_mcp`, `omo_rule`, `omo_history`,
 ### Migration
 
 No user action required. All changes are internal or additive:
-- `deliveryStatus` is an additive metadata field — existing consumers ignore it.
-- `maxLessonsPerSession` is now actually enforced — if you have sessions that previously saved more than 20 lessons (e.g. from before the cap was added), this may surprise you. Bump the cap in your config if needed.
-- `escalate` action now actively fires Oracle — this is the first version where Oracle is auto-invoked, not just manually invoked by the LLM.
+- `deliveryStatus` is an additive metadata field — existing consumers ignore it.
+- `maxLessonsPerSession` is now actually enforced — if you have sessions that previously saved more than 20 lessons (e.g. from before the cap was added), this may surprise you. Bump the cap in your config if needed.
+- `escalate` action now actively fires Oracle — this is the first version where Oracle is auto-invoked, not just manually invoked by the LLM.
 
 ### Audit roadmap (status as of v0.17.0)
 
 | Release | Status | Scope |
 |---------|--------|-------|
-| v0.15.1 (F0) | ✅ Shipped | Hotfix self-dep + npm pack gate |
-| v0.16.0 (F1-F7) | ✅ Shipped | Memory hygiene, dead code, tool coverage, CI |
-| v0.17.0 (deferred) | ✅ Shipped | F5.1 escalate, F5.4 cap, F3.6 delivery verify |
+| v0.15.1 (F0) | ✅ Shipped | Hotfix self-dep + npm pack gate |
+| v0.16.0 (F1-F7) | ✅ Shipped | Memory hygiene, dead code, tool coverage, CI |
+| v0.17.0 (deferred) | ✅ Shipped | F5.1 escalate, F5.4 cap, F3.6 delivery verify |
 
 All audit findings are now closed. Future work focuses on new features and user-driven feedback.
 
 
 
-## v0.17.1 — Audit args fix (patch)
+## v0.17.1 — Audit args fix (patch)
 
 v0.17.1 is a single-bug patch release. The fix addresses an issue discovered during v0.17.0 verification:
 
@@ -336,7 +336,7 @@ The `tool.execute.before` hook passed an empty `{}` object as the second argumen
 - `as any` type assertions  
 - `catch(e) {}` empty catch blocks
 
-The hook signature was also incomplete — it didn't receive the `output` parameter that contains the mutable args, even though the SDK provides it.
+The hook signature was also incomplete — it didn't receive the `output` parameter that contains the mutable args, even though the SDK provides it.
 
 ### The fix
 
@@ -358,14 +358,14 @@ Two changes in `src/plugin.ts`:
 ### Tests
 
 Added 4 new tests in `src/plugin.test.ts`:
-- `@ts-ignore + as any` in args → `no-type-suppression` violation detected and injected
-- `catch(e) {}` in args → `no-empty-catch` violation detected and injected
-- Clean code → no violation injected (false-positive guard)
-- `auditToolCalls: false` → audit short-circuits (regression check)
+- `@ts-ignore + as any` in args → `no-type-suppression` violation detected and injected
+- `catch(e) {}` in args → `no-empty-catch` violation detected and injected
+- Clean code → no violation injected (false-positive guard)
+- `auditToolCalls: false` → audit short-circuits (regression check)
 
 ### Test & build status
 
-- **518/518 tests pass** (up from 514 in v0.17.0 — 4 new audit tests).
+- **518/518 tests pass** (up from 514 in v0.17.0 — 4 new audit tests).
 - `bun run typecheck` clean.
 - `bun build.ts` clean (0.34 MB dist).
 
@@ -378,26 +378,26 @@ No user action required. The audit detection now correctly fires when the agent
 
 
 
-## v0.17.2 — Fix escalation dead code + 4 audit gaps
+## v0.17.2 — Fix escalation dead code + 4 audit gaps
 
-v0.17.2 closes 4 gaps discovered during live verification of v0.17.0/v0.17.1. The most important: F5.1 (escalate → Oracle) was effectively dead in production due to two compounding bugs.
+v0.17.2 closes 4 gaps discovered during live verification of v0.17.0/v0.17.1. The most important: F5.1 (escalate → Oracle) was effectively dead in production due to two compounding bugs.
 
 ### Highlights
 
-#### Gap C (CRITICAL) — Escalation now actually fires
+#### Gap C (CRITICAL) — Escalation now actually fires
 
-The score formula's `noProgress` and `deviations` inputs were hardcoded as `false` and `[]` in the plugin. This meant the `no-progress-detector` (weight 0.20) and `deviation-detector` (weight 0.20) signals always contributed 0. Combined with default thresholds, the maximum possible score was -0.55 — never reaching `escalateThreshold: 0.6` or `stopThreshold: 0.8`.
+The score formula's `noProgress` and `deviations` inputs were hardcoded as `false` and `[]` in the plugin. This meant the `no-progress-detector` (weight 0.20) and `deviation-detector` (weight 0.20) signals always contributed 0. Combined with default thresholds, the maximum possible score was -0.55 — never reaching `escalateThreshold: 0.6` or `stopThreshold: 0.8`.
 
 **Fix:**
 1. **Derive `noProgress`** from the recent tool call window. If the last 5 tool calls contain no `write`/`edit`/`task` (i.e. the agent is only reading/grepping without producing artifacts), `noProgress = true`.
 2. **Derive `deviations`** from accumulated protocol violations. The audit hook now stores violations in `state.accumulatedDeviations` (capped at 5 per session); the orchestrator input reads them.
 3. **Lower default thresholds** to match the new worst-case math:
-   - `escalateThreshold`: 0.6 → 0.45
-   - `stopThreshold`: 0.8 → 0.55
+   - `escalateThreshold`: 0.6 → 0.45
+   - `stopThreshold`: 0.8 → 0.55
 
-Now worst-case state (no oracle, no progress, 2 grave deviations, iteration at limit, stop-advice lessons) produces score ≈ -0.55 → `stop` action fires.
+Now worst-case state (no oracle, no progress, 2 grave deviations, iteration at limit, stop-advice lessons) produces score ≈ -0.55 → `stop` action fires.
 
-#### Gap Q (HIGH) — File paths threaded through pipeline
+#### Gap Q (HIGH) — File paths threaded through pipeline
 
 `orchestrator.ts` was hardcoding `filesChanged: []` instead of `input.filePaths`. This meant lesson extraction never saw the actual changed files, so F7.5's file-basename FTS indexing was empty.
 
@@ -406,17 +406,17 @@ Now worst-case state (no oracle, no progress, 2 grave deviations, iteration at l
 2. Capture `filePath` from `toolInput.args` on write/edit tool calls.
 3. New `MetaGovernorInput.filePaths?: readonly string[]` passed through to `observeAndLearn`.
 
-#### Gap D (HIGH) — Three config fields now actually do something
+#### Gap D (HIGH) — Three config fields now actually do something
 
 Three fields were in the schema and config projection but NEVER consulted by the logic:
 
-- `closedLoop.saveLessons` — parallel to `saveDecisions`. When `false`, lessons are skipped (decision records still save).
-- `intervention.includeDecisionHistory` — when `true`, `messages.transform` prepends recent intervention texts (capped at `maxHistoryMessages`) so the LLM sees its history of decisions.
-- `intervention.maxHistoryMessages` — limit for the above (default 5).
+- `closedLoop.saveLessons` — parallel to `saveDecisions`. When `false`, lessons are skipped (decision records still save).
+- `intervention.includeDecisionHistory` — when `true`, `messages.transform` prepends recent intervention texts (capped at `maxHistoryMessages`) so the LLM sees its history of decisions.
+- `intervention.maxHistoryMessages` — limit for the above (default 5).
 
 **Fix:** All three fields now control behavior. Track `recentInterventionTexts` in AuditState, format them into the injection text.
 
-#### Bonus — iteration-budget signal wired (Oracle finding)
+#### Bonus — iteration-budget signal wired (Oracle finding)
 
 Oracle flagged a pre-existing gap alongside Gap C: `iteration` was hardcoded `0` in the orchestrator input, making the `iteration-budget` signal (weight 0.15) effectively dead.
 
@@ -425,9 +425,9 @@ Fix:
 - Threaded `iteration: sessionState?.iteration ?? 0` into `MetaGovernorInput`.
 - `maxIterations` now reads from config instead of being hardcoded.
 
-Worst-case score math updated: with iteration at 100% (-0.12), all signals bad, no oracle → score = -0.65 → `stop` action fires.
+Worst-case score math updated: with iteration at 100% (-0.12), all signals bad, no oracle → score = -0.65 → `stop` action fires.
 
-#### Gap I (MEDIUM) — `verifyDelivery` return type includes "expired"
+#### Gap I (MEDIUM) — `verifyDelivery` return type includes "expired"
 
 The TypeScript signature was `Promise<"delivered" | "pending">` but the registry could return `"expired"`. The expired case leaked through as `"pending"` silently.
 
@@ -435,7 +435,7 @@ The TypeScript signature was `Promise<"delivered" | "pending">` but the registry
 
 ### Test & build status
 
-- **521/521 tests pass** (up from 518 — 3 new tests for the v0.17.2 fixes).
+- **521/521 tests pass** (up from 518 — 3 new tests for the v0.17.2 fixes).
 - `bun run typecheck` clean.
 - `bun build.ts` clean (0.34 MB dist).
 - `npm pack --dry-run` validated.
@@ -444,28 +444,28 @@ The TypeScript signature was `Promise<"delivered" | "pending">` but the registry
 
 No user action required. Two behavior changes:
 
-1. **Escalation now fires more aggressively.** If your agent has been producing violations and not making progress, expect to see escalate → Oracle prompts more often. This is the intended behavior; v0.17.0 was incorrectly silent.
+1. **Escalation now fires more aggressively.** If your agent has been producing violations and not making progress, expect to see escalate → Oracle prompts more often. This is the intended behavior; v0.17.0 was incorrectly silent.
 2. **`includeDecisionHistory` and `maxHistoryMessages` are now functional.** If you set them in v0.17.0 expecting them to work, they will now actually take effect.
 
 ### Audit roadmap (status as of v0.17.2)
 
 | Release | Status | Scope |
 |---------|--------|-------|
-| v0.15.1 (F0) | ✅ | Hotfix self-dep |
-| v0.16.0 (F1-F7) | ✅ | Memory hygiene, dead code, tool coverage, CI |
-| v0.17.0 | ✅ | F5.1 escalate, F5.4 cap, F3.6 delivery verify |
-| v0.17.1 | ✅ | Audit args fix |
-| v0.17.2 | ✅ | Gap C (escalation live), Q (file paths), D (config fields), I (delivery expired) |
+| v0.15.1 (F0) | ✅ | Hotfix self-dep |
+| v0.16.0 (F1-F7) | ✅ | Memory hygiene, dead code, tool coverage, CI |
+| v0.17.0 | ✅ | F5.1 escalate, F5.4 cap, F3.6 delivery verify |
+| v0.17.1 | ✅ | Audit args fix |
+| v0.17.2 | ✅ | Gap C (escalation live), Q (file paths), D (config fields), I (delivery expired) |
 
 
 
-## v0.17.3 — Fix Gap I properly (patch)
+## v0.17.3 — Fix Gap I properly (patch)
 
 v0.17.3 is a single-bug patch. During live verification of v0.17.2, Gap I was found to be incompletely fixed.
 
 ### The bug (v0.17.2 cosmetic fix)
 
-The `verifyDelivery` export signature was widened to include `"expired"` in v0.17.2, and the bridge tools' title/output text was updated to handle it. **BUT the underlying `pollForDelivery` helper was still collapsing `"expired"` → `"pending"` silently:**
+The `verifyDelivery` export signature was widened to include `"expired"` in v0.17.2, and the bridge tools' title/output text was updated to handle it. **BUT the underlying `pollForDelivery` helper was still collapsing `"expired"` → `"pending"` silently:**
 
 ```ts
 // v0.17.2 (BUG):
@@ -492,31 +492,31 @@ Added 3 RED tests in `src/custom-tools.test.ts`:
 
 ### Test & build status
 
-- **525/525 tests pass** (up from 522 in v0.17.2 — 3 new tests for pollForDelivery).
+- **525/525 tests pass** (up from 522 in v0.17.2 — 3 new tests for pollForDelivery).
 - `bun run typecheck` clean.
 - `bun build.ts` clean (0.34 MB dist).
 
 ### Migration
 
 No user action required. Bridge tools will now correctly distinguish all three delivery states:
-- `"delivered"` — LLM's MCP tool call was observed within 1.5s
-- `"expired"` — TTL elapsed without delivery (entry expires after 10s, but bridge tool sees this immediately as "expired" when polling times out at 1.5s)
-- `"pending"` — no registry configured (graceful degradation for tests/mocks)
+- `"delivered"` — LLM's MCP tool call was observed within 1.5s
+- `"expired"` — TTL elapsed without delivery (entry expires after 10s, but bridge tool sees this immediately as "expired" when polling times out at 1.5s)
+- `"pending"` — no registry configured (graceful degradation for tests/mocks)
 
 ### Audit roadmap (status as of v0.17.3)
 
 | Release | Status | Scope |
 |---------|--------|-------|
-| v0.15.1 → v0.17.2 | ✅ | All audit findings + 5 gap fixes |
-| v0.17.3 | ✅ | Gap I real fix (pollForDelivery returns "expired") |
+| v0.15.1 → v0.17.2 | ✅ | All audit findings + 5 gap fixes |
+| v0.17.3 | ✅ | Gap I real fix (pollForDelivery returns "expired") |
 
 Two remaining gaps documented but require SDK support to fix:
-- `recentTurnTokens: []` — token-predictor signal dead (10% of score); needs per-turn token counts from OpenCode SDK
-- `agentName` defaults to `"unknown"` — cosmetic, no functional impact
+- `recentTurnTokens: []` — token-predictor signal dead (10% of score); needs per-turn token counts from OpenCode SDK
+- `agentName` defaults to `"unknown"` — cosmetic, no functional impact
 
 
 
-## v0.18.0 — Audit remediation: 7+ silent config drops + circular ref crash
+## v0.18.0 — Audit remediation: 7+ silent config drops + circular ref crash
 
 v0.18.0 is a thorough-audit patch release. Each fix addresses a bug found by testing every public function with edge cases and adversarial inputs.
 
@@ -524,19 +524,19 @@ v0.18.0 is a thorough-audit patch release. Each fix addresses a bug found by tes
 
 | # | Bug | Severity | Fix |
 |---|-----|----------|-----|
-| 1 | `file-logger.redactData` crashed on circular references with stack overflow | 🔴 CRITICAL | `WeakSet` guard + `try/catch` fallback |
-| 2 | `loadOrchestratorConfig` only projected `closedLoop.saveDecisions` — `enabled`, `minSeverityToLearn`, `maxLessonsPerSession`, `saveLessons` were silently dropped | 🔴 CRITICAL | Project all 5 fields |
-| 3 | `loadOrchestratorConfig` didn't project `decision.warnMessageTemplate`, `escalateMessageTemplate`, `stopMessageTemplate` | 🟠 HIGH | Project all 3 templates |
-| 4 | `loadOrchestratorConfig` didn't project `scoring.paralysisThreshold`, `defaultEscalationTarget` | 🟠 HIGH | Project all fields |
-| 5 | `loadOrchestratorConfig` had `memory.timeoutMs` field name mismatch (schema said `agentmemoryTimeoutMs`) | 🟠 HIGH | Accept both names |
-| 6 | `isMetaGovernorEnabled` only checked top-level `enabled`, not `meta_governor.enabled` (wrapped shape from `opencode.jsonc`) | 🟠 HIGH | Check both shapes |
-| 7 | `createMetricsCollector` crashed when called without config (`config.version` on `undefined`) | 🟠 HIGH | Accept `Partial<MetricsCollectorConfig>` |
-| 8 | `metrics.inc` crashed on unknown event names (`bucket.count++` on `undefined`) | 🟠 HIGH | Guard `if (!bucket) return` |
-| 9 | `isNewerVersion` returned `false` for `installed=null` (no upgrade triggered for fresh installs) | 🟡 MEDIUM | Return `true` when installed is null AND latest is valid |
+| 1 | `file-logger.redactData` crashed on circular references with stack overflow | 🔴 CRITICAL | `WeakSet` guard + `try/catch` fallback |
+| 2 | `loadOrchestratorConfig` only projected `closedLoop.saveDecisions` — `enabled`, `minSeverityToLearn`, `maxLessonsPerSession`, `saveLessons` were silently dropped | 🔴 CRITICAL | Project all 5 fields |
+| 3 | `loadOrchestratorConfig` didn't project `decision.warnMessageTemplate`, `escalateMessageTemplate`, `stopMessageTemplate` | 🟠 HIGH | Project all 3 templates |
+| 4 | `loadOrchestratorConfig` didn't project `scoring.paralysisThreshold`, `defaultEscalationTarget` | 🟠 HIGH | Project all fields |
+| 5 | `loadOrchestratorConfig` had `memory.timeoutMs` field name mismatch (schema said `agentmemoryTimeoutMs`) | 🟠 HIGH | Accept both names |
+| 6 | `isMetaGovernorEnabled` only checked top-level `enabled`, not `meta_governor.enabled` (wrapped shape from `opencode.jsonc`) | 🟠 HIGH | Check both shapes |
+| 7 | `createMetricsCollector` crashed when called without config (`config.version` on `undefined`) | 🟠 HIGH | Accept `Partial<MetricsCollectorConfig>` |
+| 8 | `metrics.inc` crashed on unknown event names (`bucket.count++` on `undefined`) | 🟠 HIGH | Guard `if (!bucket) return` |
+| 9 | `isNewerVersion` returned `false` for `installed=null` (no upgrade triggered for fresh installs) | 🟡 MEDIUM | Return `true` when installed is null AND latest is valid |
 
 ### Test & build status
 
-- **557/557 tests pass** (up from 530 in v0.17.3 — 27 new tests for the audit fixes).
+- **557/557 tests pass** (up from 530 in v0.17.3 — 27 new tests for the audit fixes).
 - `bun run typecheck` clean.
 - `bun build.ts` clean (0.34 MB dist).
 - `npm pack --dry-run` validated.
@@ -549,11 +549,105 @@ No user action required. The fix to `loadOrchestratorConfig` means **users who w
 
 | Release | Status | Scope |
 |---------|--------|-------|
-| v0.15.1 → v0.17.3 | ✅ | All audit findings + deferred items + audit args fix + gap fixes |
-| v0.18.0 | ✅ | 7 silent config drops + circular ref crash + metrics crashes + upgrade trigger |
+| v0.15.1 → v0.17.3 | ✅ | All audit findings + deferred items + audit args fix + gap fixes |
+| v0.18.0 | ✅ | 7 silent config drops + circular ref crash + metrics crashes + upgrade trigger |
 
 This release closes the final round of gaps found by a thorough function-by-function audit. The plugin now correctly projects **all** user configuration, handles **all** circular reference cases, and fails safely on **all** missing-input scenarios.
 
+
+## v0.19.4 — Dual-shape default export: opencode 1.18.x loader compat (patch)
+
+v0.19.3 shipped a function-only default export hoping to fix the opencode
+serve factory-not-invoked bug. Empirical verification (reading
+`~/.config/opencode/meta-governor.log`) showed it didn''t help: opencode
+1.18.16 npm-package plugins still loaded the module without ever calling
+the factory under `opencode serve`.
+
+### The fix
+
+`src/index.ts` now exports an object that is **both** a Plugin function
+**and** a PluginModule:
+
+```ts
+const _plugin = createMetaGovernorPlugin()
+_plugin.id = "omo-meta-governor"
+_plugin.server = _plugin
+export default _plugin
+```
+
+Bundled as `var u4=IN(); u4.id="omo-meta-governor"; u4.server=u4; export{...JX=u4...}`.
+Whichever path opencode picks (`default(input, options)` or
+`default.server(input, options)`), the same callable fires and the hooks
+register.
+
+### Verification
+
+After restart of OpenChamber, log shows:
+- factory_invoked events (was 0 with v0.19.3)
+- config_loaded events (was 0 with v0.19.3)
+- intervention / violations / persist calls firing normally
+
+### Test & build status
+
+- 4/4 new tests in `src/index.test.ts` lock down the dual-shape contract.
+- `bun run typecheck` clean.
+- `bun build.ts` clean (0.35 MB dist).
+- `npm publish` to registry OK.
+
+### Migration
+
+No user action required. If you previously set
+`intervention.persistToSession: false` in your config, that toggle is
+still respected.
+
+---
+
+## v0.19.3 — opencode serve factory invocation + persistSessionMessage wiring
+
+This release closes the persistSessionMessage wiring arc (memory #999) and
+loads config from three sources automatically (CLI > project > user).
+The `index.ts` `export default` change was incomplete (see v0.19.4 for
+the proper dual-shape fix that resolves opencode serve invocation).
+
+### Highlights
+
+- **index.ts**: switched `export default` to call `createMetaGovernorPlugin()`
+  directly (function path), abandoning the `PluginModule` wrapper. Was the
+  wrong shape — see v0.19.4 for the actual fix.
+- **plugin.ts**: factory now calls `loadMetaGovernorConfig({ projectDir })` so
+  config from `.opencode/omo-meta-governor.jsonc` and
+  `~/.config/opencode/omo-meta-governor.jsonc` flows in automatically.
+- **session-bridge.ts**: `persistSessionMessage()` — fire-and-forget
+  `session.prompt()` helper that records intervention text as a REAL session
+  message (visible in TUI and session DB).
+- **types.ts + config.ts + orchestrator.ts**: `persistToSession` defaults to
+  true on `InterventionConfig`. Helps users running OpenChamber actually
+  SEE interventions in their TUI.
+- **tests**: 16 `createMetaGovernorPlugin()` calls in plugin/v172/v173-gap-d
+  tests now pass `graphSync: { enabled: false, autoInstall: false }`
+  because user config enables `autoInstall` by default (memory #989).
+
+### Test & build status
+
+- ~437/437 tests pass (per-file, `graphsink-fix.ts` skipped per known Bun
+  Windows integer-overflow crash).
+- `bun run typecheck` clean.
+- `bun build.ts` clean (0.35 MB dist).
+- `npm publish` to registry OK.
+
+### Migration
+
+No user action required.
+
+---
+
+## v0.19.0–v0.19.2 — Internal persistSessionMessage wiring arc (memory #999)
+
+Three iterations on the persistSessionMessage wiring arc. Each iteration
+added call sites and tightened the test coverage, but the fix was lost in
+stashes and merges until v0.19.3 finally shipped a working version of
+the helper. See v0.19.3 for the user-facing release notes; v0.19.4
+supersedes with the correct dual-shape export.
 ## Auto-upgrade (v0.12.0)
 
 On plugin load, queries npm/pip registries to check whether newer versions

package/dist/index.d.ts

@@ -1,24 +1,27 @@
 /**
- * @sisyphuslabs/omo-meta-governor — Self-judging agent orchestration layer.
+ * Dual-shape export for opencode plugin loader compatibility.
  *
- * Default export is an OpenCode PluginModule that registers a
- * `tool.execute.after` hook. The MetaGovernor reads session signals,
- * scores them against weighted evidence, and dispatches decisions.
+ * The default export is simultaneously:
+ * - a Plugin function: `default(input, options) => Promise<Hooks>`
+ * - a PluginModule: `default.id`, `default.server(input, options)`
  *
- * Install:
- *   npm install @sisyphuslabs/omo-meta-governor
- *
- * Configure:
- * ```jsonc
- * {
- *   "meta_governor": {
- *     "enabled": true
- *   }
- * }
- * ```
+ * `.server` points to the same callable as the default, so whichever
+ * shape the opencode loader resolves, the factory fires exactly once.
+ */
+export declare const _pluginDual: Plugin & {
+    id: string;
+    server: Plugin;
+};
+export default _pluginDual;
+/**
+ * Named alias of the dual-shape export. Some opencode plugin loaders
+ * resolve plugins by named export rather than default — exposing both
+ * covers that third hypothetical path with zero cost.
  */
-declare const _default: import("@opencode-ai/plugin").Plugin;
-export default _default;
+export declare const plugin: Plugin & {
+    id: string;
+    server: Plugin;
+};
 export { createMetaGovernorPlugin, type MetaGovernorPluginDeps } from "./plugin";
 export { logToFile } from "./file-logger";
 export { runMetaGovernor, buildDecisionContext, defaultOrchestratorConfig, } from "./orchestrator";