@elevasis/sdk 0.5.13 → 0.5.14

package/dist/cli.cjs

@@ -43478,6 +43478,21 @@ var ResourceRegistry = class {
     }
     return null;
   }
+  /**
+   * Get statistics about remotely-deployed resources
+   * Used by the health endpoint for platform-wide deployment visibility.
+   */
+  getRemoteStats() {
+    const orgs = /* @__PURE__ */ new Set();
+    for (const key of this.remoteResources.keys()) {
+      const orgName = key.split("/")[0];
+      orgs.add(orgName);
+    }
+    return {
+      activeOrgs: orgs.size,
+      totalResources: this.remoteResources.size
+    };
+  }
   // ============================================================================
   // Resource Manifest Accessors
   // ============================================================================
@@ -43783,7 +43798,7 @@ async function apiDelete(endpoint, apiUrl = resolveApiUrl()) {
 // package.json
 var package_default = {
   name: "@elevasis/sdk",
-  version: "0.5.13",
+  version: "0.5.14",
   description: "SDK for building Elevasis organization resources",
   type: "module",
   bin: {
@@ -45450,16 +45465,16 @@ proactivity -- to their assessed levels.
 
 | Resource | Location | When to Load |
 | --- | --- | --- |
-| Workspace concepts | \`reference/concepts/index.mdx\` | User asks "what is...?" or needs conceptual grounding |
+| Workspace concepts | \`reference/concepts.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 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 |
+| CLI reference | \`reference/cli.mdx\` | Running execution/platform operations |
+| Credential model | \`reference/platform-tools/index.mdx\` | Setting up integrations or credential security |
+| Interaction guidance | \`reference/framework/interaction-guidance.mdx\` | Unsure how to adapt for a skill combination |
 | Error history | \`.claude/memory/errors/index.md\` | Debugging errors, checking past fixes |
-| Command View model | \`reference/deployment/command-view.mdx\` | Deploying or building resources that invoke other resources |
-| Command Center UI reference | \`reference/deployment/command-center-ui.mdx\` | User asks about post-deployment UI or Command Center navigation |
-| SDK error reference | \`reference/troubleshooting/common-errors.mdx\` | Unknown error not in workspace memory |
+| Command View model | \`reference/deployment/command-center.mdx\` | Deploying or building resources that invoke other resources |
+| Command Center UI reference | \`reference/deployment/command-center.mdx\` | User asks about post-deployment UI or Command Center navigation |
+| SDK error reference | \`reference/troubleshooting.mdx\` | Unknown error not in workspace memory |
 | Project map | \`docs/project-map.mdx\` | Session start, project orientation |
 | Resource inventory | \`docs/resource-map.mdx\` | Finding a specific resource by name or ID |
 | Project priorities | \`docs/priorities.mdx\` | Deciding what to work on next |
@@ -45485,7 +45500,7 @@ Use \`pnpm exec elevasis-sdk\` for runtime commands (resolves the locally instal
 - \`pnpm exec elevasis-sdk execution <resource-id> <execution-id>\` -- inspect execution detail
 
 Organization is derived from your API key -- no org prefix needed in the resource ID.
-For full CLI reference: \`reference/cli/index.mdx\`
+For full CLI reference: \`reference/cli.mdx\`
 
 ## Rules
 
@@ -45500,8 +45515,8 @@ SDK patterns (imports, source structure, platform tools) are auto-loaded from
 
 When an error occurs:
 1. Check \`.claude/memory/errors/\` first for past fixes
-2. If new, check \`reference/troubleshooting/common-errors.mdx\`
-3. After resolving, record in \`memory/errors/\` with context and fix
+2. If new, check \`reference/troubleshooting.mdx\`
+3. After resolving, record in \`.claude/memory/errors/\` with context and fix
 4. If an error recurs 3+ times, add a rule to \`.claude/rules/workspace-patterns.md\`${ctx.hasUI ? `
 
 ### UI App (\`ui/\`)
@@ -45533,7 +45548,7 @@ based on what you find.
 - When growth is observed, note it in the skills.md Growth Log.
 
 For detailed per-dimension adaptation rules, read
-\`reference/developer/interaction-guidance.mdx\`.
+\`reference/framework/interaction-guidance.mdx\`.
 
 ## Commands
 
@@ -45542,7 +45557,7 @@ For detailed per-dimension adaptation rules, read
 | \`/meta\` | Project lifecycle: init, status, fix, deploy, health |
 | \`/docs\` | Browse, create, and verify permanent documentation |
 | \`/work\` | Task tracking: create, save, resume, complete |
-| \`/tutorial\` | Progressive learning path (7 core lessons + 9 modules) |
+| \`/tutorial\` | Progressive learning path (21 items across 4 sections) |
 
 ## Skills
 
@@ -45575,7 +45590,7 @@ Do not store in \`.claude/memory/\`:
 
 ### Structure
 
-- \`memory/index.md\` is the root -- maps to topic files and subdirectories
+- \`.claude/memory/index.md\` is the root -- maps to topic files and subdirectories
 - Every subdirectory has its own \`index.md\` mapping to children
 - Start at the root index and drill down
 - When a file outgrows a single document, split into a subdirectory
@@ -45599,14 +45614,14 @@ Read \`.claude/memory/profile/skills.md\` first. The \`automation\` skill level
 controls which docs you load and which lesson variant you deliver.
 
 **automation: none**
-- Load from \`reference/concepts/index.mdx\`: Glossary, What is a Workflow,
+- Load from \`reference/concepts.mdx\`: Glossary, What is a Workflow,
   Platform Tools Overview only. Skip Zod, Execution Model, Design Decisions.
-- Load \`reference/deployment/command-center-ui.mdx\` for UI-first teaching.
+- Load \`reference/deployment/command-center.mdx\` for UI-first teaching.
 - Do NOT load \`reference/resources/patterns.mdx\` or
   \`reference/platform-tools/adapters.mdx\` during core lessons.
 
 **automation: low-code**
-- Load all sections of \`reference/concepts/index.mdx\`.
+- Load all sections of \`reference/concepts.mdx\`.
 - Load \`reference/resources/patterns.mdx\` with Zapier/Make mapping in mind.
 - Load \`reference/platform-tools/adapters.mdx\` on-demand (when tools are used).
 
@@ -45694,7 +45709,7 @@ Each lesson follows this flow:
 
 When automation is none:
 Skip the file tour. Start with what Elevasis does for their business -- use analogies
-from \`reference/developer/interaction-guidance.mdx\` (recipe, assembly line, kitchen
+from \`reference/framework/interaction-guidance.mdx\` (recipe, assembly line, kitchen
 appliance). Explain deployment plainly: "You write the recipe here, then deploy it so
 it's live." Deploy the starter echo workflow (\`elevasis-sdk check\` + \`elevasis-sdk deploy\`),
 THEN tour the Command Center so the user sees populated pages, not empty ones. Tour:
@@ -45942,14 +45957,14 @@ Each module follows this flow:
 ## Modules
 
 **Module: hitl -- Human-in-the-Loop**
-Read: \`reference/deployment/command-center-ui.mdx\` (Command Queue section).
+Read: \`reference/deployment/command-center.mdx\` (Command Queue section).
 Build: Add an approval gate using \`approval.requestApproval()\`. Test full lifecycle:
 trigger, see pending in Command Queue, approve/reject, observe resume.
 Key concepts: approval adapter, pending state, Command Queue UI, resume on decision.
 Verify: Trigger workflow, open Command Queue, approve, confirm completion.
 
 **Module: schedules -- Task Scheduling**
-Read: \`reference/deployment/command-center-ui.mdx\` (Task Scheduler section).
+Read: \`reference/deployment/command-center.mdx\` (Task Scheduler section).
 Build: Create all three schedule types (Recurring cron, Relative delay, Absolute
 datetime). Use \`scheduler\` adapter for in-workflow scheduling.
 Key concepts: schedule types, cron syntax, scheduler adapter, Task Scheduler UI.
@@ -45963,7 +45978,7 @@ Verify: Run workflow, check notification in Command Center, confirm email receiv
 
 **Module: integrations -- Real-World Integrations**
 Read: \`reference/platform-tools/index.mdx\`, \`reference/platform-tools/adapters.mdx\`,
-\`reference/security/credentials.mdx\`.
+\`reference/platform-tools/index.mdx\`.
 Build: Pick a real integration adapter based on user's goals (read \`identity.md\`).
 Set up credential (OAuth via UI, API key via CLI). Build end-to-end integration workflow.
 Key concepts: adapter pattern, credential scoping, error handling for external calls.
@@ -45972,7 +45987,7 @@ handling with invalid credential.
 
 **Module: error-handling -- Error Handling Mastery**
 Read: \`reference/resources/patterns.mdx\` (error handling),
-\`reference/troubleshooting/common-errors.mdx\`.
+\`reference/troubleshooting.mdx\`.
 Build: Create a workflow demonstrating all three error types. Add try/catch,
 \`context.logger\`, and error recovery.
 Key concepts: ExecutionError, PlatformToolError, ToolingError, recovery patterns.
@@ -45988,7 +46003,7 @@ Key concepts: context.store, context.logger, domain organization, schema depth.
 Verify: Run workflow, confirm store values in step output, check logs in Execution Logs.
 
 **Module: composition -- Resource Composition**
-Read: \`reference/deployment/command-view.mdx\`, \`reference/resources/patterns.mdx\`.
+Read: \`reference/deployment/command-center.mdx\`, \`reference/resources/patterns.mdx\`.
 Build: Create two workflows where the first triggers the second using
 \`execution.trigger()\`. Declare the relationship.
 Key concepts: execution.trigger, relationship declarations, Command View graph edges.
@@ -46136,7 +46151,7 @@ Last Session: {today's date}
 \`\`\`
 
 Update rules:
-- \`Current\`: free-form, e.g. "4: Using Platform Tools" or "M:integrations" or "20: Rules, Memory, and Customization"
+- \`Current\`: free-form, e.g. "7: Using Platform Tools" or "M:integrations" or "20: Rules, Memory, and Customization"
 - \`Last Session\`: update to today's date on each \`/tutorial\` invocation
 - Completed Lessons: add a row when any numbered item (1-10, 20-21) finishes
 - Completed Modules: add a row when any module (items 11-19) finishes
@@ -46232,9 +46247,9 @@ by the \`<!-- initialized: false -->\` flag in CLAUDE.md, or run manually.
    - Create \`.claude/memory/profile/preferences.md\` (verbosity, guidance)
 
 4. **Git check**
-   - If \`.git/\` exists: note git is configured in memory/profile/preferences.md
+   - If \`.git/\` exists: note git is configured in .claude/memory/profile/preferences.md
    - If \`.git/\` does not exist: suggest \`git init\` and optionally GitHub
-   - If git remote exists: note remote URL in memory/profile/preferences.md
+   - If git remote exists: note remote URL in .claude/memory/profile/preferences.md
 
 5. **Verify project**
    Run \`elevasis-sdk check\` to confirm the starter resource is valid.
@@ -46255,9 +46270,9 @@ by the \`<!-- initialized: false -->\` flag in CLAUDE.md, or run manually.
 
 Display a project health summary:
 1. Template version (from elevasis.config.ts) and installed SDK version (from package.json). Suggest \`elevasis-sdk update\` to check for updates
-3. Profile summary (from memory/profile/skills.md)
-4. Quick drift check: count of missing managed files, missing gitignore entries
-5. Last deployment status (from memory/deployment-state.md if it exists)
+2. Profile summary (from .claude/memory/profile/skills.md)
+3. Quick drift check: count of missing managed files, missing gitignore entries
+4. Last deployment status (from .claude/memory/deployment-state.md if it exists)
 
 ### \`/meta fix\` -- Maintenance and Upgrade
 
@@ -46275,9 +46290,9 @@ Detect and repair all drift. Optionally upgrades the SDK first.
 3. **CLAUDE.md sections:** Add missing sections in correct position
 4. **Memory structure:** Create base structure if missing, then verify index consistency.
    If \`.claude/memory/\` does not exist or is empty:
-   - Create \`memory/index.md\` (root index with placeholder entries)
-   - Create \`memory/errors/index.md\` (error category summary, empty tables)
-   - Create \`memory/errors/deploy.md\`, \`memory/errors/runtime.md\`, \`memory/errors/typescript.md\`
+   - Create \`.claude/memory/index.md\` (root index with placeholder entries)
+   - Create \`.claude/memory/errors/index.md\` (error category summary, empty tables)
+   - Create \`.claude/memory/errors/deploy.md\`, \`.claude/memory/errors/runtime.md\`, \`.claude/memory/errors/typescript.md\`
    If memory exists, verify: every file referenced in an index exists; every file
    without an index entry gets one added; broken references are removed.
 5. **Documentation verification:** For each file in docs/:
@@ -46288,7 +46303,7 @@ Detect and repair all drift. Optionally upgrades the SDK first.
    e. Report discrepancies with suggested fixes
    Note: \`/docs verify\` is available for standalone interactive verification outside this pipeline.
 6. **Settings consistency:** Verify expected fields
-7. **Rules health:** Scan \`memory/errors/\` -- flag any entry that has recurred
+7. **Rules health:** Scan \`.claude/memory/errors/\` -- flag any entry that has recurred
    3+ times and is not yet in \`.claude/rules/workspace-patterns.md\`.
    If \`workspace-patterns.md\` has no rules yet and 5+ resources exist in \`src/\`,
    suggest adding patterns. Surface suggestions only -- do not auto-generate.
@@ -46301,7 +46316,7 @@ Each step reports its result. Steps 1-8 run even if step 0 is skipped.
 
 ### \`/meta deploy\` -- Full Deploy Pipeline
 
-0. Read \`reference/deployment/command-view.mdx\` -- understand the Command View
+0. Read \`reference/deployment/command-center.mdx\` -- understand the Command View
    model, relationship declarations, and what deploy-time validation checks.
    This context is essential for diagnosing validation failures in steps 1-2.
 1. Run \`elevasis-sdk check\` (validation)
@@ -46311,18 +46326,18 @@ Each step reports its result. Steps 1-8 run even if step 0 is skipped.
 5. Run \`elevasis-sdk deploy\`
 6. \`docs/project-map.mdx\` is auto-regenerated by deploy (no manual bump needed)
 7. Verify deployment via platform
-8. Update \`memory/deployment-state.md\` with count, timestamp, inventory
+8. Update \`.claude/memory/deployment-state.md\` with count, timestamp, inventory
 9. If git configured and remote exists: optionally push
 
 Each step reports its result. Pipeline stops on failure with suggested fix.
-If validation fails with relationship errors, re-read \`reference/deployment/command-view.mdx\`
+If validation fails with relationship errors, re-read \`reference/deployment/command-center.mdx\`
 for the enforcement model and common fixes.
 
 ### \`/meta health\` -- Execution Debugging
 
 Diagnose runtime failures and environment issues:
 - Show recent executions with status (completed/failed)
-- For failed executions: analyze logs, cross-reference with memory/errors/
+- For failed executions: analyze logs, cross-reference with .claude/memory/errors/
 - Check resource deployment status (deployed, outdated, never deployed)
 - Verify environment: API key valid, credentials accessible, DB connected
 
@@ -46829,7 +46844,7 @@ This file is yours. The other \`.claude/rules/\` files are SDK-owned and updated
 
 ## When to Add a Rule
 
-- An error has recurred 3+ times (CLAUDE.md instructs you to promote from \`memory/errors/\`)
+- An error has recurred 3+ times (CLAUDE.md instructs you to promote from \`.claude/memory/errors/\`)
 - A pattern appears across 3+ resources and is worth documenting for consistency
 - A naming or structural convention exists that future sessions would likely get wrong
 

package/dist/index.d.ts

@@ -3124,6 +3124,14 @@ declare class ResourceRegistry {
      * @returns Remote config or null if org has no remote resources
      */
     getAnyRemoteConfig(orgName: string): RemoteOrgConfig | null;
+    /**
+     * Get statistics about remotely-deployed resources
+     * Used by the health endpoint for platform-wide deployment visibility.
+     */
+    getRemoteStats(): {
+        activeOrgs: number;
+        totalResources: number;
+    };
     /**
      * Get triggers for an organization
      * @param organizationName - Organization name

package/dist/index.js

@@ -3410,6 +3410,21 @@ var ResourceRegistry = class {
     }
     return null;
   }
+  /**
+   * Get statistics about remotely-deployed resources
+   * Used by the health endpoint for platform-wide deployment visibility.
+   */
+  getRemoteStats() {
+    const orgs = /* @__PURE__ */ new Set();
+    for (const key of this.remoteResources.keys()) {
+      const orgName = key.split("/")[0];
+      orgs.add(orgName);
+    }
+    return {
+      activeOrgs: orgs.size,
+      totalResources: this.remoteResources.size
+    };
+  }
   // ============================================================================
   // Resource Manifest Accessors
   // ============================================================================

package/dist/templates.js

@@ -257,16 +257,16 @@ proactivity -- to their assessed levels.
 
 | Resource | Location | When to Load |
 | --- | --- | --- |
-| Workspace concepts | \`reference/concepts/index.mdx\` | User asks "what is...?" or needs conceptual grounding |
+| Workspace concepts | \`reference/concepts.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 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 |
+| CLI reference | \`reference/cli.mdx\` | Running execution/platform operations |
+| Credential model | \`reference/platform-tools/index.mdx\` | Setting up integrations or credential security |
+| Interaction guidance | \`reference/framework/interaction-guidance.mdx\` | Unsure how to adapt for a skill combination |
 | Error history | \`.claude/memory/errors/index.md\` | Debugging errors, checking past fixes |
-| Command View model | \`reference/deployment/command-view.mdx\` | Deploying or building resources that invoke other resources |
-| Command Center UI reference | \`reference/deployment/command-center-ui.mdx\` | User asks about post-deployment UI or Command Center navigation |
-| SDK error reference | \`reference/troubleshooting/common-errors.mdx\` | Unknown error not in workspace memory |
+| Command View model | \`reference/deployment/command-center.mdx\` | Deploying or building resources that invoke other resources |
+| Command Center UI reference | \`reference/deployment/command-center.mdx\` | User asks about post-deployment UI or Command Center navigation |
+| SDK error reference | \`reference/troubleshooting.mdx\` | Unknown error not in workspace memory |
 | Project map | \`docs/project-map.mdx\` | Session start, project orientation |
 | Resource inventory | \`docs/resource-map.mdx\` | Finding a specific resource by name or ID |
 | Project priorities | \`docs/priorities.mdx\` | Deciding what to work on next |
@@ -292,7 +292,7 @@ Use \`pnpm exec elevasis-sdk\` for runtime commands (resolves the locally instal
 - \`pnpm exec elevasis-sdk execution <resource-id> <execution-id>\` -- inspect execution detail
 
 Organization is derived from your API key -- no org prefix needed in the resource ID.
-For full CLI reference: \`reference/cli/index.mdx\`
+For full CLI reference: \`reference/cli.mdx\`
 
 ## Rules
 
@@ -307,8 +307,8 @@ SDK patterns (imports, source structure, platform tools) are auto-loaded from
 
 When an error occurs:
 1. Check \`.claude/memory/errors/\` first for past fixes
-2. If new, check \`reference/troubleshooting/common-errors.mdx\`
-3. After resolving, record in \`memory/errors/\` with context and fix
+2. If new, check \`reference/troubleshooting.mdx\`
+3. After resolving, record in \`.claude/memory/errors/\` with context and fix
 4. If an error recurs 3+ times, add a rule to \`.claude/rules/workspace-patterns.md\`${ctx.hasUI ? `
 
 ### UI App (\`ui/\`)
@@ -340,7 +340,7 @@ based on what you find.
 - When growth is observed, note it in the skills.md Growth Log.
 
 For detailed per-dimension adaptation rules, read
-\`reference/developer/interaction-guidance.mdx\`.
+\`reference/framework/interaction-guidance.mdx\`.
 
 ## Commands
 
@@ -349,7 +349,7 @@ For detailed per-dimension adaptation rules, read
 | \`/meta\` | Project lifecycle: init, status, fix, deploy, health |
 | \`/docs\` | Browse, create, and verify permanent documentation |
 | \`/work\` | Task tracking: create, save, resume, complete |
-| \`/tutorial\` | Progressive learning path (7 core lessons + 9 modules) |
+| \`/tutorial\` | Progressive learning path (21 items across 4 sections) |
 
 ## Skills
 
@@ -382,7 +382,7 @@ Do not store in \`.claude/memory/\`:
 
 ### Structure
 
-- \`memory/index.md\` is the root -- maps to topic files and subdirectories
+- \`.claude/memory/index.md\` is the root -- maps to topic files and subdirectories
 - Every subdirectory has its own \`index.md\` mapping to children
 - Start at the root index and drill down
 - When a file outgrows a single document, split into a subdirectory
@@ -406,14 +406,14 @@ Read \`.claude/memory/profile/skills.md\` first. The \`automation\` skill level
 controls which docs you load and which lesson variant you deliver.
 
 **automation: none**
-- Load from \`reference/concepts/index.mdx\`: Glossary, What is a Workflow,
+- Load from \`reference/concepts.mdx\`: Glossary, What is a Workflow,
   Platform Tools Overview only. Skip Zod, Execution Model, Design Decisions.
-- Load \`reference/deployment/command-center-ui.mdx\` for UI-first teaching.
+- Load \`reference/deployment/command-center.mdx\` for UI-first teaching.
 - Do NOT load \`reference/resources/patterns.mdx\` or
   \`reference/platform-tools/adapters.mdx\` during core lessons.
 
 **automation: low-code**
-- Load all sections of \`reference/concepts/index.mdx\`.
+- Load all sections of \`reference/concepts.mdx\`.
 - Load \`reference/resources/patterns.mdx\` with Zapier/Make mapping in mind.
 - Load \`reference/platform-tools/adapters.mdx\` on-demand (when tools are used).
 
@@ -501,7 +501,7 @@ Each lesson follows this flow:
 
 When automation is none:
 Skip the file tour. Start with what Elevasis does for their business -- use analogies
-from \`reference/developer/interaction-guidance.mdx\` (recipe, assembly line, kitchen
+from \`reference/framework/interaction-guidance.mdx\` (recipe, assembly line, kitchen
 appliance). Explain deployment plainly: "You write the recipe here, then deploy it so
 it's live." Deploy the starter echo workflow (\`elevasis-sdk check\` + \`elevasis-sdk deploy\`),
 THEN tour the Command Center so the user sees populated pages, not empty ones. Tour:
@@ -749,14 +749,14 @@ Each module follows this flow:
 ## Modules
 
 **Module: hitl -- Human-in-the-Loop**
-Read: \`reference/deployment/command-center-ui.mdx\` (Command Queue section).
+Read: \`reference/deployment/command-center.mdx\` (Command Queue section).
 Build: Add an approval gate using \`approval.requestApproval()\`. Test full lifecycle:
 trigger, see pending in Command Queue, approve/reject, observe resume.
 Key concepts: approval adapter, pending state, Command Queue UI, resume on decision.
 Verify: Trigger workflow, open Command Queue, approve, confirm completion.
 
 **Module: schedules -- Task Scheduling**
-Read: \`reference/deployment/command-center-ui.mdx\` (Task Scheduler section).
+Read: \`reference/deployment/command-center.mdx\` (Task Scheduler section).
 Build: Create all three schedule types (Recurring cron, Relative delay, Absolute
 datetime). Use \`scheduler\` adapter for in-workflow scheduling.
 Key concepts: schedule types, cron syntax, scheduler adapter, Task Scheduler UI.
@@ -770,7 +770,7 @@ Verify: Run workflow, check notification in Command Center, confirm email receiv
 
 **Module: integrations -- Real-World Integrations**
 Read: \`reference/platform-tools/index.mdx\`, \`reference/platform-tools/adapters.mdx\`,
-\`reference/security/credentials.mdx\`.
+\`reference/platform-tools/index.mdx\`.
 Build: Pick a real integration adapter based on user's goals (read \`identity.md\`).
 Set up credential (OAuth via UI, API key via CLI). Build end-to-end integration workflow.
 Key concepts: adapter pattern, credential scoping, error handling for external calls.
@@ -779,7 +779,7 @@ handling with invalid credential.
 
 **Module: error-handling -- Error Handling Mastery**
 Read: \`reference/resources/patterns.mdx\` (error handling),
-\`reference/troubleshooting/common-errors.mdx\`.
+\`reference/troubleshooting.mdx\`.
 Build: Create a workflow demonstrating all three error types. Add try/catch,
 \`context.logger\`, and error recovery.
 Key concepts: ExecutionError, PlatformToolError, ToolingError, recovery patterns.
@@ -795,7 +795,7 @@ Key concepts: context.store, context.logger, domain organization, schema depth.
 Verify: Run workflow, confirm store values in step output, check logs in Execution Logs.
 
 **Module: composition -- Resource Composition**
-Read: \`reference/deployment/command-view.mdx\`, \`reference/resources/patterns.mdx\`.
+Read: \`reference/deployment/command-center.mdx\`, \`reference/resources/patterns.mdx\`.
 Build: Create two workflows where the first triggers the second using
 \`execution.trigger()\`. Declare the relationship.
 Key concepts: execution.trigger, relationship declarations, Command View graph edges.
@@ -943,7 +943,7 @@ Last Session: {today's date}
 \`\`\`
 
 Update rules:
-- \`Current\`: free-form, e.g. "4: Using Platform Tools" or "M:integrations" or "20: Rules, Memory, and Customization"
+- \`Current\`: free-form, e.g. "7: Using Platform Tools" or "M:integrations" or "20: Rules, Memory, and Customization"
 - \`Last Session\`: update to today's date on each \`/tutorial\` invocation
 - Completed Lessons: add a row when any numbered item (1-10, 20-21) finishes
 - Completed Modules: add a row when any module (items 11-19) finishes
@@ -1039,9 +1039,9 @@ by the \`<!-- initialized: false -->\` flag in CLAUDE.md, or run manually.
    - Create \`.claude/memory/profile/preferences.md\` (verbosity, guidance)
 
 4. **Git check**
-   - If \`.git/\` exists: note git is configured in memory/profile/preferences.md
+   - If \`.git/\` exists: note git is configured in .claude/memory/profile/preferences.md
    - If \`.git/\` does not exist: suggest \`git init\` and optionally GitHub
-   - If git remote exists: note remote URL in memory/profile/preferences.md
+   - If git remote exists: note remote URL in .claude/memory/profile/preferences.md
 
 5. **Verify project**
    Run \`elevasis-sdk check\` to confirm the starter resource is valid.
@@ -1062,9 +1062,9 @@ by the \`<!-- initialized: false -->\` flag in CLAUDE.md, or run manually.
 
 Display a project health summary:
 1. Template version (from elevasis.config.ts) and installed SDK version (from package.json). Suggest \`elevasis-sdk update\` to check for updates
-3. Profile summary (from memory/profile/skills.md)
-4. Quick drift check: count of missing managed files, missing gitignore entries
-5. Last deployment status (from memory/deployment-state.md if it exists)
+2. Profile summary (from .claude/memory/profile/skills.md)
+3. Quick drift check: count of missing managed files, missing gitignore entries
+4. Last deployment status (from .claude/memory/deployment-state.md if it exists)
 
 ### \`/meta fix\` -- Maintenance and Upgrade
 
@@ -1082,9 +1082,9 @@ Detect and repair all drift. Optionally upgrades the SDK first.
 3. **CLAUDE.md sections:** Add missing sections in correct position
 4. **Memory structure:** Create base structure if missing, then verify index consistency.
    If \`.claude/memory/\` does not exist or is empty:
-   - Create \`memory/index.md\` (root index with placeholder entries)
-   - Create \`memory/errors/index.md\` (error category summary, empty tables)
-   - Create \`memory/errors/deploy.md\`, \`memory/errors/runtime.md\`, \`memory/errors/typescript.md\`
+   - Create \`.claude/memory/index.md\` (root index with placeholder entries)
+   - Create \`.claude/memory/errors/index.md\` (error category summary, empty tables)
+   - Create \`.claude/memory/errors/deploy.md\`, \`.claude/memory/errors/runtime.md\`, \`.claude/memory/errors/typescript.md\`
    If memory exists, verify: every file referenced in an index exists; every file
    without an index entry gets one added; broken references are removed.
 5. **Documentation verification:** For each file in docs/:
@@ -1095,7 +1095,7 @@ Detect and repair all drift. Optionally upgrades the SDK first.
    e. Report discrepancies with suggested fixes
    Note: \`/docs verify\` is available for standalone interactive verification outside this pipeline.
 6. **Settings consistency:** Verify expected fields
-7. **Rules health:** Scan \`memory/errors/\` -- flag any entry that has recurred
+7. **Rules health:** Scan \`.claude/memory/errors/\` -- flag any entry that has recurred
    3+ times and is not yet in \`.claude/rules/workspace-patterns.md\`.
    If \`workspace-patterns.md\` has no rules yet and 5+ resources exist in \`src/\`,
    suggest adding patterns. Surface suggestions only -- do not auto-generate.
@@ -1108,7 +1108,7 @@ Each step reports its result. Steps 1-8 run even if step 0 is skipped.
 
 ### \`/meta deploy\` -- Full Deploy Pipeline
 
-0. Read \`reference/deployment/command-view.mdx\` -- understand the Command View
+0. Read \`reference/deployment/command-center.mdx\` -- understand the Command View
    model, relationship declarations, and what deploy-time validation checks.
    This context is essential for diagnosing validation failures in steps 1-2.
 1. Run \`elevasis-sdk check\` (validation)
@@ -1118,18 +1118,18 @@ Each step reports its result. Steps 1-8 run even if step 0 is skipped.
 5. Run \`elevasis-sdk deploy\`
 6. \`docs/project-map.mdx\` is auto-regenerated by deploy (no manual bump needed)
 7. Verify deployment via platform
-8. Update \`memory/deployment-state.md\` with count, timestamp, inventory
+8. Update \`.claude/memory/deployment-state.md\` with count, timestamp, inventory
 9. If git configured and remote exists: optionally push
 
 Each step reports its result. Pipeline stops on failure with suggested fix.
-If validation fails with relationship errors, re-read \`reference/deployment/command-view.mdx\`
+If validation fails with relationship errors, re-read \`reference/deployment/command-center.mdx\`
 for the enforcement model and common fixes.
 
 ### \`/meta health\` -- Execution Debugging
 
 Diagnose runtime failures and environment issues:
 - Show recent executions with status (completed/failed)
-- For failed executions: analyze logs, cross-reference with memory/errors/
+- For failed executions: analyze logs, cross-reference with .claude/memory/errors/
 - Check resource deployment status (deployed, outdated, never deployed)
 - Verify environment: API key valid, credentials accessible, DB connected
 

package/package.json

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