@principles/host-runtime 0.3.1 → 0.3.3

package/dist/evaluator-runtime-context.d.ts

@@ -0,0 +1,63 @@
+/**
+ * Evaluator Runtime Context — PRI-661: ONE builder for the deterministic
+ * adversarial-replay context every HOST-NEUTRAL evaluator entry uses.
+ *
+ * WHY THIS EXISTS: PR #1495 wired the shared consumer cycle (in-host
+ * auto-consumer / Codex worker) with production gateDeps + the host-threaded
+ * tool registry, but the host-neutral CLI entries kept divergent wiring:
+ *
+ *   - `pd runtime internalization run-once --runner evaluator` assembled
+ *     EvaluatorRunner with NO gateDeps at all — the deterministic adversarial
+ *     replay was structurally unreachable (the code-bearing guard fails loud
+ *     with an assembly defect instead of evaluating anything);
+ *   - `pd runtime internalization run-rulehost` (rulehost-pipeline-runner)
+ *     replayed through the bare sandbox gate — no workspace root, no host
+ *     tool registry — so a rule could pass generation-time replay and fail
+ *     the production activation gate on the SAME workspace (the exact
+ *     drift class PRI-634-F closed everywhere else).
+ *
+ * WHAT THIS MODULE IS NOT: it is not a second tool registry and not a new
+ * authority. Host-threaded callers (the consumer cycle) keep passing their
+ * live in-memory registry — the running host IS the authority for its own
+ * session. Host-neutral callers omit it and the DURABLE workspace provenance
+ * (`.pd/host-tool-semantics/<hostKind>.json`, persisted by every host on
+ * startup) is resolved through the ONE resolver
+ * (`resolveWorkspaceHostToolSemantics`). Unresolvable provenance is a
+ * structured refusal — never a silent fallback to the core baseline (an
+ * existence check against baseline names is a forged proof; ERR-114).
+ *
+ * Parity contract (pinned by evaluator-runtime-context.test.ts and the
+ * run-once evaluator parity test): the same artifact + workspace + declared
+ * host produces the SAME deterministic replay verdict whether it travels the
+ * consumer cycle (live registry) or a CLI entry (durable declaration), because
+ * hosts persist the same mapping constants they pass in memory.
+ */
+import { type RefinerRuleHostGateDeps, type ToolSemanticRegistry } from '@principles/core/runtime-v2';
+export interface EvaluatorRuntimeContextInput {
+    /** Workspace root the replay normalizes paths against (projectDir). */
+    readonly workspaceDir: string;
+    /**
+     * Host-threaded callers pass their live registry here (consumer-cycle
+     * ports). Host-neutral CLI callers omit it — the durable workspace
+     * declaration is resolved instead.
+     */
+    readonly toolSemantics?: ToolSemanticRegistry;
+}
+export type EvaluatorRuntimeContextResolution = {
+    readonly ok: true;
+    readonly gateDeps: RefinerRuleHostGateDeps;
+} | {
+    readonly ok: false;
+    readonly reason: string;
+    readonly nextAction: string;
+};
+/**
+ * Build the evaluator's deterministic replay context.
+ *
+ * Mirrors the consumer-cycle assembly (PRI-634 A1/A3):
+ *   gateDeps: createProductionGateDeps({ toolSemantics, projectDir: workspaceDir })
+ * — gateDeps belongs to evaluator PRODUCTION semantics, never to host-optional
+ * capability, and always travels in the runner OPTIONS (second constructor
+ * argument), never the deps argument.
+ */
+export declare function createEvaluatorRuntimeContext(input: EvaluatorRuntimeContextInput): EvaluatorRuntimeContextResolution;

package/dist/evaluator-runtime-context.js

