@elevasis/sdk 0.5.9 → 0.5.11

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -18,7 +18,7 @@ This is the static SDK-level error catalog. Check `.claude/memory/errors/` first
18
18
  1. Check that `.env` exists in the workspace root
19
19
  2. Confirm it contains `ELEVASIS_API_KEY=sk_...`
20
20
  3. Make sure you are running the CLI from the workspace directory (where `.env` is located)
21
- 4. If the file exists with the right content, run `elevasis check` again
21
+ 4. If the file exists with the right content, run `elevasis-sdk check` again
22
22
 
23
23
  ### Cannot connect to API
24
24
 
@@ -37,7 +37,7 @@ This is the static SDK-level error catalog. Check `.claude/memory/errors/` first
37
37
 
38
38
  ---
39
39
 
40
- ## Validation Errors (elevasis check)
40
+ ## Validation Errors (elevasis-sdk check)
41
41
 
42
42
  ### Duplicate resource ID
43
43
 
@@ -187,7 +187,7 @@ This is the static SDK-level error catalog. Check `.claude/memory/errors/` first
187
187
  **Cause:** An import in your workflow bundle cannot be resolved.
188
188
 
189
189
  **Fix:**
190
- 1. Run `elevasis check` -- it catches most resolution errors before deploy
190
+ 1. Run `elevasis-sdk check` -- it catches most resolution errors before deploy
191
191
  2. If the import is a built-in Node.js module, ensure it is compatible with the worker environment
192
192
  3. Avoid imports that require file system access or native modules
193
193