@kici-dev/compiler 0.1.12 → 0.1.14

package/dist/llm-context/llms-full.txt

@@ -6,7 +6,7 @@ This file is the concatenated markdown of every KiCI documentation page intended
 
 ## User guide
 
-Source: https://kici.dev/docs/user/
+Source: https://docs.kici.dev/user/
 
 Documentation for workflow authors -- people writing CI/CD pipelines in TypeScript using the KiCI SDK and compiler. If you are defining workflows, running local tests, or learning the SDK API, start here.
 
@@ -88,7 +88,7 @@ Cross-repo workflows that let a single workflow repo define jobs which run on ev
 
 ## Getting started with KiCI
 
-Source: https://kici.dev/docs/user/getting-started/
+Source: https://docs.kici.dev/user/getting-started/
 
 KiCI lets you define CI/CD workflows in TypeScript instead of YAML. You get full language power -- type safety, autocompletion, loops, conditionals, and async/await -- for your build pipelines.
 
@@ -480,7 +480,7 @@ The lock file approach means the orchestrator stays git-agnostic -- it only need
 
 ## 5-minute quickstart
 
-Source: https://kici.dev/docs/user/quickstart/
+Source: https://docs.kici.dev/user/quickstart/
 
 KiCI offers two equally-supported quickstart paths. Pick the one that fits your machine — both end with the same working pipeline (orchestrator + agent + your first workflow run visible in the dashboard).
 
@@ -517,7 +517,7 @@ Both quickstarts deploy a real orchestrator + agent. If you only want to write a
 
 ## Basic workflow patterns
 
-Source: https://kici.dev/docs/user/patterns/basic/
+Source: https://docs.kici.dev/user/patterns/basic/
 
 A standard lint-then-test pipeline using job dependencies (`needs`):
 
@@ -767,7 +767,7 @@ Leave `dispatch()` unfiltered while you drive it from `kici run local`. The CLI
 
 ## Conditionals & matrix patterns
 
-Source: https://kici.dev/docs/user/patterns/conditionals-matrix/
+Source: https://docs.kici.dev/user/patterns/conditionals-matrix/
 
 Rules control whether a workflow or job runs. Use `rule()` for conditions that must pass, and `skip()` for conditions that should skip execution.
 
@@ -1098,7 +1098,7 @@ This workflow:
 
 ## Integration patterns
 
-Source: https://kici.dev/docs/user/patterns/integrations/
+Source: https://docs.kici.dev/user/patterns/integrations/
 
 Use internal event triggers to chain workflows together. Workflow A completes, emits an event (or the system auto-emits a completion event), and Workflow B triggers in response.
 