@@ -0,0 +1,61 @@
+/**
+ * Evaluator Runtime Context — PRI-661: ONE builder for the deterministic
+ * adversarial-replay context every HOST-NEUTRAL evaluator entry uses.
+ *
+ * WHY THIS EXISTS: PR #1495 wired the shared consumer cycle (in-host
+ * auto-consumer / Codex worker) with production gateDeps + the host-threaded
+ * tool registry, but the host-neutral CLI entries kept divergent wiring:
+ *
+ *   - `pd runtime internalization run-once --runner evaluator` assembled
+ *     EvaluatorRunner with NO gateDeps at all — the deterministic adversarial
+ *     replay was structurally unreachable (the code-bearing guard fails loud
+ *     with an assembly defect instead of evaluating anything);
+ *   - `pd runtime internalization run-rulehost` (rulehost-pipeline-runner)
+ *     replayed through the bare sandbox gate — no workspace root, no host
+ *     tool registry — so a rule could pass generation-time replay and fail
+ *     the production activation gate on the SAME workspace (the exact
+ *     drift class PRI-634-F closed everywhere else).
+ *
+ * WHAT THIS MODULE IS NOT: it is not a second tool registry and not a new
+ * authority. Host-threaded callers (the consumer cycle) keep passing their
+ * live in-memory registry — the running host IS the authority for its own
+ * session. Host-neutral callers omit it and the DURABLE workspace provenance
+ * (`.pd/host-tool-semantics/<hostKind>.json`, persisted by every host on
+ * startup) is resolved through the ONE resolver
+ * (`resolveWorkspaceHostToolSemantics`). Unresolvable provenance is a
+ * structured refusal — never a silent fallback to the core baseline (an
+ * existence check against baseline names is a forged proof; ERR-114).
+ *
+ * Parity contract (pinned by evaluator-runtime-context.test.ts and the
+ * run-once evaluator parity test): the same artifact + workspace + declared
+ * host produces the SAME deterministic replay verdict whether it travels the
+ * consumer cycle (live registry) or a CLI entry (durable declaration), because
+ * hosts persist the same mapping constants they pass in memory.
+ */
+import { createProductionGateDeps, } from '@principles/core/runtime-v2';
+import { resolveWorkspaceHostToolSemantics } from './host-tool-semantic-resolver.js';
+/**
+ * Build the evaluator's deterministic replay context.
+ *
+ * Mirrors the consumer-cycle assembly (PRI-634 A1/A3):
+ *   gateDeps: createProductionGateDeps({ toolSemantics, projectDir: workspaceDir })
+ * — gateDeps belongs to evaluator PRODUCTION semantics, never to host-optional
+ * capability, and always travels in the runner OPTIONS (second constructor
+ * argument), never the deps argument.
+ */
+export function createEvaluatorRuntimeContext(input) {
+    if (input.toolSemantics) {
+        return {
+            ok: true,
+            gateDeps: createProductionGateDeps({ projectDir: input.workspaceDir, toolSemantics: input.toolSemantics }),
+        };
+    }
+    const resolved = resolveWorkspaceHostToolSemantics(input.workspaceDir);
+    if (!resolved.ok) {
+        return { ok: false, reason: resolved.reason, nextAction: resolved.nextAction };
+    }
+    return {
+        ok: true,
+        gateDeps: createProductionGateDeps({ projectDir: input.workspaceDir, toolSemantics: resolved.registry }),
+    };
+}

package/dist/index.d.ts

@@ -17,6 +17,7 @@ export * from './internalization-consumer-governance.js';
 export * from './internalization-consumer-cycle.js';
 export * from './host-tool-declaration.js';
 export * from './host-tool-semantic-resolver.js';
+export * from './evaluator-runtime-context.js';
 export * from './workspace-telemetry-emitter.js';
 export * from './product-telemetry/consent-store.js';
 export * from './product-telemetry/eligibility.js';

package/dist/index.js

@@ -21,6 +21,8 @@ export * from './internalization-consumer-cycle.js';
 // neutral consumers (pd-cli/pd-console) resolve through the ONE resolver.
 export * from './host-tool-declaration.js';
 export * from './host-tool-semantic-resolver.js';
+// PRI-661: ONE evaluator replay-context builder for host-neutral CLI entries.
+export * from './evaluator-runtime-context.js';
 // PRI-634 A3: workspace-scoped critical telemetry — canonical implementation
 // moved from openclaw-plugin so both hosts share ONE semantics.
 export * from './workspace-telemetry-emitter.js';

package/dist/internalization-consumer-cycle.js

@@ -321,7 +321,18 @@ export async function runInternalizationConsumerCycle(workspaceDir, ports) {
         // Issue 2: forward effectiveConfig so runners can resolve feature flags
         // (e.g. `artificer_output_retry`) — mirrors the diagnostician wiring
         // (ADR-0019). Flag-off / absent = legacy behavior.
-        const runnerOptions = { owner, runtimeKind, effectiveConfig: configResult.effective };
+        // PRI-670: also forward the profile-resolved timeout as the runner
+        // deadline — before, runtimeProfile.timeoutMs only reached the adapter as
+        // a per-request timeout and the runner deadline stayed hardcoded at 300s,
+        // so slow/local models could never finish dreamer/evaluator stages.
+        // runtimeConfigResult.timeoutMs is profile-first with a 300s default —
+        // behavior only changes for workspaces that declare a larger timeoutMs.
+        const runnerOptions = {
+            owner,
+            runtimeKind,
+            effectiveConfig: configResult.effective,
+            timeoutMs: runtimeConfigResult.timeoutMs,
+        };
         // PRI-634 A3: workspace-scoped telemetry sink for the evaluator runner.
         // Constructed here (per-wake, workspaceDir in scope) so events from THIS
         // workspace's runner are attributable to THIS workspace — a global

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@principles/host-runtime",
-  "version": "0.3.1",
+  "version": "0.3.3",
   "description": "Shared host-neutral orchestration for Principles Disciple MVP-Core hook paths.",
   "type": "module",
   "main": "./dist/index.js",
@@ -22,7 +22,7 @@
   },
   "dependencies": {
     "@principles/core": "^1.74.1",
-    "@principles/install-layout": "0.1.0",
+    "@principles/install-layout": "^0.2.0",
     "better-sqlite3": "^13.0.3",
     "js-yaml": "^5.2.0"
   },