@herjarsa/omo-meta-governor 0.19.7 → 0.21.0

package/README.md

@@ -158,6 +158,33 @@ Enabled when `meta_governor.enabled: true` in config.
 | `respectDoneSignal` | `true` | Stop injecting after terminal signal + Oracle verified |
 | `phaseAwareDoneSignal` | `false` | **v0.15.0**: when `true`, only `<promise>PLAN-COMPLETE</promise>` latches intervention. DONE/PHASE-N-COMPLETE are per-phase hints. Recommended for multi-phase plans. |
 
+## Skill Priming (v0.20.0)
+
+Proactive skill-selection nudge: the plugin injects **one** synthetic user message at session
+start (or once implementation work begins) prompting the agent to select precise skills for the
+task via the **AAS skill catalog** (`aas search_skills` / `get_skill` / `compose_stack`) and/or
+the task-appropriate **superpowers** skill — before writing code. Minimal context cost: the
+directive forbids enumerating the full catalog.
+
+```jsonc
+{
+  "meta_governor": {
+    "enabled": true,
+    "skillPriming": {
+      "enabled": true,
+      "trigger": "sessionStart", // or "firstImplement" (default)
+      "router": "both" // "aas", "superpowers", or "both"
+    }
+  }
+}
+```
+
+| Field | Default | Description |
+|-------|---------|-------------|
+| `enabled` | `false` | Master switch for the skill-priming nudge |
+| `trigger` | `"firstImplement"` | `"sessionStart"`: first transform call of the session. `"firstImplement"`: once a write/edit-like tool is observed |
+| `router` | `"both"` | Which system(s) the directive references: `"aas"`, `"superpowers"`, `"both"` |
+
 ### Multi-phase plans (v0.15.0)
 
 For work plans with multiple phases (e.g. Sisyphus/Prometheus work plans),
@@ -554,100 +581,169 @@ No user action required. The fix to `loadOrchestratorConfig` means **users who w
 
 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.
