@kici-dev/engine 0.11.0 → 0.12.0

package/dist/audit/access-log-policy.d.ts

@@ -48,8 +48,8 @@ export interface AccessLogRateLimiter {
     permit(action: AccessLogAction, actorKey: string, perMinute: number): boolean;
 }
 /**
- * Policy table mirroring research-doc §2 verdicts (with the user's
- * §7 platform-operator override applied separately in `shouldRecordAccess`).
+ * Per-action recording policy (the platform-operator override is applied
+ * separately in `shouldRecordAccess`).
  *
  * Exhaustive over `AccessLogAction.options` — TypeScript catches additions.
  */

package/dist/audit/access-log-policy.js

@@ -32,8 +32,8 @@ const AccessLogPolicyKind = z.enum([
 	"rate_limit"
 ]);
 /**
-* Policy table mirroring research-doc §2 verdicts (with the user's
-* §7 platform-operator override applied separately in `shouldRecordAccess`).
+* Per-action recording policy (the platform-operator override is applied
+* separately in `shouldRecordAccess`).
 *
 * Exhaustive over `AccessLogAction.options` — TypeScript catches additions.
 */

package/dist/audit/activity.d.ts

@@ -2,8 +2,7 @@
  * Unified Activity row + filter schemas for the dashboard's federated
  * "Activity" view. Federates Platform `audit_log` (mutation events,
  * free-form target_type) with orchestrator `access_log` (reads + admin
- * mutations, strict-enum target_type) at the query layer — see plan
- * `~/.claude/plans/ui-audit-logs-page-sleepy-wave.md`.
+ * mutations, strict-enum target_type) at the query layer.
  *
  * The `source` discriminator on each row tells the UI whether to render
  * the audit_log or access_log column set. Fields unique to access_log

package/dist/audit/activity.js

@@ -7,8 +7,7 @@ import { z } from "zod";
 * Unified Activity row + filter schemas for the dashboard's federated
 * "Activity" view. Federates Platform `audit_log` (mutation events,
 * free-form target_type) with orchestrator `access_log` (reads + admin
-* mutations, strict-enum target_type) at the query layer — see plan
-* `~/.claude/plans/ui-audit-logs-page-sleepy-wave.md`.
+* mutations, strict-enum target_type) at the query layer.
 *
 * The `source` discriminator on each row tells the UI whether to render
 * the audit_log or access_log column set. Fields unique to access_log

package/dist/audit/retention-policy.d.ts

@@ -8,9 +8,7 @@
  * `./access-log-policy.ts`; both modules classify by the same action
  * dimension, just for different downstream decisions.
  *
- * The classification table came from research-doc §5
- *  and the user's
- * `## Decisions` section. Two override layers apply uniformly:
+ * Two override layers apply uniformly:
  *
  * 1. `outcome` is `denied` or `error` → retain 180d (forensic value).
  * 2. `actor.type === 'platform_operator'` → retain 365d

package/dist/audit/retention-policy.js

@@ -100,7 +100,7 @@ const FORENSIC_OUTCOME_DAYS = 180;
 const PLATFORM_OPERATOR_DAYS = 365;
 /**
 * Default warm TTL for action strings outside `AccessLogAction.options`. Hit
-* by E2E synthetic action names and would-be-future enum additions on a
+* by synthetic test action names and would-be-future enum additions on a
 * rolling deploy. Matches the conservative `180d` mutations bucket so
 * unknown rows are never archived sooner than a tenant-plane mutation.
 */

package/dist/context/hold-reason.d.ts

@@ -4,16 +4,14 @@
  * `minimumTrust`.
  *
  * Single source of truth for the sentence: the orchestrator's trust gate emits
- * it, the ci-security DB fixture seeds it, and the unit and E2E assertions
- * compare against it. One copy means a copy edit moves every site at once
- * (`.claude/rules/code-style.md` § "Enums over hardcoded strings").
+ * it, and test fixtures and assertions compare against it. One copy means a
+ * copy edit moves every site at once.
  *
  * `held_runs.reason` is a free-text column, so this is a function rather than
  * an enum: the sentence carries the context name, which is per-hold data.
  *
  * Carries no runtime import on purpose — this module reaches the browser
