@elevasis/sdk 0.5.6 → 0.5.8

package/dist/cli.cjs

@@ -43491,6 +43491,21 @@ var ResourceRegistry = class {
     }
     return false;
   }
+  /**
+   * Get the remote config for any resource in an organization.
+   * Used when the specific resource ID is unknown (e.g., to clean up a
+   * temp file before unregistering an org -- all resources share one config).
+   *
+   * @param orgName - Organization name
+   * @returns Remote config or null if org has no remote resources
+   */
+  getAnyRemoteConfig(orgName) {
+    const prefix = `${orgName}/`;
+    for (const [key, config3] of this.remoteResources) {
+      if (key.startsWith(prefix)) return config3;
+    }
+    return null;
+  }
   // ============================================================================
   // Resource Manifest Accessors
   // ============================================================================
@@ -43708,17 +43723,17 @@ function resolveEnvironment(prod) {
 }
 function resolveApiKey(prod) {
   if (!prod && process.env.NODE_ENV === "development") {
-    return process.env.ELEVASIS_API_KEY_DEV ?? process.env.ELEVASIS_API_KEY ?? "";
+    return process.env.ELEVASIS_PLATFORM_KEY_DEV ?? process.env.ELEVASIS_PLATFORM_KEY ?? "";
   }
-  return process.env.ELEVASIS_API_KEY ?? "";
+  return process.env.ELEVASIS_PLATFORM_KEY ?? "";
 }
 
 // src/cli/api-client.ts
 function getApiKey() {
-  const key = process.env.ELEVASIS_API_KEY;
+  const key = process.env.ELEVASIS_PLATFORM_KEY;
   if (!key) {
     throw new Error(
-      "ELEVASIS_API_KEY environment variable is required.\nSet it in your .env file: ELEVASIS_API_KEY=sk_..."
+      "ELEVASIS_PLATFORM_KEY environment variable is required.\nSet it in your .env file: ELEVASIS_PLATFORM_KEY=sk_..."
     );
   }
   return key;
@@ -43730,7 +43745,7 @@ async function apiGet(endpoint, apiUrl = resolveApiUrl()) {
   if (!response.ok) {
     const errorText = await response.text();
     if (response.status === 401) {
-      throw new Error(`401 Unauthorized: Invalid or missing ELEVASIS_API_KEY. Check your .env file.`);
+      throw new Error(`401 Unauthorized: Invalid or missing ELEVASIS_PLATFORM_KEY. Check your .env file.`);
     }
     throw new Error(`API request failed (${response.status}): ${errorText}`);
   }
@@ -43793,7 +43808,7 @@ async function apiDelete(endpoint, apiUrl = resolveApiUrl()) {
 // package.json
 var package_default = {
   name: "@elevasis/sdk",
-  version: "0.5.6",
+  version: "0.5.8",
   description: "SDK for building Elevasis organization resources",
   "comment:bin": "IMPORTANT: This package shares the 'elevasis' binary name with @repo/cli. They never conflict because @elevasis/sdk must NEVER be added as a dependency of any workspace package (apps/*, packages/*, organizations/*). Workspace projects use @repo/cli for the 'elevasis' binary. External developers (outside the workspace) get this SDK's binary via npm install.",
   type: "module",
@@ -44293,7 +44308,7 @@ async function generateProjectMap(org) {
   let nodeEnv = "not set";
   try {
     const envContent = await (0, import_promises.readFile)((0, import_path.resolve)(".env"), "utf-8");
-    const apiKeyMatch = envContent.match(/^ELEVASIS_API_KEY=(.+)$/m);
+    const apiKeyMatch = envContent.match(/^ELEVASIS_PLATFORM_KEY=(.+)$/m);
     if (apiKeyMatch && apiKeyMatch[1].trim()) apiKeySet = "yes";
     const nodeEnvMatch = envContent.match(/^NODE_ENV=(.+)$/m);
     if (nodeEnvMatch && nodeEnvMatch[1].trim()) nodeEnv = nodeEnvMatch[1].trim();
@@ -44329,7 +44344,7 @@ function registerDeployCommand(program3) {
       authSpinner.fail(source_default.red("Authentication failed"));
       const errMsg = error46 instanceof Error ? error46.message : String(error46);
       if (errMsg.includes("401") || errMsg.toLowerCase().includes("unauthorized")) {
-        const keyVar = !options2.prod && process.env.NODE_ENV === "development" && process.env.ELEVASIS_API_KEY_DEV ? "ELEVASIS_API_KEY_DEV" : "ELEVASIS_API_KEY";
+        const keyVar = !options2.prod && process.env.NODE_ENV === "development" && process.env.ELEVASIS_PLATFORM_KEY_DEV ? "ELEVASIS_PLATFORM_KEY_DEV" : "ELEVASIS_PLATFORM_KEY";
         console.error(source_default.red("  Invalid API key."));
         console.error(source_default.gray(`  Your ${keyVar} was rejected by the server.`));
         console.error(source_default.gray("  Check your .env file and verify the key in the Elevasis dashboard."));
@@ -44469,7 +44484,7 @@ startWorker(org)
         entryPoints: [wrapperPath],
         bundle: true,
         platform: "node",
-        format: "esm",
+        format: "cjs",
         outfile: bundleOutfile
       });
       await (0, import_promises.unlink)(wrapperPath);
@@ -44494,9 +44509,9 @@ startWorker(org)
         uploadSpinner.fail(source_default.red("Missing API key environment variable"));
         console.error(source_default.gray("  Set it in your .env file or shell environment:"));
         if (!options2.prod && process.env.NODE_ENV === "development") {
-          console.error(source_default.gray("    ELEVASIS_API_KEY_DEV=sk_...  (or ELEVASIS_API_KEY as fallback)"));
+          console.error(source_default.gray("    ELEVASIS_PLATFORM_KEY_DEV=sk_...  (or ELEVASIS_PLATFORM_KEY as fallback)"));
         } else {
-          console.error(source_default.gray("    ELEVASIS_API_KEY=sk_..."));
+          console.error(source_default.gray("    ELEVASIS_PLATFORM_KEY=sk_..."));
         }
         throw new Error("Missing API key environment variable");
       }
@@ -45139,11 +45154,11 @@ function tsconfigTemplate() {
   }, null, 2) + "\n";
 }
 function envTemplate() {
-  return `ELEVASIS_API_KEY=
+  return `ELEVASIS_PLATFORM_KEY=
 `;
 }
 function envExampleTemplate() {
-  return `ELEVASIS_API_KEY=sk_your_key_here
+  return `ELEVASIS_PLATFORM_KEY=sk_your_key_here
 `;
 }
 function npmrcTemplate() {
@@ -45185,7 +45200,7 @@ pnpm install
 Copy \`.env.example\` to \`.env\` and add your API key:
 
 \`\`\`
-ELEVASIS_API_KEY=sk_...
+ELEVASIS_PLATFORM_KEY=sk_...
 \`\`\`
 
 ## Development
@@ -45409,7 +45424,7 @@ At the start of every session:
 2. Read \`.claude/memory/index.md\` -- drill into relevant topic files as needed.
    Balance context relevance against token usage.
 3. Check installed \`@elevasis/sdk\` template version against \`templateVersion\`
-   in \`elevasis.config.ts\`. If newer, notify and suggest \`/meta update\`.
+   in \`elevasis.config.ts\`. If newer, notify and suggest \`/meta fix\`.
 4. If \`.claude/memory/\` does not exist, suggest \`/meta init\`.
 5. If user Platform Navigation level is none (from skills.md) and
    \`.claude/memory/tutorial-progress.md\` does not exist, suggest \`/tutorial\`.
@@ -45437,7 +45452,7 @@ proactivity -- to their assessed levels.
 | Workspace concepts | \`reference/concepts/index.mdx\` | User asks "what is...?" or needs conceptual grounding |
 | SDK patterns and examples | \`reference/resources/patterns.mdx\` | Building or modifying a workflow |
 | Platform tool catalog | \`reference/platform-tools/index.mdx\` | Connecting to external services |
-| CLI reference | \`reference/cli/index.mdx\` | Running CLI operations |
+| CLI reference | \`reference/cli/index.mdx\` | Running execution/platform operations |
 | Credential model | \`reference/security/credentials.mdx\` | Setting up integrations or tool access |
 | Interaction guidance | \`reference/developer/interaction-guidance.mdx\` | Unsure how to adapt for a skill combination |
 | Error history | \`.claude/memory/errors/index.md\` | Debugging errors, checking past fixes |
@@ -45455,7 +45470,7 @@ All \`reference/\` paths resolve to \`node_modules/@elevasis/sdk/reference/\`.
 
 ## Elevasis CLI
 
-**MANDATORY:** Use the \`elevasis\` CLI for all operations -- never \`npx\`, \`curl\`, or any other tool.
+**MANDATORY:** Use the \`elevasis\` CLI for all execution/platform operations -- never \`npx\`, \`curl\`, or any other tool.
 
 - \`elevasis exec <resource-id> --input '{...}'\` -- run a resource synchronously
 - \`elevasis exec <resource-id> --input '{...}' --async\` -- run async, returns execution ID
@@ -46080,17 +46095,49 @@ for intermediate/advanced users.
 
 ## Progress Format
 
-Store in \`.claude/memory/tutorial-progress.md\`:
-- Current (free-form, e.g. "L4: Using Platform Tools" or "M:integrations" or "MF2")
-- Started and Last Session dates
-- Completed Lessons table (lesson, title, completed, duration)
-- Completed Modules table (module, title, completed, duration)
-- Completed MF Lessons table (lesson, title, completed, notes)
-- Capability Observations table (source, observation) -- prefix L# for lessons, M:<id> for modules, MF# for MF lessons
-- Assessment Notes (bullet points)
-
-Backward-compatible: missing Completed Modules treated as empty;
-missing Completed MF Lessons treated as empty.
+On first \`/tutorial\` invocation, if \`.claude/memory/tutorial-progress.md\` does not exist,
+create it with this exact format:
+
+\`\`\`markdown
+# Tutorial Progress
+
+Current: Not started
+Started: {today's date}
+Last Session: {today's date}
+
+## Completed Lessons
+
+| Lesson | Title | Completed | Duration |
+| --- | --- | --- | --- |
+
+## Completed Modules
+
+| Module | Title | Completed | Duration |
+| --- | --- | --- | --- |
+
+## Completed MF Lessons
+
+| Lesson | Title | Completed | Notes |
+| --- | --- | --- | --- |
+
+## Capability Observations
+
+| Source | Observation |
+| --- | --- |
+
+## Assessment Notes
+
+(none yet)
+\`\`\`
+
+Update rules:
+- \`Current\`: free-form, e.g. "L4: Using Platform Tools" or "M:integrations" or "MF2"
+- \`Last Session\`: update to today's date on each \`/tutorial\` invocation
+- Completed tables: add a row when a lesson/module/MF lesson finishes
+- Capability Observations: prefix source with L# for lessons, M:<id> for modules, MF# for MF lessons
+- Assessment Notes: bullet points of general skill observations
+
+Backward-compatible: missing Completed Modules or Completed MF Lessons sections treated as empty.
 `;
 }
 function claudeMetaCommandTemplate() {
@@ -46115,14 +46162,14 @@ by the \`<!-- initialized: false -->\` flag in CLAUDE.md, or run manually.
    Run \`pnpm install\`. Wait for completion. Report any errors.
 
 2. **Setup environment**
-   Read \`.env\`. It should contain only a single line: \`ELEVASIS_API_KEY=\`.
-   If \`ELEVASIS_API_KEY\` is empty or missing, ask the user: "What is your
+   Read \`.env\`. It should contain only a single line: \`ELEVASIS_PLATFORM_KEY=\`.
+   If \`ELEVASIS_PLATFORM_KEY\` is empty or missing, ask the user: "What is your
    Elevasis API key?" When the user provides it, write \`.env\` with exactly:
    \`\`\`
-   ELEVASIS_API_KEY=<value they provided>
+   ELEVASIS_PLATFORM_KEY=<value they provided>
    \`\`\`
    No other keys (no \`NODE_ENV\`, no extras). The \`.env\` file must contain
-   only \`ELEVASIS_API_KEY\`.
+   only \`ELEVASIS_PLATFORM_KEY\`.
    Validate the key works: run \`elevasis resources\` (should return an empty
    list, not an auth error). If auth fails, tell the user their key appears
    invalid and ask them to check it in the Elevasis dashboard.
@@ -46145,6 +46192,12 @@ by the \`<!-- initialized: false -->\` flag in CLAUDE.md, or run manually.
      Zapier/Make flows -> automation: low-code
      Custom scripts -> automation: custom
 
+   Inferred dimensions (do NOT ask, derive from answers above):
+   - apiIntegration: automation: none -> none, low-code -> basic, custom -> proficient.
+     Override: if tools answer includes API services (Stripe API, webhook, REST), upgrade one level.
+   - domainExpertise: if goals are specific (names processes, metrics, edge cases) -> high.
+     If goals are vague -> low.
+
    Communication (1 question):
    - "Step-by-step explanations or concise answers?"
 
@@ -46152,7 +46205,24 @@ by the \`<!-- initialized: false -->\` flag in CLAUDE.md, or run manually.
    - Create \`.claude/memory/index.md\` (root index)
    - Create \`.claude/memory/profile/index.md\` (profile index)
    - Create \`.claude/memory/profile/identity.md\` (org, goals, tools)
-   - Create \`.claude/memory/profile/skills.md\` (multi-dimensional assessment)
+   - Create \`.claude/memory/profile/skills.md\` using this exact format:
+
+     \`\`\`markdown
+     # Skills
+
+     | Dimension | Level | Since |
+     | --- | --- | --- |
+     | platformNavigation | {level} | {date} |
+     | apiIntegration | {level} | {date} |
+     | automation | {level} | {date} |
+     | domainExpertise | {level} | {date} |
+
+     ## Growth Log
+
+     | Date | Observation | Dimension | Change |
+     | --- | --- | --- | --- |
+     \`\`\`
+
    - Create \`.claude/memory/profile/preferences.md\` (verbosity, guidance)
 
 4. **Git check**
@@ -46610,7 +46680,7 @@ organization. They are used by workflows and agents at runtime via \`platform.ge
 or the \`credential:\` field on tool steps.
 
 The SDK CLI (\`elevasis-sdk creds\`) manages credentials via API key authentication.
-Your \`ELEVASIS_API_KEY\` in \`.env\` determines the organization.
+Your \`ELEVASIS_PLATFORM_KEY\` in \`.env\` determines the organization.
 
 ## Credential Types
 
@@ -46710,7 +46780,7 @@ description: Elevasis SDK patterns -- imports, source structure, runtime, and pl
 
 ## Runtime
 
-- \`.env\` contains only \`ELEVASIS_API_KEY\` for CLI auth -- never deployed, never in worker memory
+- \`.env\` contains only \`ELEVASIS_PLATFORM_KEY\` for CLI auth -- never deployed, never in worker memory
 - Integration credentials are managed via the \`creds\` skill or Command Center UI
 
 ## Platform Tools

package/dist/index.d.ts

@@ -2973,10 +2973,12 @@ interface CreateNotificationParams {
  * worker thread execution branching and credential management.
  */
 interface RemoteOrgConfig {
-    /** Path to the esbuild bundle on disk */
-    bundlePath: string;
+    /** Supabase Storage path: "{orgId}/{deploymentId}/bundle.js" */
+    storagePath: string;
     /** Deployment record ID */
     deploymentId: string;
+    /** OS temp path to bundle -- set after first download, used by worker threads */
+    cachedTempPath?: string;
     /** Platform tool name -> credential name mapping */
     toolCredentials?: Record<string, string>;
     /** SDK version used to deploy this bundle */
@@ -3107,6 +3109,15 @@ declare class ResourceRegistry {
      * @returns true if the org has at least one runtime-registered resource
      */
     isRemote(orgName: string): boolean;
+    /**
+     * Get the remote config for any resource in an organization.
+     * Used when the specific resource ID is unknown (e.g., to clean up a
+     * temp file before unregistering an org -- all resources share one config).
+     *
+     * @param orgName - Organization name
+     * @returns Remote config or null if org has no remote resources
+     */
+    getAnyRemoteConfig(orgName: string): RemoteOrgConfig | null;
     /**
      * Get triggers for an organization
      * @param organizationName - Organization name
@@ -6320,7 +6331,7 @@ type ResourceStatus = 'dev' | 'prod';
 /**
  * Project configuration for an external developer project.
  * Defined in elevasis.config.ts at the project root.
- * Organization is derived from the ELEVASIS_API_KEY -- not configured here.
+ * Organization is derived from the ELEVASIS_PLATFORM_KEY -- not configured here.
  */
 interface ElevasConfig {
     /** Managed by `elevasis init` and `elevasis update`. Do not set manually. */

package/dist/index.js

@@ -3423,6 +3423,21 @@ var ResourceRegistry = class {
     }
     return false;
   }
+  /**
+   * Get the remote config for any resource in an organization.
+   * Used when the specific resource ID is unknown (e.g., to clean up a
+   * temp file before unregistering an org -- all resources share one config).
+   *
+   * @param orgName - Organization name
+   * @returns Remote config or null if org has no remote resources
+   */
+  getAnyRemoteConfig(orgName) {
+    const prefix = `${orgName}/`;
+    for (const [key, config] of this.remoteResources) {
+      if (key.startsWith(prefix)) return config;
+    }
+    return null;
+  }
   // ============================================================================
   // Resource Manifest Accessors
   // ============================================================================

package/dist/templates.js

@@ -200,7 +200,7 @@ At the start of every session:
 2. Read \`.claude/memory/index.md\` -- drill into relevant topic files as needed.
    Balance context relevance against token usage.
 3. Check installed \`@elevasis/sdk\` template version against \`templateVersion\`
-   in \`elevasis.config.ts\`. If newer, notify and suggest \`/meta update\`.
+   in \`elevasis.config.ts\`. If newer, notify and suggest \`/meta fix\`.
 4. If \`.claude/memory/\` does not exist, suggest \`/meta init\`.
 5. If user Platform Navigation level is none (from skills.md) and
    \`.claude/memory/tutorial-progress.md\` does not exist, suggest \`/tutorial\`.
@@ -228,7 +228,7 @@ proactivity -- to their assessed levels.
 | Workspace concepts | \`reference/concepts/index.mdx\` | User asks "what is...?" or needs conceptual grounding |
 | SDK patterns and examples | \`reference/resources/patterns.mdx\` | Building or modifying a workflow |
 | Platform tool catalog | \`reference/platform-tools/index.mdx\` | Connecting to external services |
-| CLI reference | \`reference/cli/index.mdx\` | Running CLI operations |
+| CLI reference | \`reference/cli/index.mdx\` | Running execution/platform operations |
 | Credential model | \`reference/security/credentials.mdx\` | Setting up integrations or tool access |
 | Interaction guidance | \`reference/developer/interaction-guidance.mdx\` | Unsure how to adapt for a skill combination |
 | Error history | \`.claude/memory/errors/index.md\` | Debugging errors, checking past fixes |
@@ -246,7 +246,7 @@ All \`reference/\` paths resolve to \`node_modules/@elevasis/sdk/reference/\`.
 
 ## Elevasis CLI
 
-**MANDATORY:** Use the \`elevasis\` CLI for all operations -- never \`npx\`, \`curl\`, or any other tool.
+**MANDATORY:** Use the \`elevasis\` CLI for all execution/platform operations -- never \`npx\`, \`curl\`, or any other tool.
 
 - \`elevasis exec <resource-id> --input '{...}'\` -- run a resource synchronously
 - \`elevasis exec <resource-id> --input '{...}' --async\` -- run async, returns execution ID
@@ -871,17 +871,49 @@ for intermediate/advanced users.
 
 ## Progress Format
 
-Store in \`.claude/memory/tutorial-progress.md\`:
-- Current (free-form, e.g. "L4: Using Platform Tools" or "M:integrations" or "MF2")
-- Started and Last Session dates
-- Completed Lessons table (lesson, title, completed, duration)
-- Completed Modules table (module, title, completed, duration)
-- Completed MF Lessons table (lesson, title, completed, notes)
-- Capability Observations table (source, observation) -- prefix L# for lessons, M:<id> for modules, MF# for MF lessons
-- Assessment Notes (bullet points)
-
-Backward-compatible: missing Completed Modules treated as empty;
-missing Completed MF Lessons treated as empty.
+On first \`/tutorial\` invocation, if \`.claude/memory/tutorial-progress.md\` does not exist,
+create it with this exact format:
+
+\`\`\`markdown
+# Tutorial Progress
+
+Current: Not started
+Started: {today's date}
+Last Session: {today's date}
+
+## Completed Lessons
+
+| Lesson | Title | Completed | Duration |
+| --- | --- | --- | --- |
+
+## Completed Modules
+
+| Module | Title | Completed | Duration |
+| --- | --- | --- | --- |
+
+## Completed MF Lessons
+
+| Lesson | Title | Completed | Notes |
+| --- | --- | --- | --- |
+
+## Capability Observations
+
+| Source | Observation |
+| --- | --- |
+
+## Assessment Notes
+
+(none yet)
+\`\`\`
+
+Update rules:
+- \`Current\`: free-form, e.g. "L4: Using Platform Tools" or "M:integrations" or "MF2"
+- \`Last Session\`: update to today's date on each \`/tutorial\` invocation
+- Completed tables: add a row when a lesson/module/MF lesson finishes
+- Capability Observations: prefix source with L# for lessons, M:<id> for modules, MF# for MF lessons
+- Assessment Notes: bullet points of general skill observations
+
+Backward-compatible: missing Completed Modules or Completed MF Lessons sections treated as empty.
 `;
 }
 function claudeMetaCommandTemplate() {
@@ -906,14 +938,14 @@ by the \`<!-- initialized: false -->\` flag in CLAUDE.md, or run manually.
    Run \`pnpm install\`. Wait for completion. Report any errors.
 
 2. **Setup environment**
-   Read \`.env\`. It should contain only a single line: \`ELEVASIS_API_KEY=\`.
-   If \`ELEVASIS_API_KEY\` is empty or missing, ask the user: "What is your
+   Read \`.env\`. It should contain only a single line: \`ELEVASIS_PLATFORM_KEY=\`.
+   If \`ELEVASIS_PLATFORM_KEY\` is empty or missing, ask the user: "What is your
    Elevasis API key?" When the user provides it, write \`.env\` with exactly:
    \`\`\`
-   ELEVASIS_API_KEY=<value they provided>
+   ELEVASIS_PLATFORM_KEY=<value they provided>
    \`\`\`
    No other keys (no \`NODE_ENV\`, no extras). The \`.env\` file must contain
-   only \`ELEVASIS_API_KEY\`.
+   only \`ELEVASIS_PLATFORM_KEY\`.
    Validate the key works: run \`elevasis resources\` (should return an empty
    list, not an auth error). If auth fails, tell the user their key appears
    invalid and ask them to check it in the Elevasis dashboard.
@@ -936,6 +968,12 @@ by the \`<!-- initialized: false -->\` flag in CLAUDE.md, or run manually.
      Zapier/Make flows -> automation: low-code
      Custom scripts -> automation: custom
 
+   Inferred dimensions (do NOT ask, derive from answers above):
+   - apiIntegration: automation: none -> none, low-code -> basic, custom -> proficient.
+     Override: if tools answer includes API services (Stripe API, webhook, REST), upgrade one level.
+   - domainExpertise: if goals are specific (names processes, metrics, edge cases) -> high.
+     If goals are vague -> low.
+
    Communication (1 question):
    - "Step-by-step explanations or concise answers?"
 
@@ -943,7 +981,24 @@ by the \`<!-- initialized: false -->\` flag in CLAUDE.md, or run manually.
    - Create \`.claude/memory/index.md\` (root index)
    - Create \`.claude/memory/profile/index.md\` (profile index)
    - Create \`.claude/memory/profile/identity.md\` (org, goals, tools)
-   - Create \`.claude/memory/profile/skills.md\` (multi-dimensional assessment)
+   - Create \`.claude/memory/profile/skills.md\` using this exact format:
+
+     \`\`\`markdown
+     # Skills
+
+     | Dimension | Level | Since |
+     | --- | --- | --- |
+     | platformNavigation | {level} | {date} |
+     | apiIntegration | {level} | {date} |
+     | automation | {level} | {date} |
+     | domainExpertise | {level} | {date} |
+
+     ## Growth Log
+
+     | Date | Observation | Dimension | Change |
+     | --- | --- | --- | --- |
+     \`\`\`
+
    - Create \`.claude/memory/profile/preferences.md\` (verbosity, guidance)
 
 4. **Git check**
@@ -1401,7 +1456,7 @@ organization. They are used by workflows and agents at runtime via \`platform.ge
 or the \`credential:\` field on tool steps.
 
 The SDK CLI (\`elevasis-sdk creds\`) manages credentials via API key authentication.
-Your \`ELEVASIS_API_KEY\` in \`.env\` determines the organization.
+Your \`ELEVASIS_PLATFORM_KEY\` in \`.env\` determines the organization.
 
 ## Credential Types
 
@@ -1501,7 +1556,7 @@ description: Elevasis SDK patterns -- imports, source structure, runtime, and pl
 
 ## Runtime
 
-- \`.env\` contains only \`ELEVASIS_API_KEY\` for CLI auth -- never deployed, never in worker memory
+- \`.env\` contains only \`ELEVASIS_PLATFORM_KEY\` for CLI auth -- never deployed, never in worker memory
 - Integration credentials are managed via the \`creds\` skill or Command Center UI
 
 ## Platform Tools

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elevasis/sdk",
-  "version": "0.5.6",
+  "version": "0.5.8",
   "description": "SDK for building Elevasis organization resources",
   "comment:bin": "IMPORTANT: This package shares the 'elevasis' binary name with @repo/cli. They never conflict because @elevasis/sdk must NEVER be added as a dependency of any workspace package (apps/*, packages/*, organizations/*). Workspace projects use @repo/cli for the 'elevasis' binary. External developers (outside the workspace) get this SDK's binary via npm install.",
   "type": "module",

package/reference/developer/interaction-guidance.mdx

@@ -149,11 +149,11 @@ Do not automatically update the skill profile for every observation. Update when
 When updating `.claude/memory/profile/skills.md` Growth Log:
 
 ```
-| Date | Observation | Skill Updated |
-| 2026-03-01 | Navigated to Execution Logs and filtered by resource without direction | Platform Navigation: none -> oriented |
+| Date | Observation | Dimension | Change |
+| 2026-03-01 | Navigated to Execution Logs and filtered by resource without direction | platformNavigation | none -> oriented |
 ```
 
-Also update the dimension's Level field and Evidence field to reflect the new assessment.
+Also update the dimension's Level and Since fields in the Dimensions table.
 
 ### Celebration
 

package/reference/framework/agent.mdx

@@ -18,7 +18,7 @@ The file is instruction-driven by design. Non-technical developers should never
 
 The generated `CLAUDE.md` contains these sections:
 
-- **Session Initialization** -- Checks the `<!-- initialized: false -->` auto-init flag; if false, runs `/meta init` automatically. Otherwise reads `memory/profile/skills.md` for adaptive behavior, reads `memory/index.md` for project context, checks if the template version is current, and suggests `/tutorial` for TypeScript beginners.
+- **Session Initialization** -- Checks the `<!-- initialized: false -->` auto-init flag; if false, runs `/meta init` automatically. Otherwise reads `memory/profile/skills.md` for adaptive behavior, reads `memory/index.md` for project context, checks if the template version is current, and suggests `/tutorial` for users with no Platform Navigation experience.
 - **Identity** -- Project orientation: what an Elevasis SDK project is, the developer's role, and how to adapt to non-technical users.
 - **Navigation** -- A table mapping concepts to file paths with load conditions (when to load each file). Includes SDK reference docs, credential model, error history, `docs/project-map.mdx`, and `docs/priorities.mdx`.
 - **Rules** -- Points to auto-loaded rule files in `.claude/rules/`. SDK patterns load automatically; project-specific patterns live in `workspace-patterns.md`. Includes error handling protocol.
@@ -36,7 +36,7 @@ At the start of every session the agent runs these steps silently before respond
 2. Read `.claude/memory/index.md` if it exists -- drill into relevant topic files as needed, balancing context relevance against token usage.
 3. Check the installed `@elevasis/sdk` template version against `templateVersion` in `elevasis.config.ts`. If the SDK has a newer version, notify the user and suggest running `/meta fix`.
 4. If `.claude/memory/` does not exist, suggest running `/meta init` to set up the project.
-5. If the user's TypeScript level is beginner (from skills.md) and `.claude/memory/tutorial-progress.md` does not exist, suggest `/tutorial`.
+5. If the user's Platform Navigation level is none (from skills.md) and `.claude/memory/tutorial-progress.md` does not exist, suggest `/tutorial`.
 
 ## Slash Commands
 
@@ -91,10 +91,10 @@ The developer profile is stored in `.claude/memory/profile/` as a set of markdow
 
 ### Onboarding Flow
 
-Profile data is created during `/meta init`. The command runs a competency assessment (5-7 questions with conditional skipping) and writes the responses to `memory/profile/`:
+Profile data is created during `/meta init`. The command runs a 6-question assessment and writes the responses to `memory/profile/`:
 
 - **Identity & Goals (3 questions):** What the business does, what to automate, which tools are already in use.
-- **Competency (2-3 conditional questions):** Programming background, TypeScript experience (only asked if the user has written scripts or more), automation tool familiarity.
+- **Competency (2 questions):** Command Center familiarity (maps to `platformNavigation`), automation tool familiarity (maps to `automation`). Two additional dimensions (`apiIntegration`, `domainExpertise`) are inferred from these answers.
 - **Communication (1 question):** Step-by-step explanations vs. concise answers.
 
 ### Profile Structure
@@ -103,11 +103,11 @@ Profile data is created during `/meta init`. The command runs a competency asses
 .claude/memory/profile/
 ├── index.md          # Profile summary with links to sub-files
 ├── identity.md       # Organization, industry, goals, integrations
-├── skills.md         # TypeScript level, automation experience, growth history
+├── skills.md         # Skill dimensions (platformNavigation, apiIntegration, automation, domainExpertise)
 └── preferences.md    # Verbosity, guidance style, interaction patterns
 ```
 
-`identity.md` records the organization name, industry, size, project goals, and known tool integrations. `skills.md` stores the TypeScript and automation skill levels as structured values (`beginner / intermediate / advanced`, `new / some-experience / experienced`) along with a growth history table. `preferences.md` stores verbosity (`detailed / concise`) and proactive guidance preference.
+`identity.md` records the organization name, industry, size, project goals, and known tool integrations. `skills.md` stores four skill dimensions as structured values (`platformNavigation`, `apiIntegration`, `automation`, `domainExpertise`) along with a Growth Log table. See [Interaction Guidance](../developer/interaction-guidance.mdx) for the full set of per-dimension adaptation rules. `preferences.md` stores verbosity (`detailed / concise`) and proactive guidance preference.
 
 ### Auto-Update Triggers
 

package/reference/framework/index.mdx

@@ -79,15 +79,18 @@ See [Documentation](documentation.mdx) for writing MDX docs, file limits, and th
 
 ## Adaptive Guidance
 
-The agent adapts its communication based on five independent skill dimensions stored in `memory/profile/skills.md`:
+The agent adapts its communication based on four independent skill dimensions stored in `memory/profile/skills.md`:
 
-- **Programming Fundamentals** -- none / minimal / comfortable / advanced
-- **TypeScript** -- none / exposure / proficient
-- **API & Integration** -- none / basic / proficient
-- **Automation Concepts** -- none / low-code / custom
-- **Data Management** -- none / spreadsheets / databases
+| Dimension | Levels | Assessment |
+| --- | --- | --- |
+| Platform Navigation | none / oriented / comfortable | Direct question |
+| API & Integration | none / basic / proficient | Inferred from automation + tools |
+| Automation Concepts | none / low-code / custom | Direct question |
+| Domain Expertise | high / low | Inferred from identity answers |
 
-Each dimension is assessed separately during `/meta init` via 5-6 conditional questions. A user who has deep Zapier experience but no TypeScript knowledge will receive Zod explanations every time while getting automation concepts treated as familiar ground. The questions use conditional skipping to minimize friction: beginners answer 5 questions, developers answer 6.
+Each dimension has its own adaptation rules in the [Interaction Guidance](../developer/interaction-guidance.mdx) reference. A user who has deep Zapier experience (automation: low-code) but has never called an API directly (apiIntegration: none) will get credential walkthroughs every time while having automation concepts treated as familiar ground.
+
+`/meta init` runs a 6-question assessment: 3 identity questions, 2 competency questions, and 1 communication preference. Platform Navigation and Automation are assessed directly. API & Integration is inferred from the automation level and tools the user already uses. Domain Expertise is inferred from how specifically the user describes their goals.
 
 See [Agent System](agent.mdx) for the full assessment question set, dimensional interaction rules, and communication principles.
 

package/reference/framework/memory.mdx

@@ -38,7 +38,7 @@ After `/meta init` and a first deployment, the structure looks like this:
 ├── profile/                    # Developer profile (created by /meta init)
 │   ├── index.md                # Profile summary with links to sub-files
 │   ├── identity.md             # Organization, industry, goals, integrations
-│   ├── skills.md               # TypeScript level, automation experience, growth
+│   ├── skills.md               # Skill dimensions and Growth Log
 │   └── preferences.md          # Verbosity, guidance style, interaction patterns
 ├── deployment-state.md         # Deploy IDs, resource inventory, org info
 ├── environment.md              # Credentials, API keys, env vars
@@ -85,7 +85,7 @@ The `profile/` directory stores the developer's personal context -- organization
 .claude/memory/profile/
 ├── index.md          # Profile summary with links to sub-files
 ├── identity.md       # Organization, industry, goals, integrations
-├── skills.md         # TypeScript level, automation experience, growth history
+├── skills.md         # Skill dimensions and Growth Log
 └── preferences.md    # Verbosity, guidance style, interaction patterns
 ```
 
@@ -113,22 +113,32 @@ The `profile/` directory stores the developer's personal context -- organization
 - Google Sheets (reporting)
 ```
 
-**`skills.md`** stores skill levels as structured values so the Adaptive Guidance rules can apply them consistently. It also tracks a growth history table so the agent can detect when a level upgrade is warranted. Example:
+**`skills.md`** stores four skill dimensions as structured values so the Adaptive Guidance rules in [Interaction Guidance](../developer/interaction-guidance.mdx) can apply them consistently. It also tracks a Growth Log so the agent can detect when a level upgrade is warranted. Example:
 
 ```markdown
 # Skills
 
-| Skill | Level | Since |
+| Dimension | Level | Since |
 | --- | --- | --- |
-| TypeScript | beginner | 2026-02-25 |
-| AI automation | new | 2026-02-25 |
+| platformNavigation | oriented | 2026-02-25 |
+| apiIntegration | basic | 2026-02-25 |
+| automation | low-code | 2026-02-25 |
+| domainExpertise | high | 2026-02-25 |
 
-## Growth History
+## Growth Log
 
-| Date | Change | Evidence |
-| --- | --- | --- |
+| Date | Observation | Dimension | Change |
+| --- | --- | --- | --- |
+| 2026-03-01 | Navigated to Execution Logs and filtered by resource without direction | platformNavigation | none -> oriented |
 ```
 
+Valid levels per dimension:
+
+- `platformNavigation`: none / oriented / comfortable
+- `apiIntegration`: none / basic / proficient
+- `automation`: none / low-code / custom
+- `domainExpertise`: high / low
+
 **`preferences.md`** stores verbosity and proactive guidance settings. Example:
 
 ```markdown

package/reference/framework/project-structure.mdx

@@ -216,7 +216,7 @@ Created when you run `/meta init` in Claude Code. The agent asks six onboarding
 ├── profile/                    # Developer profile (created by /meta init)
 │   ├── index.md
 │   ├── identity.md             # Organization, goals, integrations
-│   ├── skills.md               # TypeScript level, automation experience
+│   ├── skills.md               # Skill dimensions and Growth Log
 │   └── preferences.md          # Verbosity and guidance style
 ├── deployment-state.md         # Latest deployment outcomes
 ├── decisions.md                # Architecture decisions recorded over time

package/reference/getting-started/index.mdx

@@ -98,7 +98,9 @@ The `.env.example` file provides the same template and is safe to commit. The ac
 
 ### Guided Setup with Claude Code
 
-After scaffolding, open the project in Claude Code and run `/meta init`. This command installs dependencies, walks you through `.env` setup, creates your developer profile in `.claude/memory/`, and optionally runs your first deploy -- all in one guided flow.
+After scaffolding, open the project in Claude Code. The agent detects that the project is new and automatically walks you through setup: installing dependencies, configuring `.env`, creating your developer profile in `.claude/memory/`, and optionally running your first deploy. No commands needed -- just answer the questions.
+
+If the automatic setup doesn't trigger, you can start it manually with `/meta init`.
 
 ---
 
@@ -145,13 +147,13 @@ Replace `<execution-id>` with the ID returned from the executions list.
 
 ## Next Steps
 
-- **Run `/meta init` in Claude Code** -- Guided setup that installs deps, configures `.env`, and creates your developer profile in `.claude/memory/`
+- **Open in Claude Code** -- Setup runs automatically on first session (installs deps, configures `.env`, creates your developer profile)
 - [Development Framework](../framework/index.mdx) -- How Claude Code helps you build
 - [Resources](../resources/index.mdx) -- Define workflows and agents
 - [CLI Reference](../cli/index.mdx) -- Full command reference with flags
 - [Deployment](../deployment/index.mdx) -- Deployment lifecycle and environment variables
 
-When a new SDK version is released, run `elevasis update` to bring your project's managed files (CLAUDE.md, slash commands, `.gitignore`) up to date. The command adds missing files and flags any files that differ from the new template for agent-assisted review.
+When a new SDK version is released, run `/meta fix` in Claude Code for an interactive upgrade that includes SDK update, drift repair, and documentation verification. Alternatively, run `elevasis update` from the terminal to update managed files (CLAUDE.md, slash commands, `.gitignore`) without agent interaction.
 
 ---