@elevasis/sdk 0.8.5 → 0.8.6

package/dist/cli.cjs

@@ -43883,7 +43883,7 @@ function wrapAction(commandName, fn) {
 // package.json
 var package_default = {
   name: "@elevasis/sdk",
-  version: "0.8.5",
+  version: "0.8.6",
   description: "SDK for building Elevasis organization resources",
   type: "module",
   bin: {
@@ -44125,7 +44125,7 @@ async function generateProjectMap(org) {
     "",
     "# Project Map",
     "",
-    "> Auto-generated by `elevasis-sdk deploy` and `/meta fix`. Do not edit manually.",
+    "> Auto-generated by `elevasis-sdk deploy` and `/fix`. Do not edit manually.",
     "",
     "## Project Overview",
     "",
@@ -45233,7 +45233,7 @@ var import_path3 = require("path");
 var import_promises2 = require("fs/promises");
 
 // src/cli/commands/templates/core/workspace.ts
-var TEMPLATE_VERSION = 32;
+var TEMPLATE_VERSION = 34;
 function configTemplate() {
   return `import type { ElevasConfig } from '@elevasis/sdk'
 
@@ -45567,7 +45567,7 @@ function claudeMdTemplate(ctx = {}) {
 At the start of every session:
 
 0. Check the \`<!-- initialized: ... -->\` flag at the top of this file.
-   If \`false\`, read \`.claude/commands/meta.md\` and run the \`/meta init\` flow.
+   If \`false\`, read \`.claude/commands/init.md\` and run the \`/init\` flow.
    After initialization completes, change the flag to \`<!-- initialized: true -->\`.
    If \`true\`, proceed with steps below.
 1. Read \`.claude/memory/profile/skills.md\` -- adapt all responses to the user's
@@ -45575,8 +45575,8 @@ 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 fix\`.
-4. If \`.claude/memory/\` does not exist, suggest \`/meta init\`.
+   in \`elevasis.config.ts\`. If newer, notify and suggest \`/fix\`.
+4. If \`.claude/memory/\` does not exist, suggest \`/init\`.
 5. If user Platform Navigation level is none (from skills.md) and
    \`.claude/memory/tutorial-progress.md\` does not exist, suggest \`/tutorial\`.
    If tutorial-progress.md exists and Phase is not complete, mention that the
@@ -45690,7 +45690,10 @@ For detailed per-dimension adaptation rules, read
 
 | Command | Purpose |
 | --- | --- |
-| \`/meta\` | Project lifecycle: init, status, fix, deploy, health |
+| \`/init\` | First-run workspace setup and competency assessment |
+| \`/status\` | Project health dashboard |
+| \`/fix\` | Maintenance, drift repair, and SDK upgrade |
+| \`/deploy\` | Full deploy pipeline (validate \u2192 deploy \u2192 verify) |
 | \`/docs\` | Browse, create, and verify permanent documentation |
 | \`/tutorial\` | Progressive learning path (21 items across 4 sections) |
 
@@ -45702,6 +45705,7 @@ Skills auto-trigger based on conversation context. You do not need to invoke the
 | --- | --- |
 | \`work\` | You say /work, ask to track or save progress across sessions, ask what you were working on, want to create/resume/complete a task doc, or say you are done for today. Also proactively save when conversation is heavy or 2+ steps completed |
 | \`creds\` | You mention credentials, API keys, secrets, webhook secrets, or setting up integrations |
+| \`diagnostics\` | An execution fails, user asks why something failed, user mentions runtime errors, or agent observes a failed execution |
 
 ## Maintaining Memory
 
@@ -45789,7 +45793,7 @@ Elevasis Tutorial
 INTRODUCTION                                       0/4
   1  Welcome & Orientation                         [ ]
   2  How This Workspace Works                      [ ]
-  3  The /meta Command                             [ ]
+  3  Project Commands (/init, /status, /fix, /deploy)          [ ]
   4  /work and /docs                               [ ]
 
 CORE CONCEPTS                                      0/6
@@ -45867,7 +45871,7 @@ When automation is none:
 "This workspace comes with a built-in assistant that knows your project, your tools,
 and your goals. Let me show you how it's set up." Open CLAUDE.md and explain in
 plain terms: it's the agent's instruction sheet. Point out the commands in the
-Commands table. Show /meta, /tutorial. Explain the work and creds skills as
+Commands table. Show /status, /tutorial. Explain the work and creds skills as
 "the assistant automatically helps when you mention tasks or API keys." Tour the memory folder
 at a high level -- "this is where the agent stores what it learns about your project."
 Verify: Ask the user a question about their business goal and show how the agent
@@ -45880,7 +45884,7 @@ session start, how the navigation table works, what the Skills section means.
 Explain the three commands briefly and the two auto-triggering skills (work, creds). Show that the agent has memory: open
 \`.claude/memory/profile/skills.md\` and show their own profile -- "every session,
 the agent reads this and adapts." Explain the initialized flag.
-Verify: Run /meta to see project status.
+Verify: Run /status to see project status.
 Observation focus: memory system concept, session initialization flow.
 
 When automation is custom:
@@ -45888,37 +45892,39 @@ Read CLAUDE.md in full. Explain the session initialization sequence: CLAUDE.md -
 navigation table -> memory files -> context loading. Walk through: Commands section
 (3 commands + work and creds skills), Rules section (auto-loaded based on file paths), Skills
 section (auto-triggered by content patterns). Point out the initialized flag and
-explain how /meta init set it.
-Verify: Run /meta to see project status; observe which fields it reports.
+explain how /init set it.
+Verify: Run /status to see project status; observe which fields it reports.
 Observation focus: initialization model, command-vs-rule-vs-skill distinction.
 
-**Item 3: The /meta Command**
+**Item 3: Project Commands (/init, /status, /fix, /deploy)**
 
 When automation is none:
-"Think of /meta as your project dashboard -- it shows what's healthy and what needs
-attention." Run /meta (no arguments) and narrate the output in plain language: what
-each field means. Explain /meta fix as "the agent tidies up and applies updates."
-Explain /meta deploy as "the agent publishes your changes in one step." Briefly note
-/meta health shows what happened when something goes wrong.
-Verify: Run /meta (no arguments). Narrate the output together.
+"Think of /status as your project dashboard -- it shows what's healthy and what needs
+attention." Run /status and narrate the output in plain language: what each field means.
+Explain /fix as "the agent tidies up and applies updates."
+Explain /deploy as "the agent publishes your changes in one step." Mention the
+diagnostics skill: "If something goes wrong, the assistant automatically investigates."
+Verify: Run /status. Narrate the output together.
 Observation focus: project lifecycle concept, dashboard reading.
 
 When automation is low-code:
-Show all /meta operations with their purpose. Map to familiar concepts: /meta fix is
-like "repair this Zap" in Zapier; /meta deploy is a one-command publish pipeline.
-Walk through the /meta (no-args) output: template version (SDK template your workspace
-uses), SDK version (installed package), profile summary, drift check.
-Verify: Run /meta and interpret each field together.
+Show all project commands with their purpose. Map to familiar concepts: /fix is
+like "repair this Zap" in Zapier; /deploy is a one-command publish pipeline.
+Walk through /status output: template version (SDK template your workspace
+uses), SDK version (installed package), profile summary, drift check. Mention the
+diagnostics skill auto-triggers on execution failures.
+Verify: Run /status and interpret each field together.
 Observation focus: deploy pipeline understanding, version tracking.
 
 When automation is custom:
-Read \`.claude/commands/meta.md\`. Walk through each operation: init (first-run setup
-with assessment), (no-args) (status dashboard), fix (drift repair + SDK upgrade +
-rules health), deploy (7-step pipeline: check, typecheck, docs, git, deploy,
-project-map, verify), health (runtime diagnostics). Explain the merge strategy for
-CLAUDE.md and commands. Note the template access model: templates read from
-@elevasis/sdk/templates subpath.
-Verify: Run /meta to see project status. Identify what a version mismatch looks like.
+Read each command file in \`.claude/commands/\`: init.md (/init -- first-run setup
+with assessment), status.md (/status -- health dashboard), fix.md (/fix -- drift
+repair + SDK upgrade + rules health), deploy.md (/deploy -- 9-step pipeline: check,
+typecheck, docs, git, deploy, project-map, verify, state, push). Explain the
+diagnostics skill (auto-triggered on execution failures for runtime debugging).
+Explain the merge strategy for CLAUDE.md and commands. Note the template access
+model: templates read from @elevasis/sdk/templates subpath.
+Verify: Run /status to see project status. Identify what a version mismatch looks like.
 Observation focus: full lifecycle coverage, pipeline internals.
 
 **Item 4: /work and /docs**
@@ -45958,7 +45964,7 @@ Then read \`.claude/commands/docs.md\`. Cover /docs operations:
 /docs (default): browse permanent docs/, categorized with read-only auto-generated files
 separate; /docs create: interview-driven, resource-aware doc creation from src/ code
 analysis; /docs verify: cross-references resource IDs, schema fields, platform tools in
-docs against src/ -- standalone analog of /meta fix step 5.
+docs against src/ -- standalone analog of /fix step 5.
 Explain the relationship: /work owns docs/in-progress/ (task lifecycle), completing a task
 moves docs to permanent location, /docs browses and verifies what's there.
 Verify: Create a task via /work, make progress, observe auto-save, then run /work complete
@@ -46205,21 +46211,21 @@ Observation focus: MANAGED vs INIT_ONLY lifecycle, rule authoring, memory layout
 
 When automation is none:
 "When Elevasis SDK releases updates, the assistant can apply them to your workspace
-automatically. You don't have to redo your customizations." Explain /meta fix as
+automatically. You don't have to redo your customizations." Explain /fix as
 the command that applies updates. Skip technical file classification details.
 Show \`docs/project-map.mdx\` briefly: "This is an auto-generated map of everything
 in your project -- the agent uses it for navigation."
-Verify: Run /meta fix (or explain what it would do). Check \`docs/project-map.mdx\`.
+Verify: Run /fix (or explain what it would do). Check \`docs/project-map.mdx\`.
 Next steps: point to reference docs in docs/, encourage using /work for new tasks.
 Observation focus: update model concept, project map as navigation aid.
 
 When automation is low-code:
 Explain MANAGED (auto-updated by elevasis-sdk update) vs INIT_ONLY (set once, yours).
-Show how /meta fix applies SDK updates with conflict handling: "If a file changed,
+Show how /fix applies SDK updates with conflict handling: "If a file changed,
 it shows you both versions and lets you decide."
 Show \`docs/project-map.mdx\` and explain what it contains: resources, commands,
 rules, memory index. Note that deploy auto-regenerates it.
-Verify: Read \`elevasis.config.ts\` templateVersion. Compare to the running SDK version from /meta.
+Verify: Read \`elevasis.config.ts\` templateVersion. Compare to the running SDK version from /status.
 Observation focus: update workflow, project map freshness.
 
 When automation is custom:
@@ -46231,7 +46237,7 @@ file, read template from @elevasis/sdk/templates, merge preserving customization
 Explain the project map: auto-generated by deploy, contains resource inventory,
 command list, rule list, memory index.
 Next steps: explore reference docs, use /work for complex tasks, build custom rules.
-Verify: Compare elevasis.config.ts templateVersion with output of /meta. Identify any drift.
+Verify: Compare elevasis.config.ts templateVersion with output of /status. Identify any drift.
 Observation focus: full template lifecycle, conflict resolution pattern.
 
 ## Adaptation Rules
@@ -46300,8 +46306,8 @@ Update rules:
 Backward-compatible: missing Completed Modules treated as empty. Old files with Completed MF Lessons: map entries to items 2-4 and 20-21 by lesson title match.
 `;
 }
-function claudeMetaCommandTemplate() {
-  return `# /meta command
+function claudeInitCommandTemplate() {
+  return `# /init command
 
 You are a project management assistant for this Elevasis workspace.
 
@@ -46311,9 +46317,7 @@ Read \`elevasis.config.ts\` to get the current \`templateVersion\`.
 Read \`package.json\` to get the installed \`@elevasis/sdk\` version.
 Read \`.claude/memory/index.md\` if it exists for project state.
 
-## Operations
-
-### \`/meta init\` -- First-Run Setup
+## Operation
 
 Guided setup for a freshly scaffolded workspace. Triggered automatically
 by the \`<!-- initialized: false -->\` flag in CLAUDE.md, or run manually.
@@ -46404,16 +46408,40 @@ by the \`<!-- initialized: false -->\` flag in CLAUDE.md, or run manually.
 7. **Update flag**
    Change \`<!-- initialized: false -->\` to \`<!-- initialized: true -->\`
    in CLAUDE.md.
+`;
+}
+function claudeStatusCommandTemplate() {
+  return `# /status command
 
-### \`/meta\` (no arguments) -- Project Status
+You are a project management assistant for this Elevasis workspace.
+
+## Context
+
+Read \`elevasis.config.ts\` to get the current \`templateVersion\`.
+Read \`package.json\` to get the installed \`@elevasis/sdk\` version.
+Read \`.claude/memory/index.md\` if it exists for project state.
+
+## Operation
 
 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
 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)
+`;
+}
+function claudeFixCommandTemplate() {
+  return `# /fix command
 
-### \`/meta fix\` -- Maintenance and Upgrade
+You are a project management assistant for this Elevasis workspace.
+
+## Context
+
+Read \`elevasis.config.ts\` to get the current \`templateVersion\`.
+Read \`package.json\` to get the installed \`@elevasis/sdk\` version.
+Read \`.claude/memory/index.md\` if it exists for project state.
+
+## Operation
 
 Detect and repair all drift. Optionally upgrades the SDK first.
 
@@ -46453,7 +46481,30 @@ Detect and repair all drift. Optionally upgrades the SDK first.
 
 Each step reports its result. Steps 1-8 run even if step 0 is skipped.
 
-### \`/meta deploy\` -- Full Deploy Pipeline
+## Merge Strategy
+
+- **CLAUDE.md:** Add new sections in correct position. Preserve customizations.
+- **Commands:** Usually additive. Show diff for changes.
+- **.gitignore:** Append-only -- never remove existing entries.
+
+## Template Access
+
+The agent reads current templates from the installed SDK:
+\`@elevasis/sdk/templates\` subpath exports all template functions.
+`;
+}
+function claudeDeployCommandTemplate() {
+  return `# /deploy command
+
+You are a project management assistant for this Elevasis workspace.
+
+## Context
+
+Read \`elevasis.config.ts\` to get the current \`templateVersion\`.
+Read \`package.json\` to get the installed \`@elevasis/sdk\` version.
+Read \`.claude/memory/index.md\` if it exists for project state.
+
+## Operation
 
 0. Read \`reference/deployment/command-center.mdx\` -- understand the Command View
    model, relationship declarations, and what deploy-time validation checks.
@@ -46471,25 +46522,38 @@ Each step reports its result. Steps 1-8 run even if step 0 is skipped.
 Each step reports its result. Pipeline stops on failure with suggested fix.
 If validation fails with relationship errors, re-read \`reference/deployment/command-center.mdx\`
 for the enforcement model and common fixes.
+`;
+}
+function claudeDiagnosticsSkillTemplate() {
+  return `---
+name: diagnostics
+description: "Execution diagnostics and runtime debugging. TRIGGER when: an execution fails, user asks why something failed or errored, user mentions runtime errors or unexpected behavior, or agent observes a failed execution result. DO NOT TRIGGER when: user is discussing errors in code (type errors, lint errors) or build failures -- those are development issues, not runtime diagnostics."
+---
 
-### \`/meta health\` -- Execution Debugging
+# Execution Diagnostics
 
-Diagnose runtime failures and environment issues:
-- Show recent executions with status (completed/failed)
-- 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
+You are a runtime diagnostics assistant for this Elevasis workspace.
 
-## Merge Strategy
+## Context
 
-- **CLAUDE.md:** Add new sections in correct position. Preserve customizations.
-- **Commands:** Usually additive. Show diff for changes.
-- **.gitignore:** Append-only -- never remove existing entries.
+Read \`.claude/memory/errors/index.md\` if it exists for past error patterns.
+Read \`.claude/memory/deployment-state.md\` if it exists for deployment context.
 
-## Template Access
+## When Triggered
 
-The agent reads current templates from the installed SDK:
-\`@elevasis/sdk/templates\` subpath exports all template functions.
+Diagnose runtime failures and environment issues:
+
+1. **Identify the failure** -- get the execution ID and resource ID from the error or conversation context
+2. **Pull execution details** -- run \`elevasis-sdk execution <resource-id> <execution-id>\` to get logs
+3. **Cross-reference** -- check \`.claude/memory/errors/\` for known patterns
+4. **Check deployment status** -- is the resource deployed? Is it the latest version?
+5. **Verify environment** -- API key valid, required credentials accessible
+6. **Diagnose root cause** -- analyze logs, identify the failing step, trace the error
+7. **Record** -- save new error patterns to \`.claude/memory/errors/\` with context and fix
+8. **Suggest fix** -- propose a concrete fix or next step
+
+If the error has occurred before (found in memory/errors/), apply the known fix directly.
+If it recurs 3+ times, suggest adding a rule to \`.claude/rules/workspace-patterns.md\`.
 `;
 }
 function claudeWorkSkillTemplate() {
@@ -46782,7 +46846,7 @@ Leaves technical prose to the user. Concise.
 
 ### \`verify [file?]\` -- Interactive Documentation Verification
 
-Standalone interactive version of \`/meta fix\` step 5. Checks docs against current code.
+Standalone interactive version of \`/fix\` step 5. Checks docs against current code.
 
 **Without argument -- verify all:**
 
@@ -46837,7 +46901,7 @@ ambiguous ones.
 - Touch \`docs/in-progress/\` -- \`/work\`'s territory
 - Handle task lifecycle (planned / in-progress / complete)
 - Edit \`project-map.mdx\` or \`resource-map.mdx\` -- auto-generated, read-only
-- Replace \`/meta fix\` step 5 -- it supplements it with interactivity
+- Replace \`/fix\` step 5 -- it supplements it with interactivity
 `;
 }
 function claudeCredsSkillTemplate() {
@@ -47082,7 +47146,7 @@ It is NOT for instructions (commands), reference docs, or templates.
 }
 function claudeProjectMapRuleTemplate() {
   return `---
-description: Project map conventions -- auto-generated, do not edit, maintained by deploy and /meta fix
+description: Project map conventions -- auto-generated, do not edit, maintained by deploy and /fix
 paths:
   - docs/project-map.mdx
   - docs/resource-map.mdx
@@ -47092,8 +47156,8 @@ paths:
 
 - \`docs/project-map.mdx\` and \`docs/resource-map.mdx\` are fully auto-generated by \`elevasis-sdk deploy\`
 - Do not edit either file manually -- changes are overwritten on next deploy
-- \`/meta fix\` step 8 checks for drift and patches the map
-- If a new command, rule, skill, or memory file is added, run \`/meta fix\` or \`elevasis-sdk deploy\` to update
+- \`/fix\` step 8 checks for drift and patches the map
+- If a new command, rule, skill, or memory file is added, run \`/fix\` or \`elevasis-sdk deploy\` to update
 `;
 }
 function claudeTaskTrackingRuleTemplate() {
@@ -47586,7 +47650,11 @@ function getManagedTemplates(ctx = {}) {
     ".claude/hooks/post-edit-validate.mjs": claudePostEditValidateHookTemplate,
     ".claude/hooks/tool-failure-recovery.mjs": claudeToolFailureRecoveryHookTemplate,
     ".claude/commands/tutorial.md": claudeTutorialCommandTemplate,
-    ".claude/commands/meta.md": claudeMetaCommandTemplate,
+    ".claude/commands/init.md": claudeInitCommandTemplate,
+    ".claude/commands/status.md": claudeStatusCommandTemplate,
+    ".claude/commands/fix.md": claudeFixCommandTemplate,
+    ".claude/commands/deploy.md": claudeDeployCommandTemplate,
+    ".claude/skills/diagnostics/SKILL.md": claudeDiagnosticsSkillTemplate,
     ".claude/skills/work/SKILL.md": claudeWorkSkillTemplate,
     ".claude/commands/docs.md": claudeDocsCommandTemplate,
     ".claude/skills/creds/SKILL.md": claudeCredsSkillTemplate,
@@ -47801,7 +47869,11 @@ var MANAGED_FILES = [
   ".claude/hooks/post-edit-validate.mjs",
   ".claude/hooks/tool-failure-recovery.mjs",
   ".claude/commands/tutorial.md",
-  ".claude/commands/meta.md",
+  ".claude/commands/init.md",
+  ".claude/commands/status.md",
+  ".claude/commands/fix.md",
+  ".claude/commands/deploy.md",
+  ".claude/skills/diagnostics/SKILL.md",
   ".claude/skills/work/SKILL.md",
   ".claude/commands/docs.md",
   ".claude/skills/creds/SKILL.md",
@@ -47872,7 +47944,11 @@ function registerInitCommand(program3) {
         ".claude/hooks/post-edit-validate.mjs": claudePostEditValidateHookTemplate(),
         ".claude/hooks/tool-failure-recovery.mjs": claudeToolFailureRecoveryHookTemplate(),
         ".claude/commands/tutorial.md": claudeTutorialCommandTemplate(),
-        ".claude/commands/meta.md": claudeMetaCommandTemplate(),
+        ".claude/commands/init.md": claudeInitCommandTemplate(),
+        ".claude/commands/status.md": claudeStatusCommandTemplate(),
+        ".claude/commands/fix.md": claudeFixCommandTemplate(),
+        ".claude/commands/deploy.md": claudeDeployCommandTemplate(),
+        ".claude/skills/diagnostics/SKILL.md": claudeDiagnosticsSkillTemplate(),
         ".claude/skills/work/SKILL.md": claudeWorkSkillTemplate(),
         ".claude/commands/docs.md": claudeDocsCommandTemplate(),
         ".claude/skills/creds/SKILL.md": claudeCredsSkillTemplate(),
@@ -48121,8 +48197,12 @@ function registerUpdateCommand(program3) {
         }
       }
       const OBSOLETE_FILES = [
-        ".claude/commands/work.md"
+        ".claude/commands/work.md",
         // v31: moved to .claude/skills/work/SKILL.md
+        ".claude/commands/meta.md",
+        // v33: split into init.md, status.md, fix.md, deploy.md, health.md
+        ".claude/commands/health.md"
+        // v33: moved to .claude/skills/diagnostics/SKILL.md
       ];
       const removed = [];
       if (!upToDate) {
@@ -48194,8 +48274,7 @@ function registerUpdateCommand(program3) {
       }
       if (flagged.length > 0) {
         console.log("");
-        console.log(source_default.gray("  Run /meta update in Claude Code to merge flagged files."));
-        console.log(source_default.gray("  Or run /meta fix to verify and repair the full framework."));
+        console.log(source_default.gray("  Run /fix in Claude Code to verify and repair the full framework."));
       }
       if (mergedUpdated.length > 0 || mergedPreserved.length > 0) {
         console.log("");

package/dist/index.d.ts

@@ -1516,7 +1516,7 @@ type Database = {
             };
             acq_lists: {
                 Row: {
-                    batch_id: string | null;
+                    batch_ids: string[];
                     completed_at: string | null;
                     created_at: string;
                     description: string | null;
@@ -1530,7 +1530,7 @@ type Database = {
                     type: string;
                 };
                 Insert: {
-                    batch_id?: string | null;
+                    batch_ids?: string[];
                     completed_at?: string | null;
                     created_at?: string;
                     description?: string | null;
@@ -1544,7 +1544,7 @@ type Database = {
                     type?: string;
                 };
                 Update: {
-                    batch_id?: string | null;
+                    batch_ids?: string[];
                     completed_at?: string | null;
                     created_at?: string;
                     description?: string | null;
@@ -3417,7 +3417,7 @@ interface AcqList {
     name: string;
     description: string | null;
     type: string;
-    batchId: string | null;
+    batchIds: string[];
     instantlyCampaignId: string | null;
     status: string;
     metadata: Record<string, unknown>;
@@ -3499,7 +3499,7 @@ interface CreateListParams {
     name: string;
     description?: string;
     type?: string;
-    batchId?: string;
+    batchIds?: string[];
     instantlyCampaignId?: string;
     status?: string;
     metadata?: Record<string, unknown>;

package/dist/templates.js

@@ -1,7 +1,7 @@
 // package.json
 
 // src/cli/commands/templates/core/workspace.ts
-var TEMPLATE_VERSION = 32;
+var TEMPLATE_VERSION = 34;
 function configTemplate() {
   return `import type { ElevasConfig } from '@elevasis/sdk'
 
@@ -208,7 +208,7 @@ function claudeMdTemplate(ctx = {}) {
 At the start of every session:
 
 0. Check the \`<!-- initialized: ... -->\` flag at the top of this file.
-   If \`false\`, read \`.claude/commands/meta.md\` and run the \`/meta init\` flow.
+   If \`false\`, read \`.claude/commands/init.md\` and run the \`/init\` flow.
    After initialization completes, change the flag to \`<!-- initialized: true -->\`.
    If \`true\`, proceed with steps below.
 1. Read \`.claude/memory/profile/skills.md\` -- adapt all responses to the user's
@@ -216,8 +216,8 @@ 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 fix\`.
-4. If \`.claude/memory/\` does not exist, suggest \`/meta init\`.
+   in \`elevasis.config.ts\`. If newer, notify and suggest \`/fix\`.
+4. If \`.claude/memory/\` does not exist, suggest \`/init\`.
 5. If user Platform Navigation level is none (from skills.md) and
    \`.claude/memory/tutorial-progress.md\` does not exist, suggest \`/tutorial\`.
    If tutorial-progress.md exists and Phase is not complete, mention that the
@@ -331,7 +331,10 @@ For detailed per-dimension adaptation rules, read
 
 | Command | Purpose |
 | --- | --- |
-| \`/meta\` | Project lifecycle: init, status, fix, deploy, health |
+| \`/init\` | First-run workspace setup and competency assessment |
+| \`/status\` | Project health dashboard |
+| \`/fix\` | Maintenance, drift repair, and SDK upgrade |
+| \`/deploy\` | Full deploy pipeline (validate \u2192 deploy \u2192 verify) |
 | \`/docs\` | Browse, create, and verify permanent documentation |
 | \`/tutorial\` | Progressive learning path (21 items across 4 sections) |
 
@@ -343,6 +346,7 @@ Skills auto-trigger based on conversation context. You do not need to invoke the
 | --- | --- |
 | \`work\` | You say /work, ask to track or save progress across sessions, ask what you were working on, want to create/resume/complete a task doc, or say you are done for today. Also proactively save when conversation is heavy or 2+ steps completed |
 | \`creds\` | You mention credentials, API keys, secrets, webhook secrets, or setting up integrations |
+| \`diagnostics\` | An execution fails, user asks why something failed, user mentions runtime errors, or agent observes a failed execution |
 
 ## Maintaining Memory
 
@@ -430,7 +434,7 @@ Elevasis Tutorial
 INTRODUCTION                                       0/4
   1  Welcome & Orientation                         [ ]
   2  How This Workspace Works                      [ ]
-  3  The /meta Command                             [ ]
+  3  Project Commands (/init, /status, /fix, /deploy)          [ ]
   4  /work and /docs                               [ ]
 
 CORE CONCEPTS                                      0/6
@@ -508,7 +512,7 @@ When automation is none:
 "This workspace comes with a built-in assistant that knows your project, your tools,
 and your goals. Let me show you how it's set up." Open CLAUDE.md and explain in
 plain terms: it's the agent's instruction sheet. Point out the commands in the
-Commands table. Show /meta, /tutorial. Explain the work and creds skills as
+Commands table. Show /status, /tutorial. Explain the work and creds skills as
 "the assistant automatically helps when you mention tasks or API keys." Tour the memory folder
 at a high level -- "this is where the agent stores what it learns about your project."
 Verify: Ask the user a question about their business goal and show how the agent
@@ -521,7 +525,7 @@ session start, how the navigation table works, what the Skills section means.
 Explain the three commands briefly and the two auto-triggering skills (work, creds). Show that the agent has memory: open
 \`.claude/memory/profile/skills.md\` and show their own profile -- "every session,
 the agent reads this and adapts." Explain the initialized flag.
-Verify: Run /meta to see project status.
+Verify: Run /status to see project status.
 Observation focus: memory system concept, session initialization flow.
 
 When automation is custom:
@@ -529,37 +533,39 @@ Read CLAUDE.md in full. Explain the session initialization sequence: CLAUDE.md -
 navigation table -> memory files -> context loading. Walk through: Commands section
 (3 commands + work and creds skills), Rules section (auto-loaded based on file paths), Skills
 section (auto-triggered by content patterns). Point out the initialized flag and
-explain how /meta init set it.
-Verify: Run /meta to see project status; observe which fields it reports.
+explain how /init set it.
+Verify: Run /status to see project status; observe which fields it reports.
 Observation focus: initialization model, command-vs-rule-vs-skill distinction.
 
-**Item 3: The /meta Command**
+**Item 3: Project Commands (/init, /status, /fix, /deploy)**
 
 When automation is none:
-"Think of /meta as your project dashboard -- it shows what's healthy and what needs
-attention." Run /meta (no arguments) and narrate the output in plain language: what
-each field means. Explain /meta fix as "the agent tidies up and applies updates."
-Explain /meta deploy as "the agent publishes your changes in one step." Briefly note
-/meta health shows what happened when something goes wrong.
-Verify: Run /meta (no arguments). Narrate the output together.
+"Think of /status as your project dashboard -- it shows what's healthy and what needs
+attention." Run /status and narrate the output in plain language: what each field means.
+Explain /fix as "the agent tidies up and applies updates."
+Explain /deploy as "the agent publishes your changes in one step." Mention the
+diagnostics skill: "If something goes wrong, the assistant automatically investigates."
+Verify: Run /status. Narrate the output together.
 Observation focus: project lifecycle concept, dashboard reading.
 
 When automation is low-code:
-Show all /meta operations with their purpose. Map to familiar concepts: /meta fix is
-like "repair this Zap" in Zapier; /meta deploy is a one-command publish pipeline.
-Walk through the /meta (no-args) output: template version (SDK template your workspace
-uses), SDK version (installed package), profile summary, drift check.
-Verify: Run /meta and interpret each field together.
+Show all project commands with their purpose. Map to familiar concepts: /fix is
+like "repair this Zap" in Zapier; /deploy is a one-command publish pipeline.
+Walk through /status output: template version (SDK template your workspace
+uses), SDK version (installed package), profile summary, drift check. Mention the
+diagnostics skill auto-triggers on execution failures.
+Verify: Run /status and interpret each field together.
 Observation focus: deploy pipeline understanding, version tracking.
 
 When automation is custom:
-Read \`.claude/commands/meta.md\`. Walk through each operation: init (first-run setup
-with assessment), (no-args) (status dashboard), fix (drift repair + SDK upgrade +
-rules health), deploy (7-step pipeline: check, typecheck, docs, git, deploy,
-project-map, verify), health (runtime diagnostics). Explain the merge strategy for
-CLAUDE.md and commands. Note the template access model: templates read from
-@elevasis/sdk/templates subpath.
-Verify: Run /meta to see project status. Identify what a version mismatch looks like.
+Read each command file in \`.claude/commands/\`: init.md (/init -- first-run setup
+with assessment), status.md (/status -- health dashboard), fix.md (/fix -- drift
+repair + SDK upgrade + rules health), deploy.md (/deploy -- 9-step pipeline: check,
+typecheck, docs, git, deploy, project-map, verify, state, push). Explain the
+diagnostics skill (auto-triggered on execution failures for runtime debugging).
+Explain the merge strategy for CLAUDE.md and commands. Note the template access
+model: templates read from @elevasis/sdk/templates subpath.
+Verify: Run /status to see project status. Identify what a version mismatch looks like.
 Observation focus: full lifecycle coverage, pipeline internals.
 
 **Item 4: /work and /docs**
@@ -599,7 +605,7 @@ Then read \`.claude/commands/docs.md\`. Cover /docs operations:
 /docs (default): browse permanent docs/, categorized with read-only auto-generated files
 separate; /docs create: interview-driven, resource-aware doc creation from src/ code
 analysis; /docs verify: cross-references resource IDs, schema fields, platform tools in
-docs against src/ -- standalone analog of /meta fix step 5.
+docs against src/ -- standalone analog of /fix step 5.
 Explain the relationship: /work owns docs/in-progress/ (task lifecycle), completing a task
 moves docs to permanent location, /docs browses and verifies what's there.
 Verify: Create a task via /work, make progress, observe auto-save, then run /work complete
@@ -846,21 +852,21 @@ Observation focus: MANAGED vs INIT_ONLY lifecycle, rule authoring, memory layout
 
 When automation is none:
 "When Elevasis SDK releases updates, the assistant can apply them to your workspace
-automatically. You don't have to redo your customizations." Explain /meta fix as
+automatically. You don't have to redo your customizations." Explain /fix as
 the command that applies updates. Skip technical file classification details.
 Show \`docs/project-map.mdx\` briefly: "This is an auto-generated map of everything
 in your project -- the agent uses it for navigation."
-Verify: Run /meta fix (or explain what it would do). Check \`docs/project-map.mdx\`.
+Verify: Run /fix (or explain what it would do). Check \`docs/project-map.mdx\`.
 Next steps: point to reference docs in docs/, encourage using /work for new tasks.
 Observation focus: update model concept, project map as navigation aid.
 
 When automation is low-code:
 Explain MANAGED (auto-updated by elevasis-sdk update) vs INIT_ONLY (set once, yours).
-Show how /meta fix applies SDK updates with conflict handling: "If a file changed,
+Show how /fix applies SDK updates with conflict handling: "If a file changed,
 it shows you both versions and lets you decide."
 Show \`docs/project-map.mdx\` and explain what it contains: resources, commands,
 rules, memory index. Note that deploy auto-regenerates it.
-Verify: Read \`elevasis.config.ts\` templateVersion. Compare to the running SDK version from /meta.
+Verify: Read \`elevasis.config.ts\` templateVersion. Compare to the running SDK version from /status.
 Observation focus: update workflow, project map freshness.
 
 When automation is custom:
@@ -872,7 +878,7 @@ file, read template from @elevasis/sdk/templates, merge preserving customization
 Explain the project map: auto-generated by deploy, contains resource inventory,
 command list, rule list, memory index.
 Next steps: explore reference docs, use /work for complex tasks, build custom rules.
-Verify: Compare elevasis.config.ts templateVersion with output of /meta. Identify any drift.
+Verify: Compare elevasis.config.ts templateVersion with output of /status. Identify any drift.
 Observation focus: full template lifecycle, conflict resolution pattern.
 
 ## Adaptation Rules
@@ -941,8 +947,8 @@ Update rules:
 Backward-compatible: missing Completed Modules treated as empty. Old files with Completed MF Lessons: map entries to items 2-4 and 20-21 by lesson title match.
 `;
 }
-function claudeMetaCommandTemplate() {
-  return `# /meta command
+function claudeInitCommandTemplate() {
+  return `# /init command
 
 You are a project management assistant for this Elevasis workspace.
 
@@ -952,9 +958,7 @@ Read \`elevasis.config.ts\` to get the current \`templateVersion\`.
 Read \`package.json\` to get the installed \`@elevasis/sdk\` version.
 Read \`.claude/memory/index.md\` if it exists for project state.
 
-## Operations
-
-### \`/meta init\` -- First-Run Setup
+## Operation
 
 Guided setup for a freshly scaffolded workspace. Triggered automatically
 by the \`<!-- initialized: false -->\` flag in CLAUDE.md, or run manually.
@@ -1045,16 +1049,40 @@ by the \`<!-- initialized: false -->\` flag in CLAUDE.md, or run manually.
 7. **Update flag**
    Change \`<!-- initialized: false -->\` to \`<!-- initialized: true -->\`
    in CLAUDE.md.
+`;
+}
+function claudeStatusCommandTemplate() {
+  return `# /status command
 
-### \`/meta\` (no arguments) -- Project Status
+You are a project management assistant for this Elevasis workspace.
+
+## Context
+
+Read \`elevasis.config.ts\` to get the current \`templateVersion\`.
+Read \`package.json\` to get the installed \`@elevasis/sdk\` version.
+Read \`.claude/memory/index.md\` if it exists for project state.
+
+## Operation
 
 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
 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)
+`;
+}
+function claudeFixCommandTemplate() {
+  return `# /fix command
 
-### \`/meta fix\` -- Maintenance and Upgrade
+You are a project management assistant for this Elevasis workspace.
+
+## Context
+
+Read \`elevasis.config.ts\` to get the current \`templateVersion\`.
+Read \`package.json\` to get the installed \`@elevasis/sdk\` version.
+Read \`.claude/memory/index.md\` if it exists for project state.
+
+## Operation
 
 Detect and repair all drift. Optionally upgrades the SDK first.
 
@@ -1094,7 +1122,30 @@ Detect and repair all drift. Optionally upgrades the SDK first.
 
 Each step reports its result. Steps 1-8 run even if step 0 is skipped.
 
-### \`/meta deploy\` -- Full Deploy Pipeline
+## Merge Strategy
+
+- **CLAUDE.md:** Add new sections in correct position. Preserve customizations.
+- **Commands:** Usually additive. Show diff for changes.
+- **.gitignore:** Append-only -- never remove existing entries.
+
+## Template Access
+
+The agent reads current templates from the installed SDK:
+\`@elevasis/sdk/templates\` subpath exports all template functions.
+`;
+}
+function claudeDeployCommandTemplate() {
+  return `# /deploy command
+
+You are a project management assistant for this Elevasis workspace.
+
+## Context
+
+Read \`elevasis.config.ts\` to get the current \`templateVersion\`.
+Read \`package.json\` to get the installed \`@elevasis/sdk\` version.
+Read \`.claude/memory/index.md\` if it exists for project state.
+
+## Operation
 
 0. Read \`reference/deployment/command-center.mdx\` -- understand the Command View
    model, relationship declarations, and what deploy-time validation checks.
@@ -1112,25 +1163,38 @@ Each step reports its result. Steps 1-8 run even if step 0 is skipped.
 Each step reports its result. Pipeline stops on failure with suggested fix.
 If validation fails with relationship errors, re-read \`reference/deployment/command-center.mdx\`
 for the enforcement model and common fixes.
+`;
+}
+function claudeDiagnosticsSkillTemplate() {
+  return `---
+name: diagnostics
+description: "Execution diagnostics and runtime debugging. TRIGGER when: an execution fails, user asks why something failed or errored, user mentions runtime errors or unexpected behavior, or agent observes a failed execution result. DO NOT TRIGGER when: user is discussing errors in code (type errors, lint errors) or build failures -- those are development issues, not runtime diagnostics."
+---
 
-### \`/meta health\` -- Execution Debugging
+# Execution Diagnostics
 
-Diagnose runtime failures and environment issues:
-- Show recent executions with status (completed/failed)
-- 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
+You are a runtime diagnostics assistant for this Elevasis workspace.
 
-## Merge Strategy
+## Context
 
-- **CLAUDE.md:** Add new sections in correct position. Preserve customizations.
-- **Commands:** Usually additive. Show diff for changes.
-- **.gitignore:** Append-only -- never remove existing entries.
+Read \`.claude/memory/errors/index.md\` if it exists for past error patterns.
+Read \`.claude/memory/deployment-state.md\` if it exists for deployment context.
 
-## Template Access
+## When Triggered
 
-The agent reads current templates from the installed SDK:
-\`@elevasis/sdk/templates\` subpath exports all template functions.
+Diagnose runtime failures and environment issues:
+
+1. **Identify the failure** -- get the execution ID and resource ID from the error or conversation context
+2. **Pull execution details** -- run \`elevasis-sdk execution <resource-id> <execution-id>\` to get logs
+3. **Cross-reference** -- check \`.claude/memory/errors/\` for known patterns
+4. **Check deployment status** -- is the resource deployed? Is it the latest version?
+5. **Verify environment** -- API key valid, required credentials accessible
+6. **Diagnose root cause** -- analyze logs, identify the failing step, trace the error
+7. **Record** -- save new error patterns to \`.claude/memory/errors/\` with context and fix
+8. **Suggest fix** -- propose a concrete fix or next step
+
+If the error has occurred before (found in memory/errors/), apply the known fix directly.
+If it recurs 3+ times, suggest adding a rule to \`.claude/rules/workspace-patterns.md\`.
 `;
 }
 function claudeWorkSkillTemplate() {
@@ -1423,7 +1487,7 @@ Leaves technical prose to the user. Concise.
 
 ### \`verify [file?]\` -- Interactive Documentation Verification
 
-Standalone interactive version of \`/meta fix\` step 5. Checks docs against current code.
+Standalone interactive version of \`/fix\` step 5. Checks docs against current code.
 
 **Without argument -- verify all:**
 
@@ -1478,7 +1542,7 @@ ambiguous ones.
 - Touch \`docs/in-progress/\` -- \`/work\`'s territory
 - Handle task lifecycle (planned / in-progress / complete)
 - Edit \`project-map.mdx\` or \`resource-map.mdx\` -- auto-generated, read-only
-- Replace \`/meta fix\` step 5 -- it supplements it with interactivity
+- Replace \`/fix\` step 5 -- it supplements it with interactivity
 `;
 }
 function claudeCredsSkillTemplate() {
@@ -1683,7 +1747,7 @@ It is NOT for instructions (commands), reference docs, or templates.
 }
 function claudeProjectMapRuleTemplate() {
   return `---
-description: Project map conventions -- auto-generated, do not edit, maintained by deploy and /meta fix
+description: Project map conventions -- auto-generated, do not edit, maintained by deploy and /fix
 paths:
   - docs/project-map.mdx
   - docs/resource-map.mdx
@@ -1693,8 +1757,8 @@ paths:
 
 - \`docs/project-map.mdx\` and \`docs/resource-map.mdx\` are fully auto-generated by \`elevasis-sdk deploy\`
 - Do not edit either file manually -- changes are overwritten on next deploy
-- \`/meta fix\` step 8 checks for drift and patches the map
-- If a new command, rule, skill, or memory file is added, run \`/meta fix\` or \`elevasis-sdk deploy\` to update
+- \`/fix\` step 8 checks for drift and patches the map
+- If a new command, rule, skill, or memory file is added, run \`/fix\` or \`elevasis-sdk deploy\` to update
 `;
 }
 function claudeTaskTrackingRuleTemplate() {
@@ -2169,7 +2233,11 @@ function getManagedTemplates(ctx = {}) {
     ".claude/hooks/post-edit-validate.mjs": claudePostEditValidateHookTemplate,
     ".claude/hooks/tool-failure-recovery.mjs": claudeToolFailureRecoveryHookTemplate,
     ".claude/commands/tutorial.md": claudeTutorialCommandTemplate,
-    ".claude/commands/meta.md": claudeMetaCommandTemplate,
+    ".claude/commands/init.md": claudeInitCommandTemplate,
+    ".claude/commands/status.md": claudeStatusCommandTemplate,
+    ".claude/commands/fix.md": claudeFixCommandTemplate,
+    ".claude/commands/deploy.md": claudeDeployCommandTemplate,
+    ".claude/skills/diagnostics/SKILL.md": claudeDiagnosticsSkillTemplate,
     ".claude/skills/work/SKILL.md": claudeWorkSkillTemplate,
     ".claude/commands/docs.md": claudeDocsCommandTemplate,
     ".claude/skills/creds/SKILL.md": claudeCredsSkillTemplate,
@@ -2182,4 +2250,4 @@ function getManagedTemplates(ctx = {}) {
   };
 }
 
-export { claudeCredsSkillTemplate, claudeDocsAuthoringRuleTemplate, claudeMdTemplate, claudeMemoryConventionsRuleTemplate, claudeMetaCommandTemplate, claudeProjectMapRuleTemplate, claudeSdkBoundaryHookTemplate, claudeSdkPatternsRuleTemplate, claudeSettingsTemplate, claudeTaskTrackingRuleTemplate, claudeTutorialCommandTemplate, claudeWorkSkillTemplate, exampleBarrelTemplate, getManagedTemplates, gitignoreTemplate, operationsBarrelTemplate, platformStatusTemplate, starterWorkflowTemplate };
+export { claudeCredsSkillTemplate, claudeDeployCommandTemplate, claudeDiagnosticsSkillTemplate, claudeDocsAuthoringRuleTemplate, claudeFixCommandTemplate, claudeInitCommandTemplate, claudeMdTemplate, claudeMemoryConventionsRuleTemplate, claudeProjectMapRuleTemplate, claudeSdkBoundaryHookTemplate, claudeSdkPatternsRuleTemplate, claudeSettingsTemplate, claudeStatusCommandTemplate, claudeTaskTrackingRuleTemplate, claudeTutorialCommandTemplate, claudeWorkSkillTemplate, exampleBarrelTemplate, getManagedTemplates, gitignoreTemplate, operationsBarrelTemplate, platformStatusTemplate, starterWorkflowTemplate };

package/dist/types/templates.d.ts

@@ -1,2 +1,2 @@
-export { claudeMdTemplate, claudeMetaCommandTemplate, claudeWorkSkillTemplate, claudeTutorialCommandTemplate, claudeSettingsTemplate, claudeSdkBoundaryHookTemplate, claudeCredsSkillTemplate, claudeSdkPatternsRuleTemplate, claudeDocsAuthoringRuleTemplate, claudeMemoryConventionsRuleTemplate, claudeProjectMapRuleTemplate, claudeTaskTrackingRuleTemplate, gitignoreTemplate, starterWorkflowTemplate, platformStatusTemplate, operationsBarrelTemplate, exampleBarrelTemplate } from './cli/commands/init.js';
+export { claudeMdTemplate, claudeInitCommandTemplate, claudeStatusCommandTemplate, claudeFixCommandTemplate, claudeDeployCommandTemplate, claudeDiagnosticsSkillTemplate, claudeWorkSkillTemplate, claudeTutorialCommandTemplate, claudeSettingsTemplate, claudeSdkBoundaryHookTemplate, claudeCredsSkillTemplate, claudeSdkPatternsRuleTemplate, claudeDocsAuthoringRuleTemplate, claudeMemoryConventionsRuleTemplate, claudeProjectMapRuleTemplate, claudeTaskTrackingRuleTemplate, gitignoreTemplate, starterWorkflowTemplate, platformStatusTemplate, operationsBarrelTemplate, exampleBarrelTemplate } from './cli/commands/init.js';
 export { getManagedTemplates } from './cli/commands/templates/core/index.js';

package/package.json

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