- * through the engine barrel, which must pull in no Node built-ins
- * (`.claude/rules/engine.md` § "Browser-safe barrel export"). The one import
+ * through the engine barrel, which must pull in no Node built-ins. The one import
  * below is type-only and is erased at compile time.
  */
 import type { TrustTier } from './types.js';

package/dist/labels.d.ts

@@ -13,7 +13,7 @@ import { z } from 'zod';
  *   kici:os:      — operating system (kici:os:linux, kici:os:macos, kici:os:windows)
  *   kici:arch:    — CPU architecture (kici:arch:x64, kici:arch:amd64, kici:arch:arm64)
  *   kici:agent:   — scaler/execution backend type (kici:agent:container, kici:agent:bare-metal, kici:agent:firecracker)
- *   kici:scaler:  — scaler backend name (kici:scaler:stg-container, kici:scaler:prod-firecracker)
+ *   kici:scaler:  — scaler backend name (kici:scaler:linux-container, kici:scaler:prod-firecracker)
  *   kici:host:    — hostname of the machine running the agent (kici:host:<hostname>)
  *   kici:role:    — agent role (kici:role:builder, kici:role:init-runner)
  *

package/dist/labels.js

@@ -15,7 +15,7 @@ import { z } from "zod";
 *   kici:os:      — operating system (kici:os:linux, kici:os:macos, kici:os:windows)
 *   kici:arch:    — CPU architecture (kici:arch:x64, kici:arch:amd64, kici:arch:arm64)
 *   kici:agent:   — scaler/execution backend type (kici:agent:container, kici:agent:bare-metal, kici:agent:firecracker)
-*   kici:scaler:  — scaler backend name (kici:scaler:stg-container, kici:scaler:prod-firecracker)
+*   kici:scaler:  — scaler backend name (kici:scaler:linux-container, kici:scaler:prod-firecracker)
 *   kici:host:    — hostname of the machine running the agent (kici:host:<hostname>)
 *   kici:role:    — agent role (kici:role:builder, kici:role:init-runner)
 *

package/dist/mcp/tool-schemas.d.ts

@@ -4,7 +4,7 @@
  * Browser-safe (zod only) so they live in the shared engine barrel. Each export
  * is a Zod *raw shape* (a plain object of Zod fields) so it can be passed
  * directly as an MCP tool `inputSchema`. The Platform-hosted developer MCP