+
+## 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.7 — Fix npm-published package.json: restore `import` condition in `exports` (patch)
+
+v0.19.6 shipped a single callable default export with the dual-shape contract (memory #1126) but the published tarball's `package.json` had the `exports` map regenerated to contain only the `types` condition — no `import`/`default`/`require` runtime condition. Under opencode 1.18.16's plugin loader, that caused the npm-package plugin to load the module (module scope ran, `MetaGovernor plugin loaded` logged) but **never invoke the factory** (`factory_invoked` was 0). v0.19.4 had empirically verified the dual-shape fix for `opencode serve`; v0.19.6 on `opencode run` with the same dual-shape bundle in the npm cache was silently broken for the same reason.
+
+### The bug
+
+`package.json` in the v0.19.6 tarball (read from the installed package in `~/.cache/opencode/packages/@herjarsa/omo-meta-governor@latest/...`):
+
+```json
+"exports": {
+    ".": { "types": "./dist/index.d.ts" },
+    "./lib": { "types": "./dist/lib.d.ts" }
+}
+```
+
+vs. the repo's source `package.json` (correct, with `import` condition for runtime resolution):
+
+```json
+"exports": {
+    ".": { "types": "./dist/index.d.ts", "import": "./dist/index.js" },
+    "./lib": { "types": "./dist/lib.d.ts", "import": "./dist/lib.js" }
+}
+```
+
+The published manifest lost the `import` condition (and `peerDependencies: {"@opencode-ai/plugin": ">=1.0.0"}`, `publishConfig`, `repository.url`, `devDependencies.typescript`, `files` README entry, `scripts.test`). When opencode's plugin installer resolves the entry via `exports`, only `"types"` is offered — no runtime condition matches → the loader imports the bundle by `main` fallback but the export contract that uk() (`opencode.util.createPlugin`) inspects isn't satisfied, so the plugin is loaded but never invoked.
+
+### How the bug was reproduced
+
+Cheap-shape probes (`@herjarsa/omg-shape-probe2` … `probe7`) with byte-identical Bun-bundles from `dist/index.js` were published to npm and tested under `opencode run` with XDG-isolated config. All probes with `exports."."` containing `"import"` or `"default"` invoked the factory. The probe replicating the exact published shape (types-only exports) failed to invoke. Bundle SHA-256 identical between probes and the real published package:
+```
+E737C676FCC74B6CBA771616058BC5620C1F0364089B1B8626246E96FF02ED69
+```
+
+### The fix
+
+No source/bundle changes — the bundle was correct all along. The malformed published `package.json` was restored from the repo (`git show HEAD:package.json` has the canonical full exports map with `import`) and only the version was bumped to `0.19.7`. Rebuild with `bun build.ts` (bakes version into the bundle), published, verified.
+
+### Verification
+
+XDG-isolated opencode run (`opencode run` with custom config pointing at `@herjarsa/omo-meta-governor@latest`):
+
+- v0.19.6 (cache populated): log shows `MetaGovernor plugin loaded` only — **no `factory_invoked`**, intervention never runs.
+- v0.19.7 (cache cleared, reinstalled): log shows full chain:
+  ```
+  [meta-governor] MetaGovernor plugin loaded
+  [meta-governor] factory_invoked
+  [meta-governor] SessionBridge: OpenCode client hydrated — session.prompt() available
+  [meta-governor] config_loaded
+  ```
+
+Updated `~/.cache/opencode/packages/@herjarsa/omo-meta-governor@latest/node_modules/@herjarsa/omo-meta-governor/package.json` now reads `exports."."` = `{ types: "./dist/index.d.ts", import: "./dist/index.js" }` and `peerDependencies` = `{ "@opencode-ai/plugin": ">=1.0.0" }`.
+
+### Test & build status
+
+- `bun run typecheck` clean.
+- `bun build.ts` clean (0.34 MB dist, version 0.19.7 baked in).
+- `npm publish` to registry OK.
+- Empirical harness verification: factory_invoked + config_logged restored.
+
+### Migration
+
+No user action required. If you were running v0.19.6 and the plugin appeared silent (no interventions, no metrics), delete your opencode cache:
+```bash
+rm -rf ~/.cache/opencode/packages/@herjarsa/omo-meta-governor@latest
+```
+Then restart opencode — it will reinstall v0.19.7 from the registry and the pipeline will fire normally.
+
+---
+
+## 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/config.d.ts

@@ -1,4 +1,4 @@
-import type { ModelOverrideConfig, OrchestratorConfig } from "./types";
+import type { ModelOverrideConfig, OrchestratorConfig, PostWaveConfig, SkillPrimingRouter, SkillPrimingTrigger } from "./types";
 import type { ConfigFileSources } from "./config-file";
 /**
  * MetaGovernor config schema exposed to users.
@@ -85,6 +85,14 @@ export interface MetaGovernorPluginConfig {
         autoInstall?: boolean;
         installTimeoutMs?: number;
     };
+    /** Skill priming config (v0.20.0): proactive skill-selection nudge. */
+    skillPriming?: {
+        enabled?: boolean;
+        trigger?: SkillPrimingTrigger;
+        router?: SkillPrimingRouter;
+    };
+    /** Post-wave workflow gate (v0.21.0): landing directives after Oracle-approved waves. */
+    postWave?: PostWaveConfig;
 }
 /**
  * Project the full MetaGovernorPluginConfig into OrchestratorConfig.

package/dist/graph-sync.d.ts

@@ -14,6 +14,7 @@
  *   - Never throws — all errors are silently caught and logged
  *   - Tracks session init once per project via an in-memory Set
  */
+import { execSync } from "node:child_process";
 export interface GraphSyncConfig {
     /** Enable auto-initialization. Default: true */
     enabled: boolean;
@@ -35,6 +36,10 @@ export interface GraphSyncConfig {
     autoUpgrade?: boolean;
     /** v0.12.0: Min ms between registry queries for version check. Default 24h. */
     upgradeCheckTtlMs?: number;
+    /** v0.21.0: test-only DI seam — replaces execSync so availability probes
+     * never spawn real npx/pip/graphify in hermetic tests (CI Windows: the
+     * npx download + 4 fallbacks exceeded the 30s test timeout). */
+    runner?: typeof execSync;
 }
 export type InstallCode = "codegraph-installed" | "codegraph-install-failed" | "codegraph-install-skipped" | "graphify-installed" | "graphify-install-failed" | "graphify-install-skipped";
 /**
@@ -73,6 +78,36 @@ export interface ToolAvailability {
     /** Whether graphify-out/ directory already exists in the project */
     graphifyIndexExists: boolean;
 }
