@herjarsa/omo-meta-governor 0.38.2 → 0.38.4

package/dist/config.d.ts

@@ -44,6 +44,12 @@ export interface MetaGovernorPluginConfig {
         paralysisThreshold?: number;
         /** v0.18.0: was silently dropped by loadOrchestratorConfig */
         defaultEscalationTarget?: "oracle" | "user";
+        /**
+         * v0.38.4 Option D: Oracle invocation frequency. Derived from
+         * `oracle.frequency` (canonical) — exposed here only as a fallback.
+         * Users should set `oracle.frequency` in opencode.jsonc, not this field.
+         */
+        oracleFrequency?: "per-stop" | "final-only" | "off";
     };
     /** Closed-loop learning (PR 3) */
     closedLoop?: {
@@ -55,6 +61,27 @@ export interface MetaGovernorPluginConfig {
     };
     /** Model override for MetaGovernor internal LLM usage. */
     modelOverride?: ModelOverrideConfig;
+    /**
+     * v0.38.4: Oracle invocation frequency. Controls when the plugin invokes
+     * Oracle for verification — reduces noisy mid-work escalations.
+     *
+     * - `"per-stop"` (default, Option D): Oracle is invoked ONLY at the
+     *   final-gate (`<promise>DONE</promise>`) AND when score crosses the
+     *   stop threshold (`≤ -stopThreshold`). warn/escalate decisions log
+     *   but do NOT inject an Oracle prompt mid-work. Best balance: silent
+     *   on normal work, brake on emergencies, mandatory at done.
+     *
+     * - `"final-only"` (Option A): Oracle is invoked ONLY at the final-gate.
+     *   Even stop-level decisions log without injecting an Oracle prompt.
+     *   Use when you want zero mid-work interruptions.
+     *
+     * - `"off"`: Oracle is never invoked. The post-wave gate still requires
+     *   `oracleVerified` — set it manually via `omo_recall` if you need it.
+     */
+    oracle?: {
+        /** @default "per-stop" */
+        frequency?: "per-stop" | "final-only" | "off";
+    };
     /** Intervention config for visible decision injection. */
     intervention?: {
         /** @default "silent" */

package/dist/enforcement-resources.d.ts

@@ -21,8 +21,26 @@
 export declare const ENFORCEMENT_RESOURCE_URIS: readonly ["meta-governor://rules/oracle", "meta-governor://rules/agentmemory", "meta-governor://rules/skill-priming", "meta-governor://rules/protocol"];
 export type EnforcementResourceUri = (typeof ENFORCEMENT_RESOURCE_URIS)[number];
 /**
- * Build the Oracle gate rule (v0.29.0 post-task Oracle verification).
- * Same text as `protocol-enforcer.ts:71-78` but standalone and exposed via MCP resource.
+ * Build the Oracle gate rule (v0.38.4 Option D — Oracle frequency).
+ *
+ * v0.38.4 REWRITE: Oracle is no longer auto-invoked mid-work for every
+ * multi-file change. Instead, the `oracle.frequency` config controls when
+ * Oracle fires:
+ *   - `"per-stop"` (default): Oracle invoked at the final-gate
+ *     (<promise>DONE</promise>) AND when the scoring engine reaches the
+ *     stop band (action === "stop"). warn/escalate log but do NOT
+ *     invoke Oracle mid-work.
+ *   - `"final-only"`: Oracle invoked ONLY at the final-gate. Even
+ *     stop-level decisions log without invoking Oracle mid-work.
+ *   - `"off"`: Oracle is NEVER invoked automatically. The agent must
+ *     set `oracleVerified` manually (e.g. via omo_recall).
+ *
+ * The DONE final-gate is ALWAYS Oracle-verified regardless of frequency.
+ *
+ * Same MCP resource contract as before — `meta-governor://rules/oracle`
+ * still returns this text. The previous "INVOKE triggers per multi-file
+ * change" was the source of the noise — now mid-work Oracle is
+ * gated by score band, not file count.
  */
 export declare function buildOracleRule(): string;
 /**