@@ -1412,7 +1412,7 @@ export default workflow('on-github-repo-push', {
 
 ## Pattern reference
 
-Source: https://kici.dev/docs/user/patterns/reference/
+Source: https://docs.kici.dev/user/patterns/reference/
 
 Every step receives a `StepContext` with these properties:
 
@@ -1490,7 +1490,7 @@ pnpm kici compile  # Regenerates kici.lock.json with source locations
 
 ## Scheduling & event patterns
 
-Source: https://kici.dev/docs/user/patterns/scheduling-and-events/
+Source: https://docs.kici.dev/user/patterns/scheduling-and-events/
 
 Run a full build and test suite on a schedule using `schedule()`. Schedule triggers are evaluated by the orchestrator's Raft leader in clustered deployments.
 
@@ -1684,7 +1684,7 @@ export const autoDeploy = workflow('auto-deploy', {
 
 ## SDK reference: core
 
-Source: https://kici.dev/docs/user/sdk/core/
+Source: https://docs.kici.dev/user/sdk/core/
 
 ## Factory functions
 
@@ -2171,7 +2171,7 @@ These IDs are stable as long as the order of unnamed entries does not change. Ad
 
 ## SDK reference: idempotent
 
-Source: https://kici.dev/docs/user/sdk/idempotent/
+Source: https://docs.kici.dev/user/sdk/idempotent/
 
 The SDK exposes two idempotency helpers — a generic function `idempotent()` and a step factory `idempotentStep()` — for the common case where a workflow step should:
 
@@ -2321,7 +2321,7 @@ The caller never has to branch on outcome — `result.result` is always a `Bucke
 
 ## SDK reference: rules, matrix, dynamic jobs
 
-Source: https://kici.dev/docs/user/sdk/rules-matrix-dynamic/
+Source: https://docs.kici.dev/user/sdk/rules-matrix-dynamic/
 
 ## Rules
 
@@ -2644,7 +2644,7 @@ for (const item of workflow.jobs) {
 
 ## SDK reference: runtime
 
-Source: https://kici.dev/docs/user/sdk/runtime/
+Source: https://docs.kici.dev/user/sdk/runtime/
 
 ## Types
 
@@ -3110,7 +3110,7 @@ Options can also be provided as an async factory function for dynamic fixture ge
 
 ## SDK reference: triggers
 
-Source: https://kici.dev/docs/user/sdk/triggers/
+Source: https://docs.kici.dev/user/sdk/triggers/
 
 ## Triggers
 
@@ -3611,7 +3611,7 @@ Glob patterns use micromatch syntax. Regex patterns use standard JavaScript `Reg
 
 ## SDK reference: validation & events
 
-Source: https://kici.dev/docs/user/sdk/validation-events/
+Source: https://docs.kici.dev/user/sdk/validation-events/
 
 ## Validation
 
@@ -3774,7 +3774,7 @@ The orchestrator automatically emits system events for workflow and job completi
 
 ## SDK reference: waitFor
 
-Source: https://kici.dev/docs/user/sdk/wait-for/
+Source: https://docs.kici.dev/user/sdk/wait-for/
 
 The SDK exposes two wait-for helpers — a generic function `waitFor()` and a step factory `waitForStep()` — for the common case where a workflow step should:
 
@@ -3890,7 +3890,7 @@ If `check()` throws while polling, the error is logged and polling continues —
 
 ## SDK reference
 
-Source: https://kici.dev/docs/user/sdk-reference/
+Source: https://docs.kici.dev/user/sdk-reference/
 
 Reference documentation for `@kici-dev/sdk`. The reference is split across five pages by topic.
 
@@ -3927,7 +3927,7 @@ For the complete list of every named export (factory functions, triggers, rules,
 
 ## CLI authentication
 
-Source: https://kici.dev/docs/user/cli-auth/
+Source: https://docs.kici.dev/user/cli-auth/
 
 The KiCI CLI supports three authentication methods: browser-based OAuth (default), device authorization flow (for headless environments), and API key paste (for CI/CD pipelines).
 
@@ -4188,7 +4188,7 @@ If the CLI can't reach the server:
 
 ## CLI reference
 
-Source: https://kici.dev/docs/user/cli-reference/
+Source: https://docs.kici.dev/user/cli-reference/
 
 The `@kici-dev/compiler` package provides the `kici` CLI for compiling, testing, and managing workflows.
 
@@ -4561,15 +4561,14 @@ kici login [options]
 
 **Environment variables:**
 
-| Variable               | Default                   | Description                                                            |
-| ---------------------- | ------------------------- | ---------------------------------------------------------------------- |
-| `KICI_PLATFORM_URL`    | none (required for OAuth) | Platform API base URL                                                  |
-| `KICI_OIDC_ISSUER`     | none (required for OAuth) | OIDC issuer URL                                                        |
-| `KICI_OIDC_CLIENT_ID`  | none (required for OAuth) | OIDC client ID                                                         |
-| `KICI_OIDC_PROJECT_ID` | none                      | OIDC project ID                                                        |
-| `KICI_BROWSER_CMD`     | uses `open` package       | Custom browser command with `{url}` placeholder, or `none` to suppress |
-| `KICI_CALLBACK_PORT`   | random                    | Fixed port for OAuth PKCE callback server                              |
-| `KICI_CONFIG_DIR`      | `~/.kici`                 | Override config directory                                              |
+| Variable              | Default                   | Description                                                            |
+| --------------------- | ------------------------- | ---------------------------------------------------------------------- |
+| `KICI_PLATFORM_URL`   | none (required for OAuth) | Platform API base URL                                                  |
+| `KICI_OIDC_ISSUER`    | none (required for OAuth) | OIDC issuer URL                                                        |
+| `KICI_OIDC_CLIENT_ID` | none (required for OAuth) | OIDC client ID                                                         |
+| `KICI_BROWSER_CMD`    | uses `open` package       | Custom browser command with `{url}` placeholder, or `none` to suppress |
+| `KICI_CALLBACK_PORT`  | random                    | Fixed port for OAuth PKCE callback server                              |
+| `KICI_CONFIG_DIR`     | `~/.kici`                 | Override config directory                                              |
 
 **Examples:**
 
@@ -5162,7 +5161,7 @@ Set `KICI_DEBUG=true` for additional internal debug output across all commands.
 
 ## Lifecycle hooks
 
-Source: https://kici.dev/docs/user/hooks/
+Source: https://docs.kici.dev/user/hooks/
 
 Hooks are callbacks that run at specific points in the execution lifecycle. They let you react to outcomes (cancellation, success, failure) and perform cleanup without affecting the execution flow.
 
@@ -5402,7 +5401,7 @@ _Source: `packages/sdk/src/hooks/`, `packages/sdk/src/types.ts`_
 
 ## Lock file and workflow drift
 
-Source: https://kici.dev/docs/user/lock-file-and-drift/
+Source: https://docs.kici.dev/user/lock-file-and-drift/
 
 KiCI uses a **two-artifact model**: TypeScript workflows are the source of truth; the lock file (`kici.lock.json`) is the execution contract. The orchestrator reads only the lock file to match triggers and decide cache vs build. Keeping these in sync is important.
 
@@ -5525,7 +5524,7 @@ So even without a pre-commit or CI check, a stale lock file will cause the run t
 
 ## Testing guide
 
-Source: https://kici.dev/docs/user/testing-guide/
+Source: https://docs.kici.dev/user/testing-guide/
 
 Test your workflows remotely against the full CI pipeline from your local machine. `kici run remote` uploads your current repo state (including uncommitted changes), triggers the pipeline, and streams execution logs back in real time.
 
@@ -5898,7 +5897,7 @@ export const pushMain = fixture('push-main', {
 
 ## Workflow patterns
 
-Source: https://kici.dev/docs/user/workflow-patterns/
+Source: https://docs.kici.dev/user/workflow-patterns/
 
 Practical patterns for building real-world KiCI workflows in TypeScript. The patterns are organised across five pages -- start with [Basic CI](./patterns/basic.md) if you're new, or jump to [Integrations](./patterns/integrations.md) if you're wiring up a non-GitHub forge or a generic webhook.
 
@@ -5925,7 +5924,7 @@ Practical patterns for building real-world KiCI workflows in TypeScript. The pat
 
 ## Concurrency groups
 
-Source: https://kici.dev/docs/user/concurrency/
+Source: https://docs.kici.dev/user/concurrency/
 
 Concurrency groups prevent multiple workflow runs from executing in parallel when they target the same resource. Common use cases include preventing parallel deploys to the same environment or serializing database migrations.
 
@@ -6150,10 +6149,34 @@ _Source: `packages/sdk/src/types.ts` (WorkflowOptions.concurrency, JobOptions.co
 
 ## Dashboard
 
-Source: https://kici.dev/docs/user/dashboard/
+Source: https://docs.kici.dev/user/dashboard/
 
 The KiCI dashboard is a web-based interface for monitoring workflow runs, inspecting job and step details, and reading log output. It is a browser single-page application that authenticates via OIDC and communicates with the Platform tier through REST API endpoints.
 
+## Getting started
+
+<!-- help:getting-started-overview#getting-started -->
+
+The getting-started page is a six-step checklist that takes you from zero to your first workflow run.
+
+- **Self-checked steps** -- install the CLI, scaffold a workflow, and run it locally. These run on your own machine, so you tick them off yourself; the dashboard remembers your choices in the browser.
+- **Auto-detected steps** -- connect an orchestrator, add a webhook source, and trigger your first run. These tick automatically as the dashboard observes the matching activity in your organization.
+
+Each step links to the relevant settings page or documentation. A progress bar tracks overall completion, and the sidebar entry shows a `done/total` badge until you finish or dismiss reminders.
+
+<!-- /help:getting-started-overview -->
+
+When you first sign in to a brand-new organization with no orchestrator, no webhook source, and no runs, the dashboard opens this page automatically. Once your organization has any activity, the run list becomes your landing page instead. The **Getting started** sidebar entry stays available so you can return to the checklist at any time.
+
+The six steps are:
+
+1. **Install the kici CLI** -- `npm install -g kici`.
+2. **Create a workflow** -- `kici init` scaffolds a `.kici/` directory in your repository.
+3. **Run a workflow locally** -- `kici test pr:open --dry-run` executes a workflow on your machine with no orchestrator required.
+4. **Connect an orchestrator** -- deploy an orchestrator and connect it with a join token from **Settings → Orchestrator keys**.
+5. **Add a webhook source** -- register a source under **Settings → Sources** so pushes and pull requests trigger runs.
+6. **Trigger your first run** -- push to your repository to produce your first run through the relay.
+
 ## Navigation
 
 ### Sidebar
@@ -6161,6 +6184,7 @@ The KiCI dashboard is a web-based interface for monitoring workflow runs, inspec
 The left sidebar provides persistent navigation across all org-scoped pages:
 
 - **Org switcher** -- dropdown at the top to switch between organizations
+- **Getting started** -- onboarding checklist (shows a `done/total` badge until complete or dismissed)
 - **Runs** -- the default landing page, showing your workflow run history
 - **Workflows** -- permanently registered workflows listening for events
 - **Diagnostics** -- infrastructure health, execution metrics, and recent errors
@@ -7107,7 +7131,7 @@ The dashboard shows informative error pages instead of blank screens:
 
 ## Dynamic values
 
-Source: https://kici.dev/docs/user/dynamic-values/
+Source: https://docs.kici.dev/user/dynamic-values/
 
 Dynamic values let you compute `environment`, `env`, and `concurrencyGroup` at runtime based on the incoming event. Instead of hardcoding static strings, you pass a function that receives the webhook event payload and returns the resolved value.
 
@@ -7214,7 +7238,7 @@ env: async (event) => {
 
 ## Environment variables
 
-Source: https://kici.dev/docs/user/env-vars/
+Source: https://docs.kici.dev/user/env-vars/
 
 The KiCI CLI reads the following environment variables to customize its behavior. OAuth login (`kici login` without `--token`) requires `KICI_PLATFORM_URL`, `KICI_OIDC_ISSUER`, and `KICI_OIDC_CLIENT_ID` to be set — the CLI does not ship defaults for them.
 
@@ -7295,7 +7319,7 @@ kici login
 
 ## Environments
 
-Source: https://kici.dev/docs/user/environments/
+Source: https://docs.kici.dev/user/environments/
 
 <!-- help:environments-list#overview -->
 
@@ -7584,7 +7608,7 @@ interface EnvironmentSecrets {
 
 ## Event system
 
-Source: https://kici.dev/docs/user/events/
+Source: https://docs.kici.dev/user/events/
 
 KiCI supports two broad categories of workflow triggers: **git-based triggers** that work immediately, and **event-based triggers** that use a registration model. Understanding this distinction is key to working effectively with non-git triggers like schedules, custom events, and generic webhooks.
 
@@ -7959,7 +7983,7 @@ Custom events are delivered immediately when emitted (mid-workflow, not queued u
 
 ## Global workflows
 
-Source: https://kici.dev/docs/user/global-workflows/
+Source: https://docs.kici.dev/user/global-workflows/
 
 Global workflows let one **workflow repo** define jobs that run on events from many **source repos** in the same org. They're the answer to "I want one CI policy / release pipeline / security scan to fire on every repo without copy-pasting `.kici/` folders everywhere."
 
@@ -8081,7 +8105,7 @@ Non-push triggers work too — `pr()`, `tag()`, `comment()`, `release()`, `workf
 
 ## Private npm registries
 
-Source: https://kici.dev/docs/user/private-registries/
+Source: https://docs.kici.dev/user/private-registries/
 
 A workflow's `.kici/package.json` may depend on packages published to a private registry — your org's internal CodeArtifact, a GitHub Packages scope, a self-hosted Verdaccio, JFrog, Cloudsmith, GitLab, etc. KiCI ships two ways to authenticate `npm install` against those registries from inside a job, plus an escape hatch for short-lived tokens.
 
@@ -8329,7 +8353,7 @@ The dashboard JSON lives at `infra/terraform/modules/grafana/dashboards/install-
 
 ## Secrets
 
-Source: https://kici.dev/docs/user/secrets/
+Source: https://docs.kici.dev/user/secrets/
 
 KiCI provides an explicit secrets API that gives workflow steps controlled access to secrets stored in the orchestrator's secret store. Secrets are never auto-injected into `process.env` -- you must explicitly request each secret by name.
 
@@ -8595,7 +8619,7 @@ See [CLI reference](/user/cli) for the `kici types` command.
 
 ## GitHub App provider
 
-Source: https://kici.dev/docs/user/providers/github/
+Source: https://docs.kici.dev/user/providers/github/
 
 The **GitHub App** is KiCI's flagship source. A single App:
 
@@ -8911,7 +8935,7 @@ and confirm the App is installed on that repo.
 
 ## Universal-git provider
 
-Source: https://kici.dev/docs/user/providers/universal-git/
+Source: https://docs.kici.dev/user/providers/universal-git/
 
 The **universal-git** provider lets KiCI treat any git forge that speaks a
 GitHub-shaped webhook payload as a first-class source. That covers Forgejo,
@@ -9152,7 +9176,7 @@ with the right PEM.
 
 ## Data flows
 
-Source: https://kici.dev/docs/architecture/data-flows/
+Source: https://docs.kici.dev/architecture/data-flows/
 
 This document describes the key data flows through the KiCI architecture: webhook delivery, job execution, dependency caching, re-run and cancel, trace ID propagation, internal event routing, and generic webhook ingestion.
 
@@ -9917,7 +9941,7 @@ The Platform tier exposes a `/ws/browser` WebSocket endpoint for dashboard clien
 
 ## Design decisions
 
-Source: https://kici.dev/docs/architecture/design-decisions/
+Source: https://docs.kici.dev/architecture/design-decisions/
 
 This page explains the rationale behind KiCI's major architectural choices. Each section describes the decision, why it was made, and what alternatives were considered.
 
@@ -10052,7 +10076,7 @@ The orchestrator evaluates static triggers from the lock file -- branch patterns
 
 ## Architecture overview
 
-Source: https://kici.dev/docs/architecture/overview/
+Source: https://docs.kici.dev/architecture/overview/
 
 KiCI uses a three-tier relay model that separates webhook routing from code execution. Customer code never leaves customer infrastructure -- the Platform tier handles only webhook verification and routing, while the orchestrator and agent tiers run on customer-managed servers.
 
@@ -10137,7 +10161,7 @@ Shared business logic used by all three tiers. Single source of truth for cross-
 - Audit policy and retention (per-action access-log sampling, warm-retention windows for cold-store eligibility, federated activity row schema)
 - Scaler backend type enum (`container`, `bare-metal`, `firecracker`, `kubernetes`)
 - Registration trigger type enum (registerable trigger discriminator)
-- Bundler config (shared bundler configuration consumed by `e2e/helpers/service-deploy.ts`; the agent runtime uses the shared `@kici-dev/shared/ts-loader-hook` to transform TypeScript on import, with no runtime bundler step)
+- Bundler config (shared bundler configuration consumed by `e2e/helpers/service-deploy.ts`; the agent runtime uses the `@kici-dev/core/ts-loader-hook` to transform TypeScript on import, with no runtime bundler step)
 
 > Source: `packages/engine/src/`
 
@@ -10153,9 +10177,15 @@ CLI tooling for workflow authors. Compiles `.kici/workflows/*.ts` to `.kici/kici
 
 > Source: `packages/compiler/src/`
 
+### `@kici-dev/core`
+
+Light shared utilities with no server-side dependencies — JSON-structured logging, error helpers, human-readable formatting (`formatBytes`/`formatDuration`/`formatUptime`), cryptographic helpers (`sha256`/`sha256File`/`deriveSharedSecret`), zx initialization (`initZx()`), and the TypeScript loader hook that transforms TypeScript on import. It is the dependency-light core that the SDK, compiler, and `kici` CLI consume directly so they stay free of heavier server-only dependencies. `@kici-dev/shared` re-exports it, so existing `@kici-dev/shared` import paths keep working.
+
+> Source: `packages/core/src/`
+
 ### `@kici-dev/shared`
 
-Shared utilities used across packages. Provides `initZx()` for zx initialization, `createLogger()` for JSON-structured logging with TTY-aware formatting, `createPool()`/`createDb()` for typed PostgreSQL connections, `createMetricsRoutes()`/`createHealthRoutes()` for HTTP route factories (Prometheus metrics and health endpoints), `RingBuffer` for bounded collections, `requestContext`/`getRequestContext()`/`enrichRequestContext()` for async local storage request context, `getReconnectDelay()` for exponential backoff, `formatBytes`/`formatDuration`/`formatUptime` for human-readable formatting, `sha256`/`sha256File`/`deriveSharedSecret` for cryptographic utilities, `initTelemetry`/`createMeter` for OpenTelemetry integration, and `setupGracefulShutdown` for coordinated service shutdown with ordered steps.
+Shared utilities used across packages, including everything from `@kici-dev/core` (re-exported) plus server-side helpers. Provides `initZx()` for zx initialization, `createLogger()` for JSON-structured logging with TTY-aware formatting, `createPool()`/`createDb()` for typed PostgreSQL connections, `createMetricsRoutes()`/`createHealthRoutes()` for HTTP route factories (Prometheus metrics and health endpoints), `RingBuffer` for bounded collections, `requestContext`/`getRequestContext()`/`enrichRequestContext()` for async local storage request context, `getReconnectDelay()` for exponential backoff, `formatBytes`/`formatDuration`/`formatUptime` for human-readable formatting, `sha256`/`sha256File`/`deriveSharedSecret` for cryptographic utilities, `initTelemetry`/`createMeter` for OpenTelemetry integration, and `setupGracefulShutdown` for coordinated service shutdown with ordered steps.
 
 > Source: `packages/shared/src/`
 
@@ -10181,6 +10211,7 @@ The following diagram shows how `@kici` packages depend on each other. Solid arr
 
 ```mermaid
 flowchart TD
+    CORE["@kici-dev/core"]
     SDK["@kici-dev/sdk"]
     COMPILER["@kici-dev/compiler"]
     SHARED["@kici-dev/shared"]
@@ -10192,10 +10223,11 @@ flowchart TD
 
     DASH --> ENGINE
     DASH -.->|dev| PLATFORM
+    SHARED --> CORE
     SDK --> ENGINE
-    SDK --> SHARED
+    SDK --> CORE
     COMPILER --> ENGINE
-    COMPILER --> SHARED
+    COMPILER --> CORE
     COMPILER -.->|peer| SDK
     PLATFORM --> ENGINE
     PLATFORM --> SHARED
@@ -10206,12 +10238,12 @@ flowchart TD
     AGENT --> SHARED
     KICI["kici (wrapper)"]
     KICI --> COMPILER
-    KICI --> SHARED
+    KICI --> CORE
     KICIADMIN["kici-admin (admin CLI)"]
     KICIADMIN --> ORCH
 ```
 
-**Leaf packages** (no `@kici` dependencies): `@kici-dev/shared` and `@kici-dev/engine`. These can be tested and built independently. The dashboard depends on `@kici-dev/engine` for shared types (protocol schemas, state machine) and imports the Platform's API type definitions as a dev dependency, but communicates with backend services at runtime via HTTP/WebSocket, not at compile time.
+**Leaf packages** (no `@kici` dependencies): `@kici-dev/core` and `@kici-dev/engine`. These can be tested and built independently. `@kici-dev/shared` builds on `@kici-dev/core` and re-exports it. The dashboard depends on `@kici-dev/engine` for shared types (protocol schemas, state machine) and imports the Platform's API type definitions as a dev dependency, but communicates with backend services at runtime via HTTP/WebSocket, not at compile time.
 
 **Runtime tiers** (Platform, orchestrator, agent) all depend on `@kici-dev/engine` for shared business logic and `@kici-dev/shared` for utilities. Only the agent depends on `@kici-dev/sdk` (it loads workflow definitions at runtime).
 

package/dist/llm-context/llms.txt

@@ -2,61 +2,61 @@
 
 > KiCI is a TypeScript-native CI/CD workflow engine. Workflows are defined in TypeScript (not YAML), compiled into a portable lock file, and executed by self-hosted agents. The docs below cover the SDK, the CLI, workflow patterns, and the runtime architecture an LLM coding agent needs in order to author and test KiCI workflows.
 
-The full markdown bundle of every page indexed here is available at https://kici.dev/llms-full.txt.
+The full markdown bundle of every page indexed here is available at https://docs.kici.dev/llms-full.txt.
 
 ## Getting started
 
-- [User guide](https://kici.dev/docs/user/): Writing and testing CI/CD workflows in TypeScript
-- [Getting started with KiCI](https://kici.dev/docs/user/getting-started/): Install the SDK, write your first workflow, compile and test locally
-- [5-minute quickstart](https://kici.dev/docs/user/quickstart/): Stand up a KiCI orchestrator + agent and run your first workflow
+- [User guide](https://docs.kici.dev/user/): Writing and testing CI/CD workflows in TypeScript
+- [Getting started with KiCI](https://docs.kici.dev/user/getting-started/): Install the SDK, write your first workflow, compile and test locally
+- [5-minute quickstart](https://docs.kici.dev/user/quickstart/): Stand up a KiCI orchestrator + agent and run your first workflow
 
 ## Workflow patterns
 
-- [Basic workflow patterns](https://kici.dev/docs/user/patterns/basic/): Basic CI, PR-only / push-only filters, multiple triggers, manual-only workflows
-- [Conditionals & matrix patterns](https://kici.dev/docs/user/patterns/conditionals-matrix/): Conditional execution with rules, matrix builds (static + dynamic), dynamic job generation
-- [Integration patterns](https://kici.dev/docs/user/patterns/integrations/): Workflow chaining, generic webhooks, Stripe, self-hosted git forges, plain GitHub repos
-- [Pattern reference](https://kici.dev/docs/user/patterns/reference/): Step context, examples repository, GitHub check run output — cross-cutting reference for all patterns
-- [Scheduling & event patterns](https://kici.dev/docs/user/patterns/scheduling-and-events/): Nightly cron, workflow-complete-triggered deploys, custom event chaining
+- [Basic workflow patterns](https://docs.kici.dev/user/patterns/basic/): Basic CI, PR-only / push-only filters, multiple triggers, manual-only workflows
+- [Conditionals & matrix patterns](https://docs.kici.dev/user/patterns/conditionals-matrix/): Conditional execution with rules, matrix builds (static + dynamic), dynamic job generation
+- [Integration patterns](https://docs.kici.dev/user/patterns/integrations/): Workflow chaining, generic webhooks, Stripe, self-hosted git forges, plain GitHub repos
+- [Pattern reference](https://docs.kici.dev/user/patterns/reference/): Step context, examples repository, GitHub check run output — cross-cutting reference for all patterns
+- [Scheduling & event patterns](https://docs.kici.dev/user/patterns/scheduling-and-events/): Nightly cron, workflow-complete-triggered deploys, custom event chaining
 
 ## SDK reference
 
-- [SDK reference: core](https://kici.dev/docs/user/sdk/core/): Factory functions (workflow, job, step) and authoring patterns: needs, output chaining, dynamic groups
-- [SDK reference: idempotent](https://kici.dev/docs/user/sdk/idempotent/): Idempotent helpers for declarative check / apply patterns inside workflow steps
-- [SDK reference: rules, matrix, dynamic jobs](https://kici.dev/docs/user/sdk/rules-matrix-dynamic/): rule(), skip(), matrix builds (static + dynamic), and dynamicJob / dynamicGroup
-- [SDK reference: runtime](https://kici.dev/docs/user/sdk/runtime/): Types index, StepContext, secrets, fixtures
-- [SDK reference: triggers](https://kici.dev/docs/user/sdk/triggers/): GitHub event triggers, kiciEvent, workflowComplete, jobComplete, genericWebhook, schedule, lifecycle
-- [SDK reference: validation & events](https://kici.dev/docs/user/sdk/validation-events/): validateDag(), event definitions, and event emission
-- [SDK reference: waitFor](https://kici.dev/docs/user/sdk/wait-for/): Polling helpers for steps that pause until an external condition becomes true
-- [SDK reference](https://kici.dev/docs/user/sdk-reference/): Complete API reference for @kici-dev/sdk -- workflows, jobs, steps, triggers, rules, matrix, validation, runtime
+- [SDK reference: core](https://docs.kici.dev/user/sdk/core/): Factory functions (workflow, job, step) and authoring patterns: needs, output chaining, dynamic groups
+- [SDK reference: idempotent](https://docs.kici.dev/user/sdk/idempotent/): Idempotent helpers for declarative check / apply patterns inside workflow steps
+- [SDK reference: rules, matrix, dynamic jobs](https://docs.kici.dev/user/sdk/rules-matrix-dynamic/): rule(), skip(), matrix builds (static + dynamic), and dynamicJob / dynamicGroup
+- [SDK reference: runtime](https://docs.kici.dev/user/sdk/runtime/): Types index, StepContext, secrets, fixtures
+- [SDK reference: triggers](https://docs.kici.dev/user/sdk/triggers/): GitHub event triggers, kiciEvent, workflowComplete, jobComplete, genericWebhook, schedule, lifecycle
+- [SDK reference: validation & events](https://docs.kici.dev/user/sdk/validation-events/): validateDag(), event definitions, and event emission
+- [SDK reference: waitFor](https://docs.kici.dev/user/sdk/wait-for/): Polling helpers for steps that pause until an external condition becomes true
+- [SDK reference](https://docs.kici.dev/user/sdk-reference/): Complete API reference for @kici-dev/sdk -- workflows, jobs, steps, triggers, rules, matrix, validation, runtime
 
 ## CLI and authoring
 
-- [CLI authentication](https://kici.dev/docs/user/cli-auth/): Authenticate the KiCI CLI with browser OAuth, device flow, or API key paste
-- [CLI reference](https://kici.dev/docs/user/cli-reference/): All CLI commands: compile, run (local/remote), test, login, logout, org, status, cancel, secrets, types, fixture, init, hook, endpoints, workflows, docs, admin
-- [Lifecycle hooks](https://kici.dev/docs/user/hooks/): SDK hook API for cancel, cleanup, success, failure, and step-level callbacks
-- [Lock file and workflow drift](https://kici.dev/docs/user/lock-file-and-drift/): Keep the lock file in sync with your workflow source and avoid drift
-- [Testing guide](https://kici.dev/docs/user/testing-guide/): Running remote test fixtures with kici run remote
-- [Workflow patterns](https://kici.dev/docs/user/workflow-patterns/): Common patterns: monorepo builds, conditional jobs, dynamic matrices, generic webhooks, scheduling
+- [CLI authentication](https://docs.kici.dev/user/cli-auth/): Authenticate the KiCI CLI with browser OAuth, device flow, or API key paste
+- [CLI reference](https://docs.kici.dev/user/cli-reference/): All CLI commands: compile, run (local/remote), test, login, logout, org, status, cancel, secrets, types, fixture, init, hook, endpoints, workflows, docs, admin
+- [Lifecycle hooks](https://docs.kici.dev/user/hooks/): SDK hook API for cancel, cleanup, success, failure, and step-level callbacks
+- [Lock file and workflow drift](https://docs.kici.dev/user/lock-file-and-drift/): Keep the lock file in sync with your workflow source and avoid drift
+- [Testing guide](https://docs.kici.dev/user/testing-guide/): Running remote test fixtures with kici run remote
+- [Workflow patterns](https://docs.kici.dev/user/workflow-patterns/): Common patterns: monorepo builds, conditional jobs, dynamic matrices, generic webhooks, scheduling
 
 ## Workflow features
 
-- [Concurrency groups](https://kici.dev/docs/user/concurrency/): Control parallel execution with auto-cancel and queue modes
-- [Dashboard](https://kici.dev/docs/user/dashboard/)
-- [Dynamic values](https://kici.dev/docs/user/dynamic-values/)
-- [Environment variables](https://kici.dev/docs/user/env-vars/): KICI_* environment variable reference for the CLI
-- [Environments](https://kici.dev/docs/user/environments/): Configure deployment environments with variables, secrets, and protection rules
-- [Event system](https://kici.dev/docs/user/events/): How KiCI's event model works -- event types, the registration model, event matching, and circuit breaker protection
-- [Global workflows](https://kici.dev/docs/user/global-workflows/): Cross-repo workflows that run on events from any repo in the same org
-- [Private npm registries](https://kici.dev/docs/user/private-registries/): Authenticate `npm install` against private registries (CodeArtifact, GitHub Packages, Verdaccio, …) from a workflow's `.kici/package.json`
-- [Secrets](https://kici.dev/docs/user/secrets/): How to access secrets in KiCI workflow steps
+- [Concurrency groups](https://docs.kici.dev/user/concurrency/): Control parallel execution with auto-cancel and queue modes
+- [Dashboard](https://docs.kici.dev/user/dashboard/)
+- [Dynamic values](https://docs.kici.dev/user/dynamic-values/)
+- [Environment variables](https://docs.kici.dev/user/env-vars/): KICI_* environment variable reference for the CLI
+- [Environments](https://docs.kici.dev/user/environments/): Configure deployment environments with variables, secrets, and protection rules
+- [Event system](https://docs.kici.dev/user/events/): How KiCI's event model works -- event types, the registration model, event matching, and circuit breaker protection
+- [Global workflows](https://docs.kici.dev/user/global-workflows/): Cross-repo workflows that run on events from any repo in the same org
+- [Private npm registries](https://docs.kici.dev/user/private-registries/): Authenticate `npm install` against private registries (CodeArtifact, GitHub Packages, Verdaccio, …) from a workflow's `.kici/package.json`
+- [Secrets](https://docs.kici.dev/user/secrets/): How to access secrets in KiCI workflow steps
 
 ## Providers
 
-- [GitHub App provider](https://kici.dev/docs/user/providers/github/): Connect KiCI to GitHub via a GitHub App — full Checks API, installation-token clones, and cross-org dispatch
-- [Universal-git provider](https://kici.dev/docs/user/providers/universal-git/): Connect Forgejo, Gitea, Gogs, GitLab, or plain GitHub via webhook + PAT or SSH deploy key
+- [GitHub App provider](https://docs.kici.dev/user/providers/github/): Connect KiCI to GitHub via a GitHub App — full Checks API, installation-token clones, and cross-org dispatch
+- [Universal-git provider](https://docs.kici.dev/user/providers/universal-git/): Connect Forgejo, Gitea, Gogs, GitLab, or plain GitHub via webhook + PAT or SSH deploy key
 
 ## Architecture overview
 
-- [Data flows](https://kici.dev/docs/architecture/data-flows/): End-to-end data flows through the KiCI three-tier architecture
-- [Design decisions](https://kici.dev/docs/architecture/design-decisions/): Why KiCI's architecture is shaped the way it is
-- [Architecture overview](https://kici.dev/docs/architecture/overview/): Three-tier relay model, package structure, and component responsibilities
+- [Data flows](https://docs.kici.dev/architecture/data-flows/): End-to-end data flows through the KiCI three-tier architecture
+- [Design decisions](https://docs.kici.dev/architecture/design-decisions/): Why KiCI's architecture is shaped the way it is
+- [Architecture overview](https://docs.kici.dev/architecture/overview/): Three-tier relay model, package structure, and component responsibilities

package/dist/local-executor/index.js

@@ -2,8 +2,8 @@ import "../chunk-gOLHoazu.js";
 import { discoverWorkflows, resolveKiciDir } from "../execution/executor.js";
 import "../execution/index.js";
 import { transformTriggers } from "../lockfile/generator.js";
-import { compileCommand } from "../commands/compile.js";
 import { executeDag, resolveJobFilter } from "./dag-scheduler.js";
+import { compileCommand } from "../commands/compile.js";
 import { loadLocalSecrets } from "./secret-loader.js";
 import { generateEventPayload } from "./payload-generator.js";
 import { executeResolvedJob, resolveJobs } from "./job-runner.js";
@@ -14,7 +14,7 @@ import { ConcurrencyKeyEvaluationError, acquireWorkflowLock } from "./workflow-l
 import pc from "picocolors";
 import { writeFile } from "node:fs/promises";
 import path from "node:path";
-import { logger } from "@kici-dev/shared";
+import { logger } from "@kici-dev/core";
 import { matchAllWorkflows } from "@kici-dev/engine";
 import os from "node:os";
 //#region src/local-executor/index.ts

package/dist/local-executor/job-runner.js

@@ -1,4 +1,5 @@
 import "../chunk-gOLHoazu.js";
+import { ensureTsLoaderHook } from "../execution/ts-loader.js";
 import { formatter } from "../test-runner/output-formatter.js";
 import { createStepContext } from "../test-runner/step-context.js";
 import { createRuleContext, evaluateRules as evaluateRulesWithFormatting } from "../test-runner/rule-evaluator.js";
@@ -21,7 +22,9 @@ import { applyIncludeExclude, expandMatrix, isDynamicJobFn, setJobOutputsMap, se
 */
 async function resolveSdkSetters(kiciDir) {
 	if (kiciDir) try {
-		const sdk = await import(pathToFileURL(path.join(kiciDir, "node_modules", "@kici-dev", "sdk", "dist", "index.js")).href);
+		const sdkUrl = pathToFileURL(path.join(kiciDir, "node_modules", "@kici-dev", "sdk", "dist", "index.js")).href;
+		ensureTsLoaderHook();
+		const sdk = await import(sdkUrl);
 		return {
 			setStepOutputsMap: sdk.setStepOutputsMap,
 			setStepRefMap: sdk.setStepRefMap,

package/dist/local-executor/output-streamer.js

@@ -1,6 +1,6 @@
 import "../chunk-gOLHoazu.js";
 import pc from "picocolors";
-import { logger } from "@kici-dev/shared";
+import { logger } from "@kici-dev/core";
 //#region src/local-executor/output-streamer.ts
 /**
 * Output formatting for local execution: tree summary, JSON, JUnit XML.

package/dist/local-executor/picker.js

@@ -2,7 +2,7 @@ import "../chunk-gOLHoazu.js";
 import { transformTriggers } from "../lockfile/generator.js";
 import { parseEventArg, triggerSummary, triggerToEventArg } from "../test-runner/event-types.js";
 import pc from "picocolors";
-import { logger } from "@kici-dev/shared";
+import { logger } from "@kici-dev/core";
 import { select } from "@inquirer/prompts";
 //#region src/local-executor/picker.ts
 /**

package/dist/lockfile/generator.js

@@ -5,11 +5,11 @@ import { resolveHashFiles } from "./hash-files.js";
 import { analyzePurity } from "./purity-analyzer.js";
 import { readFileSync } from "node:fs";
 import path from "node:path";
-import { execSync } from "node:child_process";
-import { sha256 } from "@kici-dev/shared";
 import { getDynamicJobGroup, isDynamicFunction, isDynamicGroupRef, isDynamicJobFn, isStaticArray, isStaticObject } from "@kici-dev/sdk";
-import { PackageManager, detectPackageManagerSync } from "@kici-dev/shared/package-manager";
+import { sha256 } from "@kici-dev/core";
+import { PackageManager, detectPackageManagerSync } from "@kici-dev/core/package-manager";
 import { validateResourceRequest } from "@kici-dev/engine";
+import { execSync } from "node:child_process";
 //#region src/lockfile/generator.ts
 /**
 * Detect git repository root by running `git rev-parse --show-toplevel`.

package/dist/lockfile/hasher.js

@@ -1,5 +1,5 @@
 import "../chunk-gOLHoazu.js";
-import { normalizeLineEndings, sha256 } from "@kici-dev/shared";
+import { normalizeLineEndings, sha256 } from "@kici-dev/core";
 //#region src/lockfile/hasher.ts
 /**
 * Compile schema version -- bump when compilation approach changes

package/dist/remote/client.js

@@ -1,5 +1,5 @@
 import "../chunk-gOLHoazu.js";
-import { toErrorMessage } from "@kici-dev/shared";
+import { toErrorMessage } from "@kici-dev/core";
 //#region src/remote/client.ts
 /**
 * REST client for communicating with the KiCI orchestrator.