+/**
+ * Check which graph tools are available and whether indexes already exist.
+ */
+/**
+ * Check which graph tools are available and whether indexes already exist.
+ *
+ * Index existence requires the marker file, not just the directory:
+ * - codegraph: `.codegraph/codegraph.db`
+ * - graphify: `graphify-out/graph.json`
+ * An empty dir created by a failed init must NOT count as initialized.
+ */
+export declare function checkToolAvailability(projectDir: string, runner?: typeof execSync): Promise<ToolAvailability>;
+/**
+ * Initialize codegraph in the project. Returns true only when the init
+ * command exited successfully (no throw). Does NOT pre-create the dir —
+ * a failed init must not leave an empty dir that later counts as
+ * "already exists".
+ */
+export declare function initCodegraph(projectDir: string, timeoutMs?: number, runner?: typeof execSync): Promise<boolean>;
+/**
+ * Initialize graphify in the project. Returns true only when one of the
+ * candidate commands exited successfully.
+ *
+ * v0.21.0 candidate order: `graphify` binary first (the real CLI installed
+ * by the pip package `graphifyy` on Windows), then `python -m graphify`
+ * (real interpreter — `python3` may be a WindowsApps stub), then
+ * `python3 -m graphify`. The `graphifyy` binary is NOT attempted — it does
+ * not exist; the package's binary is named `graphify`.
+ */
+export declare function initGraphify(projectDir: string, timeoutMs?: number, runner?: typeof execSync): Promise<boolean>;
 /**
  * Stop all active watch processes for a project.
  */
@@ -89,7 +124,7 @@ export interface GraphSyncResult {
     /** Whether this project was already initialized this session */
     alreadyInitialized: boolean;
 }
-export type GraphSyncCode = "codegraph-initialized" | "codegraph-already-exists" | "codegraph-unavailable" | "codegraph-install-failed" | "codegraph-install-skipped" | "graphify-initialized" | "graphify-already-exists" | "graphify-unavailable" | "graphify-install-failed" | "graphify-install-skipped" | "watch-started-codegraph" | "watch-started-graphify" | "disabled" | "error" | "graphify-hook-installed" | "codegraph-upgraded" | "graphify-upgraded" | "upgrade-check-skipped";
+export type GraphSyncCode = "codegraph-initialized" | "codegraph-init-failed" | "codegraph-already-exists" | "codegraph-unavailable" | "codegraph-install-failed" | "codegraph-install-skipped" | "graphify-initialized" | "graphify-init-failed" | "graphify-already-exists" | "graphify-unavailable" | "graphify-install-failed" | "graphify-install-skipped" | "watch-started-codegraph" | "watch-started-graphify" | "disabled" | "error" | "graphify-hook-installed" | "codegraph-upgraded" | "graphify-upgraded" | "upgrade-check-skipped";
 /**
 * Run the graphSync pipeline. Best-effort, never throws.
 */
@@ -110,7 +145,7 @@ export declare function isGitCommitCommand(command: string | undefined | null):
  *
  * Best-effort: never throws, returns a structured result instead.
  */
-export declare function triggerReindex(projectDir: string): Promise<GraphSyncResult>;
+export declare function triggerReindex(projectDir: string, runner?: typeof execSync): Promise<GraphSyncResult>;
 /**
  * v0.11.0: Check whether the project's `.git/hooks/post-commit` is the
  * graphify-managed one. Reads the file and looks for the `graphify-hook-start`
@@ -128,7 +163,7 @@ export declare function isGraphifyHookInstalled(projectDir: string): Promise<boo
  *
  * Best-effort: never throws, returns a structured result.
  */
-export declare function triggerCodegraphSync(projectDir: string): Promise<GraphSyncResult>;
+export declare function triggerCodegraphSync(projectDir: string, runner?: typeof execSync): Promise<GraphSyncResult>;
 import type { LogLevel } from "./file-logger";
 export declare function logToFile(level: LogLevel, msg: string): Promise<void>;
 /**