@elevasis/sdk 1.15.0 → 1.16.0

package/dist/test-utils/index.js

@@ -6752,6 +6752,7 @@ createAdapter("acqDb", [
   "markProposalReviewed",
   "updateCloseLostReason",
   "updateFees",
+  "cacheInstantlyThreadIds",
   "transitionItem",
   "setContactNurture",
   "cancelSchedulesAndHitlByEmail",
@@ -24262,6 +24263,7 @@ var mockAcqDb = (overrides) => createMockAdapter(
     "markProposalReviewed",
     "updateCloseLostReason",
     "updateFees",
+    "cacheInstantlyThreadIds",
     "transitionItem",
     "setContactNurture",
     "cancelSchedulesAndHitlByEmail",

package/dist/types/worker/adapters/lead.d.ts

@@ -4,7 +4,7 @@
  * Typed wrapper over platform.call() for acquisition lead management.
  * Singleton export -- no credential needed (platform tool).
  *
- * 51 methods covering lists, companies, contacts, deals, list-stage updates, deal-sync, deal notes, deal tasks, enrichment, and social monitoring operations.
+ * 56 methods covering lists, companies, contacts, deals, list-stage updates, deal-sync, deal notes, deal tasks, enrichment, and social monitoring operations.
  * organizationId is injected server-side by the dispatcher -- never sent from the SDK.
  */
 import { type TypedAdapter } from './create-adapter.js';

package/dist/types/worker/platform.d.ts

@@ -5,14 +5,7 @@
  * from within worker threads. Communicates with the parent process via
  * postMessage() -- the parent dispatches to the real service layer.
  */
-/** Inbound tool-result from parent */
-interface ToolResultMessage {
-    type: 'tool-result';
-    id: string;
-    result?: unknown;
-    error?: string;
-    code?: string;
-}
+import type { ToolCallResponse } from '@repo/core/execution/engine/tools/messages';
 /** Inbound credential-result from parent */
 interface CredentialResultMessage {
     type: 'credential-result';
@@ -42,7 +35,7 @@ export declare class PlatformToolError extends Error {
  * Handle a tool-result message from the parent process.
  * Called from the parentPort.on('message') handler in index.ts.
  */
-export declare function handleToolResult(msg: ToolResultMessage): void;
+export declare function handleToolResult(msg: ToolCallResponse): void;
 /**
  * Handle a credential-result message from the parent process.
  * Called from the parentPort.on('message') handler in index.ts.

package/dist/worker/index.js

@@ -4998,6 +4998,7 @@ var acqDb = createAdapter("acqDb", [
   "markProposalReviewed",
   "updateCloseLostReason",
   "updateFees",
+  "cacheInstantlyThreadIds",
   "transitionItem",
   "setContactNurture",
   "cancelSchedulesAndHitlByEmail",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elevasis/sdk",
-  "version": "1.15.0",
+  "version": "1.16.0",
   "description": "SDK for building Elevasis organization resources",
   "type": "module",
   "bin": {
@@ -18,6 +18,10 @@
     "./test-utils": {
       "types": "./dist/test-utils/index.d.ts",
       "import": "./dist/test-utils/index.js"
+    },
+    "./node": {
+      "types": "./dist/node/index.d.ts",
+      "import": "./dist/node/index.js"
     }
   },
   "files": [
@@ -29,11 +33,14 @@
     "dist/types/worker/adapters/",
     "dist/test-utils/index.js",
     "dist/test-utils/index.d.ts",
+    "dist/node/",
     "dist/cli.cjs",
     "reference/"
   ],
   "dependencies": {
-    "esbuild": "^0.25.0"
+    "@mdx-js/mdx": "^3.1.1",
+    "esbuild": "^0.25.0",
+    "remark-gfm": "^4.0.1"
   },
   "peerDependencies": {
     "zod": "^4.1.0"
@@ -50,10 +57,12 @@
     "tsup": "^8.0.0",
     "typescript": "5.9.2",
     "zod": "^4.1.0",
-    "@repo/core": "0.15.0",
+    "@repo/core": "0.16.0",
+    "@repo/eslint-config": "0.0.0",
     "@repo/typescript-config": "0.0.0"
   },
   "scripts": {
+    "lint": "eslint src --max-warnings 0",
     "build": "node -e \"require('fs').rmSync('dist',{recursive:true,force:true})\" && tsc -p tsconfig.core-dts.json && tsc -p tsconfig.build.json && tsup && rollup -c rollup.dts.config.mjs && esbuild src/cli/index.ts --bundle --platform=node --outfile=dist/cli.cjs --format=cjs --external:esbuild --banner:js=\"#!/usr/bin/env node\" && node scripts/copy-reference-docs.mjs && node ../../scripts/monorepo/generate-reference-artifacts.js",
     "type-check": "tsc --noEmit",
     "check-types": "pnpm type-check",

package/reference/_navigation.md

@@ -2,7 +2,7 @@
 
 Auto-generated from the package reference manifests.
 
-Package entries indexed: 47.
+Package entries indexed: 54.
 
 ## @elevasis/core / Core
 
@@ -16,6 +16,12 @@ Package entries indexed: 47.
 | --- | --- | --- | --- |
 | Entities | `packages/core/src/business/README.md` | Published base entity contracts (Project, Milestone, Task, Deal, Company, Contact) generic over a metadata extension slot. | (not specified) |
 
+## @elevasis/core / Knowledge
+
+| Resource | Location | Description | When to Load |
+| --- | --- | --- | --- |
+| Knowledge | `packages/core/src/knowledge/README.md` | Published knowledge query layer: byFeature/byKind/byOwner/governs/governedBy queries, parsePath, and output formatters. | (not specified) |
+
 ## @elevasis/core / Organization Model
 
 | Resource | Location | Description | When to Load |
@@ -46,6 +52,19 @@ Package entries indexed: 47.
 | --- | --- | --- | --- |
 | Test Utils | `runtime.mdx` | Workflow runner, registry assertion, and typed adapter mocks for SDK consumers. | (not specified) |
 
+## @elevasis/sdk / Tooling
+
+| Resource | Location | Description | When to Load |
+| --- | --- | --- | --- |
+| Node Build Tooling | `cli.mdx` | Node-only build helpers: knowledge codegen and other fs/path/process utilities. Not browser-safe. | (not specified) |
+
+## @elevasis/ui / Build
+
+| Resource | Location | Description | When to Load |
+| --- | --- | --- | --- |
+| Vite | `packages/ui/src/knowledge/README.md` | Composite Vite plugin factory (elevasisVite) that bundles all @elevasis/ui Vite plugins into a single array for consumer vite.config.ts files. | (not specified) |
+| Vite Plugin Knowledge | `packages/ui/src/knowledge/README.md` | Vite plugin that regenerates the build-time knowledge MDX bodies and search index, with HMR support. | (not specified) |
+
 ## @elevasis/ui / Components
 
 | Resource | Location | Description | When to Load |
@@ -70,6 +89,7 @@ Package entries indexed: 47.
 | Features Monitoring Requests | `packages/ui/src/features/README.md` | Published submitted-requests list, detail, and triage surface for downstream shells. | (not specified) |
 | Features SEO | `packages/ui/src/features/README.md` | Published SEO feature surface for downstream shells. | (not specified) |
 | Features Settings | `packages/ui/src/features/README.md` | Published settings feature surface for downstream shells. | (not specified) |
+| Features Knowledge | `packages/ui/src/features/README.md` | Published knowledge feature manifest for downstream shells. | (not specified) |
 
 ## @elevasis/ui / Foundation
 
@@ -120,6 +140,8 @@ Package entries indexed: 47.
 | --- | --- | --- | --- |
 | Theme | `packages/ui/src/theme/README.md` | Published theme entry for downstream applications. | (not specified) |
 | Graph | `packages/ui/src/graph/README.md` | Published graph helper and visualization entry. | (not specified) |
+| Theme Presets | `packages/ui/src/theme/presets/README.md` | Re-exports the canonical THEME_PRESETS tuple, ThemePresetName union, and ThemePresetEnum Zod enum from @repo/core. Single source of truth for preset names across UI, schemas, and Zustand state. | (not specified) |
+| Knowledge | `packages/ui/src/knowledge/README.md` | Published knowledge browser primitives: Browser, Tree, NodeList, NodeView, SearchBar, MDX provider, and the generated KNOWLEDGE_BODIES map. | (not specified) |
 
 ---
 

package/reference/_reference-manifest.json

@@ -29,6 +29,20 @@
       "referencePath": "packages/core/src/business/README.md",
       "publishedExportPath": "./dist/business/entities-published.js"
     },
+    {
+      "packageName": "@elevasis/core",
+      "packageDir": "packages/core",
+      "subpath": "./knowledge",
+      "kind": "subpath",
+      "title": "Knowledge",
+      "description": "Published knowledge query layer: byFeature/byKind/byOwner/governs/governedBy queries, parsePath, and output formatters.",
+      "group": "Knowledge",
+      "order": 1,
+      "sourcePath": "packages/core/src/knowledge/index.ts",
+      "docPath": "packages/core/src/knowledge/README.md",
+      "referencePath": "packages/core/src/knowledge/README.md",
+      "publishedExportPath": "./dist/knowledge/index.js"
+    },
     {
       "packageName": "@elevasis/core",
       "packageDir": "packages/core",
@@ -99,6 +113,48 @@
       "referencePath": "runtime.mdx",
       "publishedExportPath": "./dist/test-utils/index.js"
     },
+    {
+      "packageName": "@elevasis/sdk",
+      "packageDir": "packages/sdk",
+      "subpath": "./node",
+      "kind": "subpath",
+      "title": "Node Build Tooling",
+      "description": "Node-only build helpers: knowledge codegen and other fs/path/process utilities. Not browser-safe.",
+      "group": "Tooling",
+      "order": 1,
+      "sourcePath": "packages/sdk/src/node/index.ts",
+      "docPath": "apps/docs/content/docs/sdk/cli.mdx",
+      "referencePath": "cli.mdx",
+      "publishedExportPath": "./dist/node/index.js"
+    },
+    {
+      "packageName": "@elevasis/ui",
+      "packageDir": "packages/ui",
+      "subpath": "./vite",
+      "kind": "subpath",
+      "title": "Vite",
+      "description": "Composite Vite plugin factory (elevasisVite) that bundles all @elevasis/ui Vite plugins into a single array for consumer vite.config.ts files.",
+      "group": "Build",
+      "order": 0,
+      "sourcePath": "packages/ui/src/vite/index.ts",
+      "docPath": "packages/ui/src/knowledge/README.md",
+      "referencePath": "packages/ui/src/knowledge/README.md",
+      "publishedExportPath": "./dist/vite/index.js"
+    },
+    {
+      "packageName": "@elevasis/ui",
+      "packageDir": "packages/ui",
+      "subpath": "./vite-plugin-knowledge",
+      "kind": "subpath",
+      "title": "Vite Plugin Knowledge",
+      "description": "Vite plugin that regenerates the build-time knowledge MDX bodies and search index, with HMR support.",
+      "group": "Build",
+      "order": 1,
+      "sourcePath": "packages/ui/src/vite-plugin-knowledge/index.ts",
+      "docPath": "packages/ui/src/knowledge/README.md",
+      "referencePath": "packages/ui/src/knowledge/README.md",
+      "publishedExportPath": "./dist/vite-plugin-knowledge/index.js"
+    },
     {
       "packageName": "@elevasis/ui",
       "packageDir": "packages/ui",
@@ -309,6 +365,20 @@
       "referencePath": "packages/ui/src/features/README.md",
       "publishedExportPath": "./dist/features/settings/index.js"
     },
+    {
+      "packageName": "@elevasis/ui",
+      "packageDir": "packages/ui",
+      "subpath": "./features/knowledge",
+      "kind": "subpath",
+      "title": "Features Knowledge",
+      "description": "Published knowledge feature manifest for downstream shells.",
+      "group": "Features",
+      "order": 11,
+      "sourcePath": "packages/ui/src/features/knowledge/index.ts",
+      "docPath": "packages/ui/src/features/README.md",
+      "referencePath": "packages/ui/src/features/README.md",
+      "publishedExportPath": "./dist/features/knowledge/index.js"
+    },
     {
       "packageName": "@elevasis/ui",
       "packageDir": "packages/ui",
@@ -658,6 +728,34 @@
       "docPath": "packages/ui/src/graph/README.md",
       "referencePath": "packages/ui/src/graph/README.md",
       "publishedExportPath": "./dist/graph/index.js"
+    },
+    {
+      "packageName": "@elevasis/ui",
+      "packageDir": "packages/ui",
+      "subpath": "./theme/presets",
+      "kind": "subpath",
+      "title": "Theme Presets",
+      "description": "Re-exports the canonical THEME_PRESETS tuple, ThemePresetName union, and ThemePresetEnum Zod enum from @repo/core. Single source of truth for preset names across UI, schemas, and Zustand state.",
+      "group": "Visual",
+      "order": 2,
+      "sourcePath": "packages/ui/src/theme/presets/index.ts",
+      "docPath": "packages/ui/src/theme/presets/README.md",
+      "referencePath": "packages/ui/src/theme/presets/README.md",
+      "publishedExportPath": "./dist/theme/presets/index.js"
+    },
+    {
+      "packageName": "@elevasis/ui",
+      "packageDir": "packages/ui",
+      "subpath": "./knowledge",
+      "kind": "subpath",
+      "title": "Knowledge",
+      "description": "Published knowledge browser primitives: Browser, Tree, NodeList, NodeView, SearchBar, MDX provider, and the generated KNOWLEDGE_BODIES map.",
+      "group": "Visual",
+      "order": 3,
+      "sourcePath": "packages/ui/src/knowledge/index.ts",
+      "docPath": "packages/ui/src/knowledge/README.md",
+      "referencePath": "packages/ui/src/knowledge/README.md",
+      "publishedExportPath": "./dist/knowledge/index.js"
     }
   ]
 }

package/reference/claude-config/rules/agent-start-here.md

@@ -6,6 +6,19 @@ description: Canonical first-read for agents entering the template scaffold -- p
 
 Read this file first when entering a freshly scaffolded project.
 
+## Project Profile
+
+Before doing anything else, check for `.claude/memory/profile.md`. It is created by `/tutorial` on first invocation and persists across sessions.
+
+If present, read it. The file declares which onboarding **track** is active -- `vibe-coder` (non-technical user, agent does the work) or `technical` (developer, code-first) -- and ships a tone block describing how to communicate.
+
+Apply the tone block to ALL agent output for the rest of the session, not just inside `/tutorial`:
+
+- **vibe-coder track:** never use technical vocabulary in user-facing dialogue (workflow -> automation, deploy -> make it live, schema -> "the information your automation needs"). Tool calls are made silently -- do not narrate slash commands, file paths, or build steps. The full swap table lives in `profile.md`.
+- **technical track:** code-first, current command surface, real file paths. The user reads diffs and stacktraces; do not over-explain.
+
+If the file does not exist, the user has not run `/tutorial` yet. Proceed normally and note that running `/tutorial` would establish a project tone for future sessions.
+
 ## First Action: Check Active Projects
 
 Before loading any docs for a new session, check whether the user's ask resumes or relates to an in-flight client project. Project context (milestones, tasks, resume notes) is DB-canonical -- agents and CLI read/write it through the `elevasis-sdk project:*` surface.

package/reference/claude-config/rules/organization-model.md

@@ -1,43 +1,43 @@
----
-description: Edits to the canonical organization model go through /configure
+---
+description: Edits to the canonical organization model go through /knowledge
 paths:
   - core/config/organization-model.ts
   - core/config/extensions/**/*.ts
----
-
-# Organization Model Edit Guide
-
-`foundations/config/organization-model.ts` is the single source of truth for this
-project's organizational identity -- it encodes customers, offerings, roles, goals,
-features, statuses, and resource mappings that agents, workflows, and the UI shell all
-consume at runtime.
-
-## Preferred Entry Point: `/configure`
-
-Direct edits to `organization-model.ts` are discouraged. Instead, use `/configure` (or
-`/configure <domain>`) to run the read → propose → confirm → write → validate ceremony:
-
-1. The skill reads the current model so proposals start from ground truth.
-2. It drafts only the specific block being changed, leaving everything else intact.
-3. The user confirms before any file is written.
-4. After writing, `pnpm -C operations check-types` runs and `OrganizationModelSchema.parse()`
-   is verified. On failure the file is rolled back automatically.
-
-Use `/configure <domain>` for targeted edits: `identity`, `customers`, `offerings`,
-`roles`, `goals`, `techStack`, `features`, or `labels`.
-
-## Runtime Validation
-
-The model is validated at startup via `resolveOrganizationModel()` followed by
-`OrganizationModelSchema.parse()`. Cross-reference checks (segment ID refs in offerings,
-role reporting lines, period ordering in goals) are runtime-only and not caught by tsc
-alone -- always let the ceremony run both checks before treating a change as complete.
-
-## Extension Files
-
-New Zod extension files under `foundations/config/extensions/` are Level B codify
-operations. Route these through `/configure <domain>` as well -- the skill gates Level B
-to explicit user confirmation before scaffolding a new `.ts` file.
-
-This is a soft guide, not a hard block. The ceremony exists to prevent silent schema
-drift and to keep the model's editorial history visible.
+---
+
+# Organization Model Edit Guide
+
+`foundations/config/organization-model.ts` is the single source of truth for this
+project's organizational identity -- it encodes customers, offerings, roles, goals,
+features, statuses, and resource mappings that agents, workflows, and the UI shell all
+consume at runtime.
+
+## Preferred Entry Point: `/knowledge`
+
+Direct edits to `organization-model.ts` are discouraged. Instead, use `/knowledge` (or
+`/knowledge <domain>`) to run the read → propose → confirm → write → validate ceremony:
+
+1. The skill reads the current model so proposals start from ground truth.
+2. It drafts only the specific block being changed, leaving everything else intact.
+3. The user confirms before any file is written.
+4. After writing, `pnpm -C operations check-types` runs and `OrganizationModelSchema.parse()`
+   is verified. On failure the file is rolled back automatically.
+
+Use `/knowledge <domain>` for targeted edits: `identity`, `customers`, `offerings`,
+`roles`, `goals`, `techStack`, `features`, or `labels`.
+
+## Runtime Validation
+
+The model is validated at startup via `resolveOrganizationModel()` followed by
+`OrganizationModelSchema.parse()`. Cross-reference checks (segment ID refs in offerings,
+role reporting lines, period ordering in goals) are runtime-only and not caught by tsc
+alone -- always let the ceremony run both checks before treating a change as complete.
+
+## Extension Files
+
+New Zod extension files under `foundations/config/extensions/` are Level B codify
+operations. Route these through `/knowledge <domain>` as well -- the skill gates Level B
+to explicit user confirmation before scaffolding a new `.ts` file.
+
+This is a soft guide, not a hard block. The ceremony exists to prevent silent schema
+drift and to keep the model's editorial history visible.

package/reference/claude-config/rules/organization-os.md

@@ -42,7 +42,7 @@ Full Organization OS documentation ships with the SDK and is available locally a
 All paths under `node_modules/@elevasis/sdk/reference/scaffold/`:
 
 - `node_modules/@elevasis/sdk/reference/scaffold/index.mdx` -- scaffold root and navigation
-- `node_modules/@elevasis/sdk/reference/scaffold/core/organization-model.mdx` -- semantic contract, all 14 domains, adapter authoring, validation gate, `/configure` entry point
+- `node_modules/@elevasis/sdk/reference/scaffold/core/organization-model.mdx` -- semantic contract, all 14 domains, adapter authoring, validation gate, `/knowledge` entry point
 - `node_modules/@elevasis/sdk/reference/scaffold/core/organization-graph.mdx` -- graph derivation, node/edge taxonomy, lenses
 - `node_modules/@elevasis/sdk/reference/scaffold/ui/feature-shell.mdx` -- FeatureModule manifest, provider runtime
 - `node_modules/@elevasis/sdk/reference/scaffold/ui/composition-extensibility.mdx` -- layout primitives, router abstraction
@@ -77,35 +77,35 @@ All paths under `node_modules/@elevasis/sdk/reference/scaffold/`:
 
 ## When Working with Organization OS
 
-- **Changing org model (structural reality):** Use `/configure` as the entry point. Direct edits to `foundations/config/organization-model.ts` are discouraged -- `/configure` runs the read → propose → confirm → write → validate ceremony. Run `/configure` for the full layered flow or `/configure \<domain>` for a targeted domain.
+- **Changing org model (structural reality):** Use `/knowledge` as the entry point. Direct edits to `foundations/config/organization-model.ts` are discouraged -- `/knowledge` runs the read → propose → confirm → write → validate ceremony. Run `/knowledge` for the full layered flow or `/knowledge \<domain>` for a targeted domain.
 - **Building or extending CRM:** Start with `node_modules/@elevasis/sdk/reference/scaffold/recipes/extend-crm.md`. CRM spans Organization OS sales semantics, shared UI primitives, deal hooks, workflow adapters, and generated contracts.
 - **Building or extending lead gen:** Start with `node_modules/@elevasis/sdk/reference/scaffold/recipes/extend-lead-gen.md`. Lead gen spans Organization OS prospecting semantics, shared UI primitives, list/member hooks, artifact hooks, workflow adapters, and generated contracts.
 - **Customizing CRM deal actions:** Follow `node_modules/@elevasis/sdk/reference/scaffold/recipes/customize-crm-actions.md`. Do not add `sales.actions` to the org model; the v1 server-side override surface is intentionally deferred.
-- **Adding a feature:** Follow `node_modules/@elevasis/sdk/reference/scaffold/recipes/add-a-feature.md`. For toggling an existing feature, use `/configure features`.
+- **Adding a feature:** Follow `node_modules/@elevasis/sdk/reference/scaffold/recipes/add-a-feature.md`. For toggling an existing feature, use `/knowledge features`.
 - **Adding a resource:** Follow `node_modules/@elevasis/sdk/reference/scaffold/recipes/add-a-resource.md`.
 - **Extending entities:** Start with `foundations/types/entities.ts` for the demo extension pattern. Base shapes come from `@elevasis/core/entities`.
 - **Authoring a workflow that takes a Project/Deal/etc.:** Reference entity types from `foundations/types/entities.ts` in the input schema -- do not redeclare them.
 - **Understanding contracts:** Check `node_modules/@elevasis/sdk/reference/scaffold/reference/contracts.md` for current type shapes.
 - **Debugging sync issues:** Check `node_modules/@elevasis/sdk/reference/scaffold/operations/propagation-pipeline.md` for the verification pipeline.
 
-## `/configure` -- Org Model QA Entry Point
+## `/knowledge` -- Org Model QA Entry Point
 
-`/configure` is the recurring, safe-to-re-run org model editor for this project. It is a skill (not a command) at `.claude/skills/configure/SKILL.md`.
+`/knowledge` is the recurring, safe-to-re-run org model editor for this project. It is a skill (not a command) at `.claude/skills/knowledge/SKILL.md`.
 
 **Usage:**
 
-- `/configure` -- layered flow: identity → customers → offerings → roles → goals → techStack
-- `/configure identity` -- legal identity, mission/vision, industry, geography, timezone
-- `/configure customers` -- customer segments with jobs-to-be-done, pains, gains, firmographics
-- `/configure offerings` -- products and services with pricing model and segment references
-- `/configure roles` -- role chart with responsibilities, reporting lines, and holders
-- `/configure goals` -- organizational goals with period and measurable outcomes
-- `/configure techStack` -- external-SaaS integration metadata on resource mappings
-- `/configure features` -- enable, disable, or add features
-- `/configure labels` -- edit display labels on enum entries (statuses, stages)
+- `/knowledge` -- layered flow: identity → customers → offerings → roles → goals → techStack
+- `/knowledge identity` -- legal identity, mission/vision, industry, geography, timezone
+- `/knowledge customers` -- customer segments with jobs-to-be-done, pains, gains, firmographics
+- `/knowledge offerings` -- products and services with pricing model and segment references
+- `/knowledge roles` -- role chart with responsibilities, reporting lines, and holders
+- `/knowledge goals` -- organizational goals with period and measurable outcomes
+- `/knowledge techStack` -- external-SaaS integration metadata on resource mappings
+- `/knowledge features` -- enable, disable, or add features
+- `/knowledge labels` -- edit display labels on enum entries (statuses, stages)
 
 Every write is gated: `resolveOrganizationModel()` must succeed (Zod cross-refs pass) and `pnpm -C operations check-types` must pass. On failure the change is rolled back.
 
-**Distinction from `/setup`:** `/setup` is first-time bootstrap only. After bootstrap it delegates here. `/configure` is idempotent and safe to re-run at any time.
+**Distinction from `/setup`:** `/setup` is first-time bootstrap only. After bootstrap it delegates here. `/knowledge` is idempotent and safe to re-run at any time.
 
-The ambient vibe layer (`.claude/rules/vibe.md`) automatically detects Codify intent in plain language and delegates to `/configure`. Power users can invoke `/configure` directly to bypass the ambient layer entirely.
+The ambient vibe layer (`.claude/rules/vibe.md`) automatically detects Codify intent in plain language and delegates to `/knowledge`. Power users can invoke `/knowledge` directly to bypass the ambient layer entirely.

package/reference/claude-config/rules/ui.md

@@ -104,13 +104,9 @@ For real-time updates, feature surfaces use the local singleton wrapper:
 import { sseConnectionManager } from '@/lib/sse/SSEConnectionManager'
 ```
 
-**Required env vars:**
+**WorkOS config:**
 
-```bash
-VITE_WORKOS_CLIENT_ID=client_...
-VITE_WORKOS_REDIRECT_URI=http://localhost:4300/auth-redirect
-VITE_WORKOS_SIGNOUT_URI=http://localhost:4300/login
-```
+WorkOS `clientId`, `redirectUri`, and `signoutUri` are hardcoded in `ui/src/config/workos.ts` -- no UI env vars are required to run the template. Edit that file if a fork needs a different WorkOS client. The dev server runs on port `4300` with Vite `strictPort: true`, so a second `pnpm -C ui dev` on the same machine fails fast instead of drifting.
 
 The API URL is centralized in `ui/src/lib/constants/api.ts`. In the current template it is hard-coded to `https://api.elevasis.io`, so if the bootstrap is repointed to another API target, that file is the source of truth.
 

package/reference/claude-config/rules/vibe.md

@@ -1,5 +1,5 @@
 ---
-description: Ambient intent classifier -- routes natural-language input to 7 intent buckets without a slash command; Codify and Toggle delegate to /configure
+description: Ambient intent classifier -- routes natural-language input to 7 intent buckets without a slash command; Codify and Toggle delegate to /knowledge
 paths:
   - "**/*"
 ---
@@ -112,12 +112,12 @@ The user describes organizational reality that is not yet expressed in the model
 | "We track deal stage as discovery, scoping, proposal, closed"                    | Describes custom CRM stages that should replace defaults |
 | "Add a project type called 'retainer' with monthly billing and a contract field" | Explicit request to add a new entity extension           |
 
-**Agent action:** delegate immediately to `/configure`. Do not attempt the ceremony yourself. Invoke with the relevant domain: `/configure crm` for deal/contact changes, `/configure projects` for project types, `/configure features` for feature toggles. Plain-language summary of what was detected is acceptable before delegating, but the actual draft-confirm-write ceremony belongs to `/configure`.
+**Agent action:** delegate immediately to `/knowledge`. Do not attempt the ceremony yourself. Invoke with the relevant domain: `/knowledge crm` for deal/contact changes, `/knowledge projects` for project types, `/knowledge features` for feature toggles. Plain-language summary of what was detected is acceptable before delegating, but the actual draft-confirm-write ceremony belongs to `/knowledge`.
 
-This routing applies to both codify levels (decision #21 -- Codify ceremony delegated to `/configure`):
+This routing applies to both codify levels (decision #21 -- Codify ceremony delegated to `/knowledge`):
 
-- **Level A** (config-only edits to `organization-model.ts`, feature toggles, label renames): delegate to `/configure <domain>` immediately.
-- **Level B** (new Zod extension files in `foundations/config/extensions/`): also delegate to `/configure <domain>`; `/configure` gates Level B to explicit user asks before scaffolding a new TS file.
+- **Level A** (config-only edits to `organization-model.ts`, feature toggles, label renames): delegate to `/knowledge <domain>` immediately.
+- **Level B** (new Zod extension files in `foundations/config/extensions/`): also delegate to `/knowledge <domain>`; `/knowledge` gates Level B to explicit user asks before scaffolding a new TS file.
 
 Vibe detects the intent and delegates in both cases. It does not run either pipeline itself.
 
@@ -127,7 +127,7 @@ For "build/extend lead gen" / "campaign creator" / "outbound list state" asks, c
 
 For "add a custom CRM action" / "Send Quote button" asks, classify as Codify, then read `node_modules/@elevasis/sdk/reference/scaffold/recipes/customize-crm-actions.md` before editing. Start with the shared `crmActions` provider path for action visibility, labels, ordering, and render-time configuration. In v1, platform-known/default action endpoint behavior is server-constrained; use project-owned UI that calls the workflow directly when a custom key sits outside that server-dispatched set.
 
-Heuristics for when to propose codification (passed to `/configure` as context):
+Heuristics for when to propose codification (passed to `/knowledge` as context):
 
 - First mention of a new attribute: note to `resume_context`, do not propose yet
 - Second mention OR explicit declaration ("we're ecom"): propose extension
@@ -148,7 +148,7 @@ The user wants to enable or disable a feature.
 | "Disable monitoring for now"    | "Disable" + feature reference                 |
 | "We don't use SEO, turn it off" | Declarative + "turn it off" = feature disable |
 
-**Agent action:** delegate to `/configure features`. The ceremony (confirm + edit `foundations/config/organization-model.ts` + typecheck) belongs to `/configure`, not to the ambient rule.
+**Agent action:** delegate to `/knowledge features`. The ceremony (confirm + edit `foundations/config/organization-model.ts` + typecheck) belongs to `/knowledge`, not to the ambient rule.
 
 ## Quick Reference Table
 
@@ -159,8 +159,8 @@ The user wants to enable or disable a feature.
 | Describe   | "what is", "tell me about", "explain", "where am I"             | Agent -- narrate from org model labels     |
 | Transition | "done", "stuck", "blocked", "finished", "complete"              | Agent -- confirm + `project:task:save`     |
 | Navigate   | "focus on", "switch to", "back to", "look at"                   | Agent -- update scope + narrate            |
-| Codify     | "we are X", "we track Y", repeated attribute, "add type/field"  | Delegate to `/configure \<domain>`         |
-| Toggle     | "enable", "disable", "turn on/off" + feature                    | Delegate to `/configure features`          |
+| Codify     | "we are X", "we track Y", repeated attribute, "add type/field"  | Delegate to `/knowledge \<domain>`         |
+| Toggle     | "enable", "disable", "turn on/off" + feature                    | Delegate to `/knowledge features`          |
 
 ## Source of Truth for Plain Language
 
@@ -194,9 +194,9 @@ Override per project in `foundations/config/organization-model.ts` under `vibe.c
 
 This rule covers Phase 1 of the vibe layer rollout. The layers the ambient classifier can narrate and codify in Phase 1 are:
 
-- Layer 1 (Model): narrate schema shape, propose codification edits via `/configure`
-- Layer 4 (Features): describe which features are on/off, propose enabling one via `/configure`
-- Layer 7 (Foundations): explain and edit `organization-model.ts` and `extensions/` via `/configure`
+- Layer 1 (Model): narrate schema shape, propose codification edits via `/knowledge`
+- Layer 4 (Features): describe which features are on/off, propose enabling one via `/knowledge`
+- Layer 7 (Foundations): explain and edit `organization-model.ts` and `extensions/` via `/knowledge`
 
 Layers 2 (Public API), 3 (UI Shell Runtime), 5 (Toolkit), and 6 (Graph) require runtime read APIs that are not yet available. Do not attempt to narrate or classify against those layers in Phase 1. If the user's input clearly references one of those layers, acknowledge the scope and explain that full support arrives in a later phase.
 
@@ -204,5 +204,5 @@ Layers 2 (Public API), 3 (UI Shell Runtime), 5 (Toolkit), and 6 (Graph) require
 
 - Vibe is not a slash command. There is no `/vibe` invocation (decision #19 -- ambient rule, not a skill or command).
 - Vibe is not a skill. It lives in this rule file + CLAUDE.md + the PreToolUse hook -- not in `.claude/skills/`.
-- Vibe does not own the codify ceremony. `/configure` owns draft, confirm, write, and typecheck for both Level A and Level B codify pipelines (decision #21 -- Codify ceremony delegated to `/configure`). Vibe detects intent and hands off.
+- Vibe does not own the codify ceremony. `/knowledge` owns draft, confirm, write, and typecheck for both Level A and Level B codify pipelines (decision #21 -- Codify ceremony delegated to `/knowledge`). Vibe detects intent and hands off.
 - Vibe is not active in the monorepo. If working inside the monorepo (not an `external/` project), this ambient routing does not apply.