- * server (packages/platform/src/mcp/server.ts) is the consumer.
+ * server is the consumer.
  */
 import { z } from 'zod';
 export declare const listRunsToolSchema: {

package/dist/mcp/tool-schemas.js

@@ -7,7 +7,7 @@ import { z } from "zod";
 * Browser-safe (zod only) so they live in the shared engine barrel. Each export
 * is a Zod *raw shape* (a plain object of Zod fields) so it can be passed
 * directly as an MCP tool `inputSchema`. The Platform-hosted developer MCP
-* server (packages/platform/src/mcp/server.ts) is the consumer.
+* server is the consumer.
 */
 /**
 * Optional organization id. When the calling user belongs to exactly one org

package/dist/metrics/catalog-policy.d.ts

@@ -2,8 +2,7 @@
  * Hand-maintained label-value policy on top of the auto-generated
  * `MetricLabels` / `MetricKind` allow-list in
  * `./metric-catalog.generated.ts`. Consumed by the Platform's
- * orchestrator-metrics filter (`packages/platform/src/ws/metrics-filter.ts`)
- * to harden the WS `orch.metrics` push path against pollution of the
+ * orchestrator-metrics filter to harden the WS `orch.metrics` push path against pollution of the
  * monitoring system.
  *
  * Three layers compose:

package/dist/metrics/catalog-policy.js

@@ -7,8 +7,7 @@ import { MetricNames, MetricService } from "./metric-catalog.generated.js";
 * Hand-maintained label-value policy on top of the auto-generated
 * `MetricLabels` / `MetricKind` allow-list in
 * `./metric-catalog.generated.ts`. Consumed by the Platform's
-* orchestrator-metrics filter (`packages/platform/src/ws/metrics-filter.ts`)
-* to harden the WS `orch.metrics` push path against pollution of the
+* orchestrator-metrics filter to harden the WS `orch.metrics` push path against pollution of the
 * monitoring system.
 *
 * Three layers compose:

package/dist/protocol/dashboard-global-workflows.d.ts

@@ -3,7 +3,7 @@
  *
  * Consumers import from `@kici-dev/engine/protocol/dashboard-global-workflows`.
  * This file is intentionally kept out of the engine barrel so it remains a
- * server-only surface (see `.claude/rules/engine.md`).
+ * server-only surface: the barrel must stay browser-safe.
  */
 export * from './messages/dashboard-global-workflows.js';
 //# sourceMappingURL=dashboard-global-workflows.d.ts.map

package/dist/protocol/messages/common.d.ts

@@ -24,7 +24,6 @@ export declare const WS_MAX_PAYLOAD_BYTES: number;
  * FAST-PATHED: A manual validator exists in
  * packages/orchestrator/src/ws/agent-handler.ts (isValidHeartbeat).
  * If you change this schema, update the manual validator in the same commit.
- * See CLAUDE.md rule: "Zod fast-path sync invariant".
  */
 export declare const heartbeatSchema: z.ZodObject<{
     type: z.ZodLiteral<"heartbeat">;

package/dist/protocol/messages/common.js

@@ -26,7 +26,6 @@ const WS_MAX_PAYLOAD_BYTES = 26214400;
 * FAST-PATHED: A manual validator exists in
 * packages/orchestrator/src/ws/agent-handler.ts (isValidHeartbeat).
 * If you change this schema, update the manual validator in the same commit.
-* See CLAUDE.md rule: "Zod fast-path sync invariant".
 */
 const heartbeatSchema = z.object({
 	type: z.literal("heartbeat"),

package/dist/protocol/messages/dashboard.d.ts

@@ -34,7 +34,7 @@ export declare const dashboardRunDetailRequestSchema: z.ZodObject<{
 /**
  * Request the machine-first, provenance-tagged structured run result from the
  * orchestrator (user-plane equivalent of the orchestrator-admin
- * `/runs/:id/structured` endpoint). Reuses the Phase-1 `AgentRunResult` shape.
+ * `/runs/:id/structured` endpoint). Reuses the `AgentRunResult` shape.
  */
 export declare const dashboardRunStructuredRequestSchema: z.ZodObject<{
     type: z.ZodLiteral<"dashboard.run.structured">;

package/dist/protocol/messages/dashboard.js

@@ -33,7 +33,7 @@ const dashboardRunDetailRequestSchema = z.object({
 /**
 * Request the machine-first, provenance-tagged structured run result from the
 * orchestrator (user-plane equivalent of the orchestrator-admin
-* `/runs/:id/structured` endpoint). Reuses the Phase-1 `AgentRunResult` shape.
+* `/runs/:id/structured` endpoint). Reuses the `AgentRunResult` shape.
 */
 const dashboardRunStructuredRequestSchema = z.object({
 	type: z.literal("dashboard.run.structured"),
@@ -605,7 +605,7 @@ const runRerunRequestSchema = z.object({
 	actor: actorPrincipalSchema,
 	runId: z.string(),
 	/**
-	* Phase F — Platform forwards the original run's `routing_key` so the
+	* The Platform forwards the original run's `routing_key` so the
 	* orchestrator can probe its cold-store under the right tenant prefix
 	* when the run is missing from PG. Optional for backwards compatibility
 	* with older Platform versions in mixed deploys; if absent, the
@@ -747,7 +747,7 @@ const dashboardEventLogDetailRequestSchema = z.object({
 	orgId: z.string(),
 	deliveryId: z.string(),
 	/**
-	* Phase E cold-store hint: when the Platform side has resurrected the
+	* Cold-store hint: when the Platform side has resurrected the
 	* archived `event_log` row, it forwards the `routing_key` so the
 	* orchestrator can scope its own cold-store fetch to a single tenant
 	* prefix instead of scanning every routing_key for the org.
@@ -831,7 +831,7 @@ const dashboardEventLogPayloadStreamRequestSchema = z.object({
 	orgId: z.string(),
 	deliveryId: z.string(),
 	/**
-	* Phase E cold-store hint: when Platform has resurrected the archived
+	* Cold-store hint: when Platform has resurrected the archived
 	* `event_log` row, it forwards `routing_key` so the orchestrator can scope
 	* its own cold-store fetch to a single tenant prefix instead of scanning
 	* every routing_key for the org. Mirrors `dashboardEventLogDetailRequestSchema`.

package/dist/protocol/messages/orchestrator-agent.d.ts

@@ -378,7 +378,6 @@ export declare const jobAckSchema: z.ZodObject<{
  * FAST-PATHED: A manual validator exists in
  * packages/orchestrator/src/ws/agent-handler.ts (isValidLogChunk).
  * If you change this schema, update the manual validator in the same commit.
- * See CLAUDE.md rule: "Zod fast-path sync invariant".
  */
 export declare const agentLogChunkSchema: z.ZodObject<{
     type: z.ZodLiteral<"log.chunk">;

package/dist/protocol/messages/orchestrator-agent.js

@@ -442,7 +442,6 @@ const jobAckSchema = z.object({
 * FAST-PATHED: A manual validator exists in
 * packages/orchestrator/src/ws/agent-handler.ts (isValidLogChunk).
 * If you change this schema, update the manual validator in the same commit.
-* See CLAUDE.md rule: "Zod fast-path sync invariant".
 */
 const agentLogChunkSchema = z.object({
 	type: z.literal("log.chunk"),

package/dist/protocol/messages/peer.js

@@ -41,7 +41,7 @@ const peerCapabilitiesSchema = z.object({
 * version-skew signal rather than something to ignore.
 */
 const scalerCapacitySummarySchema = z.object({
-	/** Scaler backend name (e.g. "stg-worker-bare-metal") */
+	/** Scaler backend name (e.g. "worker-bare-metal") */
 	name: z.string().optional(),
 	/** Scaler backend type (e.g. "bare-metal", "container") */
 	type: z.string().optional(),

package/dist/protocol/messages/platform-orchestrator.d.ts

@@ -143,12 +143,12 @@ export type TrustPolicyUpdate = z.infer<typeof trustPolicyUpdateSchema>;
  *
  * NOT a wire-parseable schema: this shape is intentionally absent from the
  * `platformToOrchestratorMessageSchema` discriminated union so that a rogue
- * or compromised Platform process (A10) cannot fabricate one and bypass the
+ * or compromised Platform process cannot fabricate one and bypass the
  * on-orchestrator HMAC verification gate. The only legitimate construction
  * site is `completeChunkedRelay` in `packages/orchestrator/src/ws/platform-client.ts`,
  * which synthesizes this shape AFTER `onVerifyInbound` returns `'accepted'`.
  *
- * Migration `packages/platform/src/db/migrations/012_drop_webhook_secret_columns.ts`
+ * The Platform migration that dropped the webhook secret columns
  * makes the orch-side `verifyInboundWebhook` (called from `onVerifyInbound` on
  * the chunked relay path `webhook.relay.start` / `webhook.relay.chunk`) the
  * sole trust boundary against a malicious Platform; keeping this schema OUT
@@ -310,7 +310,7 @@ export type PlatformCapabilitiesMessage = z.infer<typeof platformCapabilitiesMes
  * Platform's monitoring system: a malformed or hostile push fails Zod
  * parse at the WS edge and never reaches the aggregator or the Mimir
  * relay. The content-level allow-list (catalog) is enforced one step
- * deeper — see `packages/platform/src/ws/metrics-filter.ts`.
+ * deeper, in the Platform's orchestrator-metrics filter.
  *
  * Caps:
  * - 2000 metric data points per push (one orch ships ~60 today)
@@ -552,10 +552,10 @@ export type OrchCapabilitiesUpdate = z.infer<typeof orchCapabilitiesUpdateSchema
  * The single-frame `webhookRelaySchema` is intentionally NOT a member of this
  * union: that shape carries an attacker-controlled `payload` and pre-existed
  * the chunked relay's on-orch HMAC verification, so accepting it on the wire
- * would let a compromised Platform (A10) fabricate webhook deliveries that
+ * would let a compromised Platform fabricate webhook deliveries that
  * bypass the only trust boundary against a malicious Platform (see the
- * docblock on `webhookRelaySchema` above and migration
- * `packages/platform/src/db/migrations/012_drop_webhook_secret_columns.ts`).
+ * docblock on `webhookRelaySchema` above and the Platform migration that
+ * dropped the webhook secret columns).
  * The chunked path `webhook.relay.start` + `webhook.relay.chunk` is the sole
  * legitimate route from Platform to `onWebhookRelay`. */
 export declare const platformToOrchestratorMessageSchema: z.ZodDiscriminatedUnion<[z.ZodObject<{

package/dist/protocol/messages/platform-orchestrator.js

@@ -173,12 +173,12 @@ const trustPolicyUpdateSchema = z.object({
 *
 * NOT a wire-parseable schema: this shape is intentionally absent from the
 * `platformToOrchestratorMessageSchema` discriminated union so that a rogue
-* or compromised Platform process (A10) cannot fabricate one and bypass the
+* or compromised Platform process cannot fabricate one and bypass the
 * on-orchestrator HMAC verification gate. The only legitimate construction
 * site is `completeChunkedRelay` in `packages/orchestrator/src/ws/platform-client.ts`,
 * which synthesizes this shape AFTER `onVerifyInbound` returns `'accepted'`.
 *
-* Migration `packages/platform/src/db/migrations/012_drop_webhook_secret_columns.ts`
+* The Platform migration that dropped the webhook secret columns
 * makes the orch-side `verifyInboundWebhook` (called from `onVerifyInbound` on
 * the chunked relay path `webhook.relay.start` / `webhook.relay.chunk`) the
 * sole trust boundary against a malicious Platform; keeping this schema OUT
@@ -363,7 +363,7 @@ const platformCapabilitiesMessageSchema = z.object({
 * Platform's monitoring system: a malformed or hostile push fails Zod
 * parse at the WS edge and never reaches the aggregator or the Mimir
 * relay. The content-level allow-list (catalog) is enforced one step
-* deeper — see `packages/platform/src/ws/metrics-filter.ts`.
+* deeper, in the Platform's orchestrator-metrics filter.
 *
 * Caps:
 * - 2000 metric data points per push (one orch ships ~60 today)
@@ -543,10 +543,10 @@ const orchCapabilitiesUpdateSchema = z.object({
 * The single-frame `webhookRelaySchema` is intentionally NOT a member of this
 * union: that shape carries an attacker-controlled `payload` and pre-existed
 * the chunked relay's on-orch HMAC verification, so accepting it on the wire
-* would let a compromised Platform (A10) fabricate webhook deliveries that
+* would let a compromised Platform fabricate webhook deliveries that
 * bypass the only trust boundary against a malicious Platform (see the
-* docblock on `webhookRelaySchema` above and migration
-* `packages/platform/src/db/migrations/012_drop_webhook_secret_columns.ts`).
+* docblock on `webhookRelaySchema` above and the Platform migration that
+* dropped the webhook secret columns).
 * The chunked path `webhook.relay.start` + `webhook.relay.chunk` is the sole
 * legitimate route from Platform to `onWebhookRelay`. */
 const platformToOrchestratorMessageSchema = z.discriminatedUnion("type", [

package/dist/registration/registerable-trigger-type.d.ts

@@ -14,7 +14,7 @@ import { z } from 'zod';
  *      matched via the per-event lock file pipeline on the same-source path
  *      (e.g. a real GitHub push webhook). Registering them in addition is
  *      what makes cross-source dispatch work for a generic webhook that
- *      targets an externally-hosted repo (phase 28.5): the cross-source
+ *      targets an externally-hosted repo: the cross-source
  *      branch looks up `(customer_id, repo_identifier)` and reuses the
  *      stored `provider_context` (installation id, app id, …) to mint
  *      credentials for the actual provider bundle that owns the repo.

package/dist/registration/registerable-trigger-type.js

@@ -16,7 +16,7 @@ import { z } from "zod";
 *      matched via the per-event lock file pipeline on the same-source path
 *      (e.g. a real GitHub push webhook). Registering them in addition is
 *      what makes cross-source dispatch work for a generic webhook that
-*      targets an externally-hosted repo (phase 28.5): the cross-source
+*      targets an externally-hosted repo: the cross-source
 *      branch looks up `(customer_id, repo_identifier)` and reuses the
 *      stored `provider_context` (installation id, app id, …) to mint
 *      credentials for the actual provider bundle that owns the repo.

package/dist/trigger/decision-trace.d.ts

@@ -159,9 +159,9 @@ export declare function createCommitMessageTraceEntry(args: {
  * What a withheld trace field is replaced with when the reader does not hold
  * `event_log:read_payload`.
  *
- * Lives here rather than beside the Platform's redactor because three packages
- * read it: the Platform writes it, the dashboard renders it, and the E2E suite
- * asserts the permission boundary against it. A literal repeated at each site
+ * Lives here rather than beside the Platform's redactor because it crosses
+ * packages: the Platform writes it, the dashboard renders it, and tests assert
+ * the permission boundary against it. A literal repeated at each site
  * would drift into a marker one of them no longer recognizes.
  */
 export declare const REDACTED_TRACE_FIELD = "[redacted \u2014 requires event_log:read_payload]";

package/dist/trigger/decision-trace.js

@@ -145,9 +145,9 @@ function createCommitMessageTraceEntry(args) {
 * What a withheld trace field is replaced with when the reader does not hold
 * `event_log:read_payload`.
 *
-* Lives here rather than beside the Platform's redactor because three packages
-* read it: the Platform writes it, the dashboard renders it, and the E2E suite
-* asserts the permission boundary against it. A literal repeated at each site
+* Lives here rather than beside the Platform's redactor because it crosses
+* packages: the Platform writes it, the dashboard renders it, and tests assert
+* the permission boundary against it. A literal repeated at each site
 * would drift into a marker one of them no longer recognizes.
 */
 const REDACTED_TRACE_FIELD = "[redacted — requires event_log:read_payload]";

package/dist/trigger/types.d.ts

@@ -732,9 +732,15 @@ export interface ResolvedSandboxGrant {
     capabilities?: string[];
     /** Network override; when set it wins over the config network mode. */
     network?: SandboxNetworkMode;
-    /** Force a read-only rootfs (operator-config path only in Phase 2). */
+    /**
+     * Force a read-only rootfs. The orchestrator does not grant it; the agent's
+     * own config sets it.
+     */
     readonlyRootfs?: boolean;
-    /** Run the container as this user (operator-config path only in Phase 2). */
+    /**
+     * Run the container as this user. The orchestrator does not grant it; the
+     * agent's own config sets it.
+     */
     user?: string;
 }
 /**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kici-dev/engine",
-  "version": "0.11.0",
+  "version": "0.12.0",
   "description": "Shared business logic for the KiCI CI/CD stack: protocol, triggers, state machine, and provider interfaces used by the Platform relay, orchestrator, and compiler.",
   "keywords": [
     "ci",

package/sbom.spdx.json

@@ -2,10 +2,10 @@
   "spdxVersion": "SPDX-2.3",
   "dataLicense": "CC0-1.0",
   "SPDXID": "SPDXRef-DOCUMENT",
-  "name": "@kici-dev/engine@0.11.0",
-  "documentNamespace": "https://kici.dev/sbom/%40kici-dev%2Fengine/0.11.0/551d6e11-b929-4b7a-9e55-d758c60dec3d",
+  "name": "@kici-dev/engine@0.12.0",
+  "documentNamespace": "https://kici.dev/sbom/%40kici-dev%2Fengine/0.12.0/26df8fdf-b46b-49db-86d9-b586bd3124fa",
   "creationInfo": {
-    "created": "2026-09-25T16:08:00Z",
+    "created": "2026-09-28T05:10:36Z",
     "creators": [
       "Tool: kici-sbom-generator"
     ]
@@ -54,7 +54,7 @@
     {
       "SPDXID": "SPDXRef-RootPackage",
       "name": "@kici-dev/engine",
-      "versionInfo": "0.11.0",
+      "versionInfo": "0.12.0",
       "downloadLocation": "NOASSERTION",
       "filesAnalyzed": false,
       "licenseConcluded": "NOASSERTION",
@@ -65,7 +65,7 @@
         {
           "referenceCategory": "PACKAGE-MANAGER",
           "referenceType": "purl",
-          "referenceLocator": "pkg:npm/%40kici-dev/engine@0.11.0"
+          "referenceLocator": "pkg:npm/%40kici-dev/engine@0.12.0"
         }
       ],
       "description": "Shared business logic for the KiCI CI/CD stack: protocol, triggers, state machine, and provider interfaces used by the Platform relay, orchestrator, and compiler.",