@elevasis/sdk 1.8.0 → 1.8.1

package/dist/cli.cjs

@@ -40520,7 +40520,7 @@ function wrapAction(commandName, fn) {
 // package.json
 var package_default = {
   name: "@elevasis/sdk",
-  version: "1.8.0",
+  version: "1.8.1",
   description: "SDK for building Elevasis organization resources",
   type: "module",
   bin: {
@@ -42293,7 +42293,7 @@ function registerTaskGet(program3) {
   program3.command("project:task:get <id>").description("Get a task by ID\n  Example: elevasis-sdk project:task:get <uuid>").option("--api-url <url>", "API base URL").option("--pretty", "Render human-readable output instead of raw JSON").action(
     wrapAction("project:task:get", async (id, options) => {
       const apiUrl = resolveApiUrl(options.apiUrl);
-      const result = await apiGet(`/api/external/tasks/${id}`, apiUrl);
+      const result = await apiGet(`/api/external/project-tasks/${id}`, apiUrl);
       if (options.pretty) {
         const t = result.task;
         console.log(source_default.cyan(`
@@ -42423,7 +42423,7 @@ function registerTaskResume(program3) {
   ).option("--api-url <url>", "API base URL").option("--pretty", "Render a human-readable resume briefing instead of raw JSON").action(
     wrapAction("project:task:resume", async (id, options) => {
       const apiUrl = resolveApiUrl(options.apiUrl);
-      const result = await apiGet(`/api/external/tasks/${id}`, apiUrl);
+      const result = await apiGet(`/api/external/project-tasks/${id}`, apiUrl);
       const task = result.task;
       const ctx = task.resume_context ?? {};
       if (options.pretty) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elevasis/sdk",
-  "version": "1.8.0",
+  "version": "1.8.1",
   "description": "SDK for building Elevasis organization resources",
   "type": "module",
   "bin": {

package/reference/claude-config/logs/scaffold-registry-reminder.log

@@ -15,3 +15,20 @@
 [2026-04-21T02:40:59.696Z] SKIP — registry not found (pre-SDK-delivery)
 [2026-04-21T02:46:47.986Z] SKIP — registry not found (pre-SDK-delivery)
 [2026-04-21T02:46:54.532Z] SKIP — registry not found (pre-SDK-delivery)
+[2026-04-21T07:44:32.528Z] SKIP — registry not found (pre-SDK-delivery)
+[2026-04-21T07:52:53.483Z] SKIP — registry not found (pre-SDK-delivery)
+[2026-04-21T07:54:29.656Z] SKIP — registry not found (pre-SDK-delivery)
+[2026-04-21T07:54:33.615Z] SKIP — registry not found (pre-SDK-delivery)
+[2026-04-21T07:57:28.696Z] SKIP — registry not found (pre-SDK-delivery)
+[2026-04-21T08:00:48.300Z] SKIP — registry not found (pre-SDK-delivery)
+[2026-04-21T08:00:49.082Z] SKIP — registry not found (pre-SDK-delivery)
+[2026-04-21T08:00:50.494Z] SKIP — registry not found (pre-SDK-delivery)
+[2026-04-21T08:00:56.735Z] SKIP — registry not found (pre-SDK-delivery)
+[2026-04-21T08:00:58.798Z] SKIP — registry not found (pre-SDK-delivery)
+[2026-04-21T08:01:07.662Z] SKIP — registry not found (pre-SDK-delivery)
+[2026-04-21T08:01:19.062Z] SKIP — registry not found (pre-SDK-delivery)
+[2026-04-21T08:01:24.353Z] SKIP — registry not found (pre-SDK-delivery)
+[2026-04-21T08:01:42.662Z] SKIP — registry not found (pre-SDK-delivery)
+[2026-04-21T08:12:30.121Z] SKIP — registry not found (pre-SDK-delivery)
+[2026-04-21T08:14:55.475Z] SKIP — registry not found (pre-SDK-delivery)
+[2026-04-21T08:17:01.426Z] SKIP — registry not found (pre-SDK-delivery)

package/reference/claude-config/skills/configure/operations/features.md

@@ -11,10 +11,10 @@ This operation handles both toggling existing features and introducing custom fe
 
 ## Background: Level A vs Level B
 
-- **Level A (config-only edit):** The feature exists in the platform defaults
-  (`packages/core/src/organization-model/defaults.ts`). The adapter in
-  `foundations/config/organization-model.ts` overrides its `enabled` flag or adjusts metadata.
-  No new TypeScript files needed.
+- **Level A (config-only edit):** The feature exists in the platform defaults (see
+  `node_modules/@elevasis/sdk/reference/scaffold/reference/contracts.md` for the default feature
+  set). The adapter in `foundations/config/organization-model.ts` overrides its `enabled` flag or
+  adjusts metadata. No new TypeScript files needed.
 
 - **Level B (new extension file):** The feature does not exist in platform defaults. A new
   feature ID and manifest need to be declared. This requires a new TypeScript file under
@@ -23,7 +23,8 @@ This operation handles both toggling existing features and introducing custom fe
 
 ## Schema reference
 
-Source: `packages/core/src/organization-model/domains/features.ts`
+Source: `node_modules/@elevasis/core/organization-model` (published types) or
+`node_modules/@elevasis/sdk/reference/scaffold/reference/contracts.md` (auto-generated shapes)
 
 ```typescript
 FeatureSchema = z.object({
@@ -40,7 +41,7 @@ FeatureSchema = z.object({
 })
 ```
 
-Platform default feature IDs (from `packages/core/src/organization-model/contracts.ts`):
+Platform default feature IDs (from `node_modules/@elevasis/sdk/reference/scaffold/reference/contracts.md`):
 `crm`, `lead-gen`, `projects`, `operations`, `monitoring`, `settings`, `seo`
 
 Where this lands in the adapter: `foundations/config/organization-model.ts` under the `features`
@@ -54,8 +55,8 @@ merge), so the adapter must redeclare all features it wants to override.
 ### Step 1: Read current state
 
 Read `foundations/config/organization-model.ts` and extract the current `features` array from the
-adapter. Also read `packages/core/src/organization-model/defaults.ts` to see what the platform
-defaults look like.
+adapter. Also read `node_modules/@elevasis/sdk/reference/scaffold/reference/contracts.md` to see
+what the platform defaults look like.
 
 Present a combined view:
 

package/reference/claude-config/skills/deploy/SKILL.md

@@ -132,7 +132,7 @@ After a successful push, mark any linked project task as `submitted`. This is a
 2. **Fire the transition** (only when a single confident task ID is resolved):
 
    ```bash
-   pnpm -C operations exec elevasis-sdk project:task:update <task-id> --status submitted
+   pnpm elevasis-sdk project:task:update <task-id> --status submitted
    ```
 
 3. **Failure handling.** If the CLI call errors, no task ID can be resolved, or the user declines, emit a single warning line and continue:

package/reference/claude-config/skills/elevasis/SKILL.md

@@ -40,7 +40,7 @@ For dev vs prod targeting:
 Validate all resource definitions (schemas, contracts, config):
 
 ```bash
-pnpm -C operations exec elevasis-sdk check
+pnpm elevasis-sdk check
 ```
 
 Reports: resource count, validation errors, schema serialization warnings. Exit code 0 = pass.
@@ -50,7 +50,7 @@ Reports: resource count, validation errors, schema serialization warnings. Exit
 Bundle and deploy resources to the Elevasis platform.
 
 ```bash
-pnpm -C operations exec elevasis-sdk deploy [--prod]
+pnpm elevasis-sdk deploy [--prod]
 ```
 
 Replace `[--prod]` with `--prod` when targeting production.
@@ -68,10 +68,10 @@ Deploy replaces the previous active deployment. Resources become executable imme
 **Always run before executing.** Shows resource metadata, input/output schemas, and step chain:
 
 ```bash
-pnpm -C operations exec elevasis-sdk describe <resourceId>
+pnpm elevasis-sdk describe <resourceId>
 
 # JSON output for programmatic use
-pnpm -C operations exec elevasis-sdk describe <resourceId> --json
+pnpm elevasis-sdk describe <resourceId> --json
 ```
 
 Output includes: type, name, version, status, domains, input schema (required/optional fields with types), output schema, step definitions with entry point and routing.
@@ -82,14 +82,14 @@ Run a deployed resource. **Always `describe` first to see the input schema.**
 
 ```bash
 # Simple input (inline JSON)
-pnpm -C operations exec elevasis-sdk exec <resourceId> -i '{"key": "value"}'
+pnpm elevasis-sdk exec <resourceId> -i '{"key": "value"}'
 
 # Complex input (temp file -- PREFERRED for non-trivial payloads)
 # Write input to a temp file first, then reference it with -f
-pnpm -C operations exec elevasis-sdk exec <resourceId> -f .tmp-input.json
+pnpm elevasis-sdk exec <resourceId> -f .tmp-input.json
 
 # Async execution (for long-running workflows -- polls until complete)
-pnpm -C operations exec elevasis-sdk exec <resourceId> -f .tmp-input.json --async
+pnpm elevasis-sdk exec <resourceId> -f .tmp-input.json --async
 ```
 
 **When to use `-f` (file input):**
@@ -118,10 +118,10 @@ pnpm -C operations exec elevasis-sdk exec <resourceId> -f .tmp-input.json --asyn
 View all deployed resources:
 
 ```bash
-pnpm -C operations exec elevasis-sdk resources
+pnpm elevasis-sdk resources
 
 # JSON output
-pnpm -C operations exec elevasis-sdk resources --json
+pnpm elevasis-sdk resources --json
 ```
 
 Shows: resource ID, type (workflow/agent), name, description, status.
@@ -132,19 +132,19 @@ View past executions for a resource:
 
 ```bash
 # List recent executions (default: last 50)
-pnpm -C operations exec elevasis-sdk executions <resourceId>
+pnpm elevasis-sdk executions <resourceId>
 
 # Filter by status
-pnpm -C operations exec elevasis-sdk executions <resourceId> --status failed --limit 10
+pnpm elevasis-sdk executions <resourceId> --status failed --limit 10
 
 # View specific execution (full detail with logs)
-pnpm -C operations exec elevasis-sdk execution <resourceId> <executionId>
+pnpm elevasis-sdk execution <resourceId> <executionId>
 
 # Logs only (skip metadata)
-pnpm -C operations exec elevasis-sdk execution <resourceId> <executionId> --logs-only
+pnpm elevasis-sdk execution <resourceId> <executionId> --logs-only
 
 # Include input and result data
-pnpm -C operations exec elevasis-sdk execution <resourceId> <executionId> --input --result
+pnpm elevasis-sdk execution <resourceId> <executionId> --input --result
 ```
 
 **`executions` flags:** `--limit <n>` (default 50), `--status running|completed|failed`, `--json`
@@ -158,7 +158,7 @@ Execution detail shows: status, start/end times, duration, input, result, error
 View deployment history:
 
 ```bash
-pnpm -C operations exec elevasis-sdk deployments
+pnpm elevasis-sdk deployments
 ```
 
 Shows: deployment ID, SDK version, status (active/deploying/failed/stopped), created timestamp.
@@ -169,19 +169,19 @@ Manage integration credentials (API keys, webhook secrets):
 
 ```bash
 # List credentials (metadata only, secrets not exposed)
-pnpm -C operations exec elevasis-sdk creds list
+pnpm elevasis-sdk creds list
 
 # Create a credential
-pnpm -C operations exec elevasis-sdk creds create --name my-api-key --type api-key --value '{"apiKey":"sk-..."}'
+pnpm elevasis-sdk creds create --name my-api-key --type api-key --value '{"apiKey":"sk-..."}'
 
 # Update a credential value
-pnpm -C operations exec elevasis-sdk creds update my-api-key --value '{"apiKey":"new-key"}'
+pnpm elevasis-sdk creds update my-api-key --value '{"apiKey":"new-key"}'
 
 # Rename a credential
-pnpm -C operations exec elevasis-sdk creds rename old-name --to new-name
+pnpm elevasis-sdk creds rename old-name --to new-name
 
 # Delete a credential
-pnpm -C operations exec elevasis-sdk creds delete my-api-key --force
+pnpm elevasis-sdk creds delete my-api-key --force
 ```
 
 Credential names: lowercase, digits, hyphens only (`^[a-z0-9]+(-[a-z0-9]+)*$`). Types: `api-key`, `webhook-secret`.
@@ -192,10 +192,10 @@ Rename a resource ID across all platform tables:
 
 ```bash
 # Dry run (preview only)
-pnpm -C operations exec elevasis-sdk rename old-id --to new-id
+pnpm elevasis-sdk rename old-id --to new-id
 
 # Apply rename
-pnpm -C operations exec elevasis-sdk rename old-id --to new-id --execute
+pnpm elevasis-sdk rename old-id --to new-id --execute
 ```
 
 Always dry-run first to see affected tables and row counts.
@@ -206,10 +206,10 @@ Mark execution errors as resolved:
 
 ```bash
 # Resolve a specific error
-pnpm -C operations exec elevasis-sdk error resolve <errorId>
+pnpm elevasis-sdk error resolve <errorId>
 
 # Resolve all errors for an execution
-pnpm -C operations exec elevasis-sdk error resolve-execution <executionId>
+pnpm elevasis-sdk error resolve-execution <executionId>
 ```
 
 ## Standard Workflow

package/reference/claude-config/skills/project/SKILL.md

@@ -35,6 +35,38 @@ allowed-tools: Bash, Read, Write, Edit, Glob, Grep
 - `/project checklist <client> "<milestone>"` — View checklist for a milestone.
 - `/project delete <client>` — Delete project (cascades milestones, tasks, notes).
 
+---
+
+## Ambient Vibe Integration
+
+This skill is the landing point for three of the seven vibe intent types. Agents arriving from the ambient layer should behave identically to a direct invocation — vibe is a classifier, not a different code path.
+
+| Vibe intent | What vibe detected | What to do here |
+|---|---|---|
+| **Capture** | "add a task", "remember to", "track this" | Draft the task/note, confirm with user, then `project:task:create` or `project:note:create` |
+| **Transition** | "done", "stuck", "blocked", "finished" | Resolve current task from session context, confirm status, then `project:task:update --status <new>` |
+| **Navigate** | "focus on", "switch to", "back to" | Resolve target via `project:resolve <query>` or `project:work <query>`, update scope, narrate new context |
+
+**The full continuity loop** — how work flows across sessions:
+
+```
+vibe (Capture) → /project task:create → task in DB
+                         ↓
+                    work happens
+                         ↓
+              /save → project:task:save → prj_tasks.resume_context
+                         ↓
+              next session: /project work <query>
+                         ↓
+              project:work → resume brief (current state + next steps)
+                         ↓
+              agent picks up exactly where it left off
+```
+
+When a session begins with an ambiguous opening, check `project:work` before asking the user to re-explain. The resume brief is the canonical continuity payload — trust it.
+
+---
+
 ## Prerequisites
 
 **Run from the project root** (the directory containing `.elevasis`). Before issuing any other commands, run:

package/reference/claude-config/skills/save/SKILL.md

@@ -19,7 +19,7 @@ Auto-manage project documentation from conversation context, and fan out convers
 
 Before doing anything else, determine the active project / task:
 
-1. Look for an active task-doc frontmatter in the current conversation or the most recently edited file under `docs/`. Expected frontmatter:
+1. Look for an active task-doc frontmatter in the current conversation or the most recently edited file. Expected frontmatter:
 
    ```yaml
    ---
@@ -56,7 +56,7 @@ Review the current conversation to identify:
 
 ### Step 3: Update Knowledge Docs
 
-Scan `docs/` for unindexed or stale knowledge docs and draft creates / updates / moves. All edits are on knowledge/architecture/feature docs -- NOT on task resume state (that flows to the DB in Step 4).
+Scan for unindexed or stale knowledge docs and draft creates / updates / moves. This template does not have a `docs/` tree — look for any local knowledge files (`.claude/rules/`, `operations/src/README.md`, `foundations/`, or project-specific docs the user has created). All edits are on knowledge/architecture/feature docs -- NOT on task resume state (that flows to the DB in Step 4).
 
 Determine what needs to happen:
 
@@ -155,7 +155,7 @@ If no signal rises to note-worthy, skip this step entirely. Do not create filler
 Run this ONLY when Step 5 created a `blocker` note AND Step 1 resolved a task ID. It's the second half of the "I'm stuck" fanout: the note captures the why, this call flips the task's lifecycle state so it surfaces as blocked in portfolio views.
 
 ```bash
-pnpm -C operations exec elevasis-sdk project:task:update <task-uuid> --status blocked
+pnpm elevasis-sdk project:task:update <task-uuid> --status blocked
 ```
 
 Rules:

package/reference/scaffold/reference/contracts.md

@@ -1,4 +1,4 @@
-<!-- Auto-generated on 2026-04-21T05:52:18.229Z by scripts/monorepo/generate-scaffold-contracts.js -->
+<!-- Auto-generated on 2026-04-21T08:23:05.375Z by scripts/monorepo/generate-scaffold-contracts.js -->
 ---
 title: Reference Contracts
 description: Auto-generated TypeScript contracts for SDK consumers. Do not edit manually.