@genee/omp-opsx-addon 0.9.0 → 0.11.0

package/lib/concurrency-writer.ts

@@ -38,6 +38,7 @@ import { closeSync, mkdirSync, openSync, readFileSync, renameSync, rmSync, statS
 import { dirname } from 'path';
 import { YAML } from 'bun';
 import { clampLimit } from './concurrency-tuner.js';
+import { overrideProviderMaxInFlight } from './host-settings-adapter.js';
 import { canonicalizeProvider } from './usage-resolver.js';
 
 /** Sink for degradation notices; defaults to a no-op. */
@@ -218,8 +219,8 @@ export function readManagedLimits(
 /**
  * Merge one provider's new limit into the **complete** per-provider map.
  * `providers.maxInFlightRequests` is a whole-key override on the host side, so
- * every caller MUST pass the full map (this is the map that goes to
- * `settings.override` and to {@link writeManagedLimit}).
+ * every caller MUST pass the full map (this is the map that goes to the
+ * hot-apply override — {@link applyLimit} — and to {@link writeManagedLimit}).
  */
 export function buildMergedMap(
     current: Record<string, number>,
@@ -582,10 +583,15 @@ export function writeManagedLimit(args: WriteManagedLimitArgs): WriteManagedLimi
 }
 
 /**
- * Injected host settings port (`pi.pi.settings`), narrowed to the call we make.
+ * Injected host settings port (`pi.pi.settings`).
+ *
+ * Only the identity of the host singleton matters here: the hot-apply goes
+ * through `lib/host-settings-adapter.ts`, which resolves the API generation
+ * (registry handle on omp >= 18.3, path-based `override` before that). Hence
+ * `override` is optional — a host that dropped it is still a usable port.
  */
 export interface SettingsPort {
-    override(path: string, value: unknown): void;
+    override?(path: string, value: unknown): void;
 }
 
 export interface ApplyLimitArgs {
@@ -604,8 +610,10 @@ export interface ApplyLimitResult {
 }
 
 /**
- * Hot-apply the shared map in this process via
- * `settings.override('providers.maxInFlightRequests', merged)`.
+ * Hot-apply the shared map in this process through the host settings runtime
+ * override (`providers.maxInFlightRequests`: registry handle on omp >= 18.3,
+ * path-based `settings.override` before that — both via
+ * `lib/host-settings-adapter.ts`).
  *
  * `providers.maxInFlightRequests` is a **whole-key override**, so the second
  * argument MUST be the complete per-provider map — passing only the target
@@ -614,13 +622,14 @@ export interface ApplyLimitResult {
  * (the caller keeps the previous value), while a partial map would silently
  * make the omitted providers unlimited. When the API throws (host schema moved
  * on), the persisted config is untouched — the host config watcher picks the
- * value up — and the failure is warned, never fatal.
+ * value up — and the failure is warned, never fatal. Async because the adapter
+ * loads host handles by dynamic import.
  */
-export function applyLimit(args: ApplyLimitArgs): ApplyLimitResult {
+export async function applyLimit(args: ApplyLimitArgs): Promise<ApplyLimitResult> {
     const warn = args.warn ?? NO_WARN;
     const settings = args.settings;
-    if (!settings || typeof settings.override !== 'function') {
-        warn('[omp-opsx-addon] concurrency: settings.override unavailable; skipping hot apply (config file value still applies)');
+    if (!settings) {
+        warn('[omp-opsx-addon] concurrency: settings unavailable; skipping hot apply (config file value still applies)');
         return { applied: false, reason: 'settings-unavailable' };
     }
     const provider = canonicalizeProvider(args.provider.trim());
@@ -631,15 +640,18 @@ export function applyLimit(args: ApplyLimitArgs): ApplyLimitResult {
     const payload = buildMergedMap(args.merged ?? {}, provider, args.value);
     for (const [id, value] of Object.entries(payload)) {
         if (!id || typeof value !== 'number' || !Number.isSafeInteger(value) || value < 1) {
-            warn(`[omp-opsx-addon] concurrency: refusing settings.override — invalid map entry ${JSON.stringify(id)}: ${JSON.stringify(value)}`);
+            warn(`[omp-opsx-addon] concurrency: refusing the hot-apply override — invalid map entry ${JSON.stringify(id)}: ${JSON.stringify(value)}`);
             return { applied: false, reason: 'invalid-merged' };
         }
     }
     try {
-        settings.override('providers.maxInFlightRequests', payload);
+        if (!(await overrideProviderMaxInFlight(settings, payload))) {
+            warn('[omp-opsx-addon] concurrency: no settings runtime-override API available (host handle / settings.override); skipping hot apply (config file value still applies)');
+            return { applied: false, reason: 'settings-unavailable' };
+        }
         return { applied: true };
     } catch (err) {
-        warn(`[omp-opsx-addon] concurrency: settings.override failed (${message(err)}); the host config watcher will apply the persisted value`);
+        warn(`[omp-opsx-addon] concurrency: settings hot-apply failed (${message(err)}); the host config watcher will apply the persisted value`);
         return { applied: false, reason: 'override-failed' };
     }
 }

package/lib/edit-variant-pin.ts

@@ -2,9 +2,11 @@ import * as fs from 'node:fs';
 import * as os from 'node:os';
 import * as path from 'node:path';
 import type { ExtensionAPI } from '@oh-my-pi/pi-coding-agent';
+import { overrideEditModelVariants } from './host-settings-adapter.js';
 
 /**
- * Runtime edit-variant pin fallback for omp >= 18.0.11.
+ * Runtime edit-variant pin, with a persisted fallback for hosts that no longer
+ * expose `edit.modelVariants` to the runtime settings API.
  *
  * The host hard-maps deepseek-v4-flash to the sloppy §/» marker grammar (it
  * misreads hashline ranges), but the model repeatedly breaks sloppy control
@@ -12,11 +14,14 @@ import type { ExtensionAPI } from '@oh-my-pi/pi-coding-agent';
  * plain old_string/new_string "replace" variant instead.
  *
  * Up to 17.x this extension did that via
- * `settings.override("edit.modelVariants", …)`. omp 18.0.11 dropped
- * `edit.modelVariants` from the settings schema, so `override()` throws
- * inside `get()`: the path-segment table has no entry for it and `getByPath`
- * iterates `undefined`. The host still honors the key when it arrives through
- * the global config file — `#getEditVariantEntries` reads the merged view
+ * `settings.override("edit.modelVariants", …)`; omp 18.3 replaced that
+ * path-based API with registry handles (`edit.modelVariants` handle →
+ * `handle.override(settings, …)`, see `lib/host-settings-adapter.ts`), so the
+ * runtime path lives on. On 18.0.11–18.x hosts whose path-based schema
+ * dropped `edit.modelVariants`, `override()` throws inside `get()`: the
+ * path-segment table has no entry for it and `getByPath` iterates
+ * `undefined`. Those hosts still honor the key when it arrives through the
+ * global config file — `#getEditVariantEntries` reads the merged view
  * directly and `resolveEditMode` prefers the per-model variant over
  * `edit.mode` — so persisting once is functionally equivalent to the runtime
  * pin.
@@ -102,38 +107,41 @@ export function persistEditVariantPin(
 }
 
 /**
- * Pin the edit variant for the target models.
+ * Pin the edit variant for the target models. Never rejects: every failure is
+ * warned through the host logger (the caller fires this and forgets it).
  *
- * Preferred path: in-memory `settings.override` (omp < 18.0.11). When that
- * throws (18.0.11 removed the schema path), persist into the global
- * config.yml once — idempotent, effective from the next session.
+ * Preferred path: the in-memory runtime override — the `edit.modelVariants`
+ * registry handle on omp >= 18.3, the path-based `settings.override` before
+ * that (both resolved inside `lib/host-settings-adapter.ts`). When this host
+ * offers no runtime path that reaches the setting (18.0.11+ dropped it from
+ * the path-based schema), persist into the global config.yml once —
+ * idempotent, effective from the next session.
  */
-export function applyEditVariantPin(pi: ExtensionAPI, pin: Record<string, string>): void {
+export async function applyEditVariantPin(pi: ExtensionAPI, pin: Record<string, string>): Promise<void> {
     // `pi.pi` is the whole SDK module namespace; its `settings` field has no
-    // declared runtime instance type on the extension-facing surface, so
-    // narrow to the two methods we call (the same shape the host's Settings
-    // class exposes publicly).
-    const settings = pi.pi?.settings as unknown as
-        | { override(path: string, value: unknown): void; getAgentDir?: () => string }
-        | undefined;
-    if (!settings) {
+    // declared runtime instance type on the extension-facing surface, so the
+    // `in`/`typeof` checks below are the whole contract.
+    const settings: unknown = pi.pi?.settings;
+    if (!settings || typeof settings !== 'object') {
         pi.logger?.warn('[omp-opsx-addon] pi.pi.settings unavailable; edit variant pin skipped');
         return;
     }
 
     try {
-        settings.override('edit.modelVariants', pin);
-        return;
+        if (await overrideEditModelVariants(settings, pin)) return;
     } catch {
-        /* settings schema no longer knows this path — persist instead */
+        /* host schema no longer knows the path — persist instead */
     }
 
     try {
-        let agentDir: string;
-        try {
-            agentDir = settings.getAgentDir?.() ?? '';
-        } catch {
-            agentDir = '';
+        let agentDir = '';
+        if ('getAgentDir' in settings && typeof settings.getAgentDir === 'function') {
+            try {
+                const dir = settings.getAgentDir();
+                if (typeof dir === 'string') agentDir = dir;
+            } catch {
+                agentDir = '';
+            }
         }
         if (!agentDir) agentDir = path.join(os.homedir(), '.omp', 'agent');
 

package/lib/host-settings-adapter.ts

@@ -0,0 +1,227 @@
+/**
+ * Host Settings API compatibility adapter (change: omp-18.3-settings-api-compat).
+ *
+ * omp 18.3.2 removed the path-based Settings API (`settings.override(path, value)`
+ * / `settings.clearOverride(path)`) in favour of registry handles: a handle
+ * carries the setting's identity — `handle.override(settings, value)` writes the
+ * runtime overlay and clearing goes through
+ * `settings.clearOverrideValue(handle)` (equivalent to
+ * `handle.clearOverride(settings)`). Every path-based call this plugin made
+ * (`clearOverride('modelRoles')`, `override('task.agentModelOverrides', …)`,
+ * `override('providers.maxInFlightRequests', …)`,
+ * `override('edit.modelVariants', …)`) now throws
+ * (`settings.clearOverride is not a function`), which took down the whole
+ * `/pick-model` apply path and silently disabled the concurrency hot-apply.
+ *
+ * Handles live on deep host subpaths and are loaded LAZILY via dynamic
+ * `import()` — never a static import:
+ *  - this package's own dev dependency is older (18.1.2) and ships no such
+ *    subpaths, so a static import would break typecheck/build;
+ *  - the host's legacy-pi-compat redirect rewrites these specifiers to the
+ *    host's own module instances, which is the singleton the session reads
+ *    (a separately `require()`d copy would be a no-op target for writes).
+ *
+ * The specifiers MUST BE STRING LITERALS — `import('@oh-my-pi/pi-coding-agent/
+ * config/model-settings')` — never a computed/concatenated string. The host
+ * rewrites extension sources textually (it collects string-literal import
+ * references and swaps them for absolute host paths), so a runtime-built
+ * specifier is not seen by the rewriter and resolves natively against this
+ * package's own 18.1.2 copy, i.e. the handle silently stays `undefined` on
+ * exactly the hosts this adapter exists for. `types/host-settings-modules.d.ts`
+ * supplies the build-time declarations those literal specifiers need.
+ * Each specifier is attempted independently of the others and the result (hit
+ * or miss) is cached for the process lifetime, so a host without these
+ * subpaths pays each failed import exactly once.
+ *
+ * Every helper falls back to the path-based API when the handle is missing, so
+ * hosts <= 18.1 keep their previous behaviour byte-for-byte.
+ */
+
+/** Minimal host registry-handle surface (omp >= 18.3 settings API). */
+export interface HostSettingHandle {
+    /** Write this setting's runtime override (never persisted). */
+    override(settings: unknown, value: unknown): void;
+    /**
+     * Clear this setting's runtime override. Present on handles, but the
+     * documented clear path is `settings.clearOverrideValue(handle)`, so the
+     * adapter tries that first (see {@link clearModelRolesRuntimeOverride}).
+     */
+    clearOverride?(settings: unknown): void;
+}
+
+/** Resolved handle per setting this plugin touches; a miss stays `undefined`. */
+export interface HostSettingsHandles {
+    /** `cfgModelRoles` — `config/model-settings`. */
+    modelRoles?: HostSettingHandle;
+    /** `cfgTaskAgentModelOverrides` — `task/settings`. */
+    taskAgentModelOverrides?: HostSettingHandle;
+    /** `cfgProvidersMaxInFlightRequests` — `session/settings`. */
+    providersMaxInFlight?: HostSettingHandle;
+    /** `cfgEditModelVariants` — `edit/settings`. */
+    editModelVariants?: HostSettingHandle;
+}
+
+interface HandleSpec {
+    key: keyof HostSettingsHandles;
+    exportName: string;
+    /**
+     * Literal-specifier loader (see the header: a computed specifier would not
+     * be rewritten by the host loader). Dynamic, so an older host's missing
+     * subpath rejects instead of breaking module evaluation.
+     */
+    load: () => Promise<unknown>;
+}
+
+const HANDLE_SPECS: readonly HandleSpec[] = [
+    {
+        key: 'modelRoles',
+        exportName: 'cfgModelRoles',
+        load: () => import('@oh-my-pi/pi-coding-agent/config/model-settings'),
+    },
+    {
+        key: 'taskAgentModelOverrides',
+        exportName: 'cfgTaskAgentModelOverrides',
+        load: () => import('@oh-my-pi/pi-coding-agent/task/settings'),
+    },
+    {
+        key: 'providersMaxInFlight',
+        exportName: 'cfgProvidersMaxInFlightRequests',
+        load: () => import('@oh-my-pi/pi-coding-agent/session/settings'),
+    },
+    {
+        key: 'editModelVariants',
+        exportName: 'cfgEditModelVariants',
+        load: () => import('@oh-my-pi/pi-coding-agent/edit/settings'),
+    },
+];
+
+async function loadHandle(spec: HandleSpec): Promise<HostSettingHandle | undefined> {
+    try {
+        const mod = (await spec.load()) as Record<string, unknown> | null | undefined;
+        const candidate = mod?.[spec.exportName] as Partial<HostSettingHandle> | undefined;
+        if (candidate && typeof candidate.override === 'function') return candidate as HostSettingHandle;
+    } catch {
+        /* subpath absent on this host (<= 18.1) — the path-based fallback applies */
+    }
+    return undefined;
+}
+
+let handlesPromise: Promise<HostSettingsHandles> | null = null;
+let handlesForTest: HostSettingsHandles | null | undefined;
+
+/** Test-only seam: inject fake handles, bypassing the dynamic imports. */
+export function _setHandlesForTest(handles: HostSettingsHandles | null | undefined): void {
+    handlesForTest = handles;
+}
+
+/** Test-only seam: drop injected handles and any cached load. */
+export function _resetForTest(): void {
+    handlesForTest = undefined;
+    handlesPromise = null;
+}
+
+/**
+ * Handles of the running host, loaded once per process. A host that lacks the
+ * subpaths yields `{}` — cached, so the failed imports run exactly once.
+ */
+export function hostSettingsHandles(): Promise<HostSettingsHandles> {
+    if (handlesForTest !== undefined) return Promise.resolve(handlesForTest ?? {});
+    handlesPromise ??= (async () => {
+        const out: HostSettingsHandles = {};
+        await Promise.all(
+            HANDLE_SPECS.map(async (spec) => {
+                const handle = await loadHandle(spec);
+                if (handle) out[spec.key] = handle;
+            }),
+        );
+        return out;
+    })();
+    return handlesPromise;
+}
+
+/** Path-based Settings API on hosts <= 18.1. */
+interface PathSettings {
+    override?(path: string, value: unknown): void;
+    clearOverride?(path: string): void;
+}
+
+/** Handle-clearing Settings API on hosts >= 18.3. */
+interface HandleClearingSettings {
+    clearOverrideValue?(handle: unknown): void;
+}
+
+/** Shared write path: registry handle first, path-based `override` second. */
+async function writeOverride(
+    handleKey: keyof HostSettingsHandles,
+    legacyPath: string,
+    settings: unknown,
+    value: unknown,
+): Promise<boolean> {
+    const handle = (await hostSettingsHandles())[handleKey];
+    if (handle) {
+        handle.override(settings, value);
+        return true;
+    }
+    const legacy = typeof settings === 'object' && settings !== null ? (settings as PathSettings) : null;
+    if (legacy && typeof legacy.override === 'function') {
+        legacy.override(legacyPath, value);
+        return true;
+    }
+    return false;
+}
+
+/**
+ * Clear the session-scoped `modelRoles` overlay.
+ *
+ * omp >= 18.3: `settings.clearOverrideValue(cfgModelRoles)` (falling back to
+ * `handle.clearOverride(settings)`). <= 18.1: `settings.clearOverride('modelRoles')`.
+ *
+ * Returns `false` when neither API is present — callers warn and keep writing
+ * (an absent *clear* API does not mean settings are unusable).
+ */
+export async function clearModelRolesRuntimeOverride(settings: unknown): Promise<boolean> {
+    const handle = (await hostSettingsHandles()).modelRoles;
+    if (handle) {
+        const clearing = typeof settings === 'object' && settings !== null
+            ? (settings as HandleClearingSettings)
+            : null;
+        if (clearing && typeof clearing.clearOverrideValue === 'function') {
+            clearing.clearOverrideValue(handle);
+            return true;
+        }
+        if (typeof handle.clearOverride === 'function') {
+            handle.clearOverride(settings);
+            return true;
+        }
+    }
+    const legacy = typeof settings === 'object' && settings !== null ? (settings as PathSettings) : null;
+    if (legacy && typeof legacy.clearOverride === 'function') {
+        legacy.clearOverride('modelRoles');
+        return true;
+    }
+    return false;
+}
+
+/** Write the `task.agentModelOverrides` neutralization (handle API, else path API). */
+export function applyAgentModelOverrides(
+    settings: unknown,
+    value: Record<string, string>,
+): Promise<boolean> {
+    return writeOverride('taskAgentModelOverrides', 'task.agentModelOverrides', settings, value);
+}
+
+/** Hot-apply the complete `providers.maxInFlightRequests` map (handle API, else path API). */
+export function overrideProviderMaxInFlight(
+    settings: unknown,
+    value: Record<string, number>,
+): Promise<boolean> {
+    return writeOverride('providersMaxInFlight', 'providers.maxInFlightRequests', settings, value);
+}
+
+/** Pin `edit.modelVariants` at runtime (handle API, else path API). */
+export function overrideEditModelVariants(
+    settings: unknown,
+    value: Record<string, string>,
+): Promise<boolean> {
+    return writeOverride('editModelVariants', 'edit.modelVariants', settings, value);
+}

package/lib/model-roles.ts

@@ -17,14 +17,17 @@
  * commit/tiny via enumeration fallbacks terminating at smol, task via
  * primary-session inheritance, plan as a graceful no-op, advisor via the
  * static slow chain, custom roles via the config layer. The landing sequence
- * is unchanged: clearOverride('modelRoles') → overrideModelRoles(payload) →
- * empty-string neutralization of persisted per-agent pins.
+ * is unchanged: clear the modelRoles session overlay → overrideModelRoles(payload)
+ * → empty-string neutralization of persisted per-agent pins (the clear and the
+ * neutralization go through `lib/host-settings-adapter.ts`: registry handles on
+ * omp >= 18.3, path-based settings calls before that).
  */
 import { type ModelRole } from '@oh-my-pi/pi-coding-agent/config/model-roles';
 import type { Model, Api } from '@oh-my-pi/pi-catalog/types';
 import type { SelectionContext } from '../index.js';
 import type { TierName } from './model-tiers.js';
-import { OPSX_ROLES } from './unified-config.js';
+import { applyAgentModelOverrides, clearModelRolesRuntimeOverride } from './host-settings-adapter.js';
+import { OPSX_AGENTS } from './unified-config.js';
 
 /** Per-agent names written into `task.agentModelOverrides` neutralization. */
 const AGENT_MODEL_KEYS: Record<string, string> = {
@@ -138,8 +141,8 @@ export function resolveOmpRoleTier(
  * Build the minimal write-set overlay plan (design D5): for each role in
  * `OMP_WRITE_SET_ROLES`, resolve its tier (or `skip`), apply capability
  * gating, then assign the single picked model for the tier. Roles without a
- * pick are recorded with a reason and omitted from the payload — after
- * `clearOverride` they fall back to the user's config layer (or stay
+ * pick are recorded with a reason and omitted from the payload — after the
+ * pre-clear they fall back to the user's config layer (or stay
  * unconfigured). Roles outside the write set are never iterated.
  */
 export function buildRoleOverridePlan(input: BuildRoleOverridePlanInput): RoleOverridePlan {
@@ -222,15 +225,30 @@ export function dispatchModelHint(role: string, selection: SelectionContext): st
  */
 export function agentOverrideNeutralization(): Record<string, string> {
     const neutral: Record<string, string> = {};
-    for (const role of OPSX_ROLES) neutral[AGENT_MODEL_KEYS[role]] = '';
+    for (const role of OPSX_AGENTS) neutral[AGENT_MODEL_KEYS[role]] = '';
     return neutral;
 }
 
-/** Minimal Settings surface this module needs (host-process `pi.pi.settings`). */
+/**
+ * Minimal Settings surface this module needs (host-process `pi.pi.settings`).
+ *
+ * Deliberately a union of both host generations: `overrideModelRoles` (the
+ * session overlay write) exists in every version, while clearing and the
+ * path-based writes moved from `clearOverride(path)` / `override(path, value)`
+ * (<= 18.1) to registry handles (`clearOverrideValue(handle)`, see
+ * `lib/host-settings-adapter.ts`) in 18.3. Optional members keep every
+ * generation assignable; `applyRoleModelOverrides` never assumes a method
+ * exists.
+ */
 export interface RoleSettings {
-    clearOverride(key: string): void;
+    /** Session overlay write (limited to `{smol, default, slow, vision}` by the plan). */
     overrideModelRoles(roles: Record<string, string>): void;
-    override(key: string, value: unknown): void;
+    /** omp <= 18.1: clear the `modelRoles` runtime overlay by path. */
+    clearOverride?(key: string): void;
+    /** omp >= 18.3: clear a runtime overlay through its registry handle. */
+    clearOverrideValue?(handle: unknown): void;
+    /** omp <= 18.1: path-based runtime override. */
+    override?(key: string, value: unknown): void;
 }
 
 /**
@@ -243,25 +261,36 @@ export interface RoleSettings {
  * picked model are omitted and fall back to the config layer after the
  * clear) → neutralize persisted per-agent pins with empty strings. Never writes
  * disk; the runtime overlay is released with the session.
+ *
+ * Async because clearing/writing goes through `lib/host-settings-adapter.ts`,
+ * whose host handles are loaded by dynamic import; every call site awaits.
+ * Clearing and the neutralization write degrade to a warn when this host
+ * offers neither API generation — the missing *clear* is not a reason to skip
+ * the overlay write itself (the plan payload still applies).
  */
-export function applyRoleModelOverrides(
+export async function applyRoleModelOverrides(
     settings: RoleSettings | null | undefined,
     sel: SelectionContext,
     warn: (msg: string) => void = () => {},
-): void {
+): Promise<void> {
     if (!settings) {
         warn('[omp-opsx-addon] pi.pi.settings unavailable; model role overrides skipped');
         return;
     }
-    settings.clearOverride('modelRoles');
+    if (!(await clearModelRolesRuntimeOverride(settings))) {
+        warn('[omp-opsx-addon] no settings API to clear the modelRoles session overlay (host handles and path-based clearOverride both unavailable); writing the overlay without a pre-clear — stale roles from a previous selection may linger');
+    }
     settings.overrideModelRoles(sel.roleOverrides);
-    settings.override('task.agentModelOverrides', agentOverrideNeutralization());
+    const neutralized = await applyAgentModelOverrides(settings, agentOverrideNeutralization());
+    if (!neutralized) {
+        warn('[omp-opsx-addon] no settings API for task.agentModelOverrides (host handles and path-based override both unavailable)');
+    }
     const applied = Object.keys(sel.roleOverrides);
     const skippedText = sel.skippedRoles.length > 0
         ? `; skipped: ${sel.skippedRoles.map((s) => `${s.role}(${s.reason})`).join(', ')}`
         : '';
     const skipWarns = sel.skippedRoles.filter((s) => s.reason !== 'skip');
-    warn(`[omp-opsx-addon] modelRoles applied (${applied.length} roles: ${applied.join(', ') || 'none'})${skippedText}; per-agent pins neutralized`);
+    warn(`[omp-opsx-addon] modelRoles applied (${applied.length} roles: ${applied.join(', ') || 'none'})${skippedText}; per-agent pins ${neutralized ? 'neutralized' : 'NOT neutralized'}`);
     for (const s of skipWarns) {
         if (s.reason === 'capability') {
             warn(`[omp-opsx-addon] model role "${s.role}": no capable model in selection; skipped (role keeps configured/default value; change selector/allowlist or set model_role_tiers.${s.role}: skip)`);