@elevasis/sdk 1.5.4 → 1.5.5

package/dist/cli.cjs

@@ -43990,7 +43990,7 @@ function wrapAction(commandName, fn) {
 // package.json
 var package_default = {
   name: "@elevasis/sdk",
-  version: "1.5.4",
+  version: "1.5.5",
   description: "SDK for building Elevasis organization resources",
   type: "module",
   bin: {
@@ -46165,6 +46165,72 @@ function registerProjectCommands(program3) {
   registerNoteDelete(program3);
 }
 
+// src/cli/commands/issue/issue.ts
+var import_node_fs2 = require("node:fs");
+
+// ../core/src/issues/api-schemas.ts
+var IssueSeverityEnum = external_exports.enum(["critical", "warning", "info"]);
+var IssueCategoryEnum = external_exports.enum([
+  "ui_bug",
+  "data_inconsistency",
+  "performance",
+  "error_pattern",
+  "configuration",
+  "other"
+]);
+var IssueStatusEnum = external_exports.enum(["open", "investigating", "resolved", "wont_fix"]);
+var IssueSourceEnum = external_exports.enum(["agent", "cli", "api", "webhook", "user", "external"]);
+var CreateIssueInputSchema = external_exports.object({
+  title: external_exports.string().min(1),
+  description: external_exports.string().min(1),
+  severity: IssueSeverityEnum,
+  category: IssueCategoryEnum,
+  affected_page: external_exports.string().nullish(),
+  evidence: external_exports.record(external_exports.string(), external_exports.unknown()).nullish(),
+  context: external_exports.record(external_exports.string(), external_exports.unknown()).nullish(),
+  project_id: external_exports.string().uuid().nullish(),
+  task_id: external_exports.string().uuid().nullish()
+}).strict();
+var ListIssuesQuerySchema = external_exports.object({
+  status: IssueStatusEnum.optional(),
+  severity: IssueSeverityEnum.optional(),
+  project_id: external_exports.string().uuid().optional(),
+  limit: external_exports.coerce.number().int().min(1).max(200).default(50)
+});
+
+// src/cli/commands/issue/issue.ts
+function registerIssueCommands(program3) {
+  program3.command("issue:submit").description(
+    "Submit a structured issue report via POST /api/external/issues\n  Example: elevasis-sdk issue:submit -f ./issue.json"
+  ).option("-i, --input <json>", "Issue body as JSON string").option("-f, --input-file <path>", "Read issue body from a JSON file (avoids shell escaping)").option("--api-url <url>", "API base URL").option("--pretty", "Render human-readable output instead of raw JSON").action(
+    wrapAction("issue:submit", async (options2) => {
+      if (!options2.input && !options2.inputFile) {
+        throw new Error("Provide --input <json> or --input-file <path>");
+      }
+      const raw = options2.inputFile ? JSON.parse((0, import_node_fs2.readFileSync)(options2.inputFile, "utf8")) : JSON.parse(options2.input);
+      const parsed = CreateIssueInputSchema.safeParse(raw);
+      if (!parsed.success) {
+        const issues = parsed.error.issues.map((i) => `  - ${i.path.join(".") || "(root)"}: ${i.message}`).join("\n");
+        throw new Error(`Invalid issue body:
+${issues}`);
+      }
+      const apiUrl = resolveApiUrl(options2.apiUrl);
+      const result = await apiPost("/api/external/issues", parsed.data, apiUrl);
+      if (options2.pretty) {
+        const i = result.issue;
+        console.log(source_default.green("\nIssue submitted"));
+        console.log(source_default.gray(`  ID:       ${i.id}`));
+        console.log(source_default.gray(`  Severity: ${i.severity}`));
+        console.log(source_default.gray(`  Category: ${i.category}`));
+        console.log(source_default.gray(`  Status:   ${i.status}`));
+        console.log();
+      } else {
+        console.log(JSON.stringify(result, null, 2));
+      }
+    })
+  );
+}
+
 // src/cli/commands/init-claude.ts
 var import_path4 = require("path");
 var import_fs2 = require("fs");
@@ -46707,6 +46773,7 @@ Commands:
   elevasis-sdk project:list [--search <query>]      List projects with optional search
   elevasis-sdk project:resolve <query>              Resolve a project ID from a name or UUID
   elevasis-sdk project:work <query>                 Open a lifecycle-aware project work brief
+  elevasis-sdk issue:submit -f <path>               Submit a structured issue report
   elevasis-sdk rename <id> --to <newId> [--prod]     Rename resource across platform tables
   elevasis-sdk init-claude                            Initialize .claude/ config from SDK
   elevasis-sdk generate-docs                         Generate docs/index.md from frontmatter
@@ -46727,6 +46794,7 @@ registerCredsCommand(program2);
 registerErrorCommand(program2);
 registerRenameCommand(program2);
 registerProjectCommands(program2);
+registerIssueCommands(program2);
 registerInitClaudeCommand(program2);
 registerGenerateDocsCommand(program2);
 registerGenerateResourcesCommand(program2);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elevasis/sdk",
-  "version": "1.5.4",
+  "version": "1.5.5",
   "description": "SDK for building Elevasis organization resources",
   "type": "module",
   "bin": {
@@ -44,8 +44,8 @@
     "tsup": "^8.0.0",
     "typescript": "5.9.2",
     "zod": "^4.1.0",
-    "@repo/typescript-config": "0.0.0",
-    "@repo/core": "0.5.0"
+    "@repo/core": "0.5.0",
+    "@repo/typescript-config": "0.0.0"
   },
   "scripts": {
     "build": "node -e \"require('fs').rmSync('dist',{recursive:true,force:true})\" && tsc -p tsconfig.core-dts.json && tsc -p tsconfig.build.json && tsup && rollup -c rollup.dts.config.mjs && esbuild src/cli/index.ts --bundle --platform=node --outfile=dist/cli.cjs --format=cjs --external:esbuild --banner:js=\"#!/usr/bin/env node\" && node scripts/copy-reference-docs.mjs && node ../../scripts/monorepo/generate-reference-artifacts.js",

package/reference/claude-config/commands/submit-issue.md

@@ -8,5 +8,4 @@
 
 ## Env Requirements
 
-- `ELEVASIS_API_URL` (base URL of the Elevasis API)
-- `ELEVASIS_API_KEY` (Bearer `sk_*`, provisioned via Command Center → Settings → API Keys)
+- `ELEVASIS_PLATFORM_KEY` (same key used by all `elevasis-sdk` commands — no extra setup if deploy already works)

package/reference/claude-config/skills/submit-issue/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: submit-issue
-description: Submit a structured issue report to the Elevasis platform via API — enforces pre-analysis before posting
+description: Submit a structured issue report to the Elevasis platform via CLI — enforces pre-analysis before posting
 ---
 
 # Submit Issue
@@ -9,18 +9,13 @@ Submit a structured issue report to the Elevasis platform. The agent performs a
 
 **Usage:** `/submit-issue [optional description]`
 
-If a description is provided, it is the primary signal for Phase 1. Otherwise the agent analyzes recent conversation context (~20 messages) plus any active error context.
+If a description is provided, it is the primary signal for Phase 1. Otherwise the agent analyzes recent conversation context plus any active error context.
 
 ## Env Requirements
 
-Both variables must be present in the project's root `.env`:
+`ELEVASIS_PLATFORM_KEY` must be present in the project's root `.env` (the same key used by all other `elevasis-sdk` commands — no additional setup needed if deploy is already working).
 
-| Variable           | Description                                                                                   |
-| ------------------ | --------------------------------------------------------------------------------------------- |
-| `ELEVASIS_API_URL` | Platform API base URL (e.g. `https://api.elevasis.io`)                                        |
-| `ELEVASIS_API_KEY` | API key starting with `sk_` (67 chars), provisioned from Command Center > Settings > API Keys |
-
-The organization is resolved server-side from the key. Never include an `organization_id` in the request body.
+The organization and API base URL are resolved automatically by the CLI. No `ELEVASIS_API_KEY` or `ELEVASIS_API_URL` needed.
 
 ## Pre-Analysis Phases
 
@@ -81,7 +76,7 @@ Select exactly one value for each:
 
 ### Phase 5: Build Structured Report
 
-Assemble the request body from phases 1–4:
+Assemble the report body from phases 1–4:
 
 ```json
 {
@@ -106,6 +101,8 @@ Assemble the request body from phases 1–4:
 
 Omit any field that has nothing meaningful to record. `project_id` and `task_id` are optional UUID fields — include them only if the issue is clearly scoped to a specific project or task visible in context.
 
+Do NOT include `source` or `organization_id` — the server sets both automatically.
+
 ### Phase 6: Confirm with User
 
 Unless the command was invoked with `--auto`, present the assembled report to the user before submitting:
@@ -136,44 +133,33 @@ Auto-submit (`--auto`) skips this confirmation entirely — use only when the ca
 
 ## Submit
 
-Once confirmed (or `--auto`), POST to the external issues endpoint:
+Once confirmed (or `--auto`), write the assembled JSON body to a temp file then submit via the SDK CLI:
 
 ```bash
-curl -sS -X POST "${ELEVASIS_API_URL}/api/external/issues" \
-  -H "Authorization: Bearer ${ELEVASIS_API_KEY}" \
-  -H "Content-Type: application/json" \
-  -d @- <<'JSON'
-{
-  "title": "...",
-  "description": "...",
-  "severity": "warning",
-  "category": "ui_bug",
-  "affected_page": "/projects/abc",
-  "evidence": {},
-  "context": {}
-}
-JSON
+# Write the report body to a temp file
+# (Use the Write tool to create issue-report.json at the project root)
+
+pnpm exec elevasis-sdk issue:submit --input-file ./issue-report.json --pretty
 ```
 
-Do NOT include `source` or `organization_id` in the body — the server sets both automatically.
+Delete the temp file after submission succeeds or fails.
 
 ## Report Back
 
-On a successful response (2xx), surface the issue ID to the user:
+On success, the CLI prints the issue ID. Surface it to the user:
 
 ```
 Submitted — id: <uuid>
 Track it in Command Center > Issues.
 ```
 
-If the response body contains additional fields (status, created_at), include them in a brief one-line summary.
-
 ## Troubleshooting
 
-| Status             | Cause                                                             | Fix                                                                                                                                           |
-| ------------------ | ----------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
-| `401 Unauthorized` | `ELEVASIS_API_KEY` is missing, malformed, or revoked              | Verify the key in root `.env` starts with `sk_` and is 67 chars. Re-provision from Command Center > Settings > API Keys if needed.            |
-| `403 Forbidden`    | Key exists but the associated org lacks access to issue reporting | Contact the platform operator to verify the key's org permissions.                                                                            |
-| `400 Bad Request`  | Request body failed validation                                    | Read the response body for the specific field error. Common causes: missing `title` or `description`, invalid `severity` or `category` value. |
-| `404 Not Found`    | `ELEVASIS_API_URL` is wrong or the endpoint path has a typo       | Confirm the URL in `.env` (no trailing slash) and that the path is exactly `/api/external/issues`.                                            |
-| Connection refused | API server unreachable                                            | Check `ELEVASIS_API_URL` and network connectivity. For local dev, confirm the API server is running.                                          |
+| Error                           | Cause                                                             | Fix                                                                                                           |
+| ------------------------------- | ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
+| `ELEVASIS_PLATFORM_KEY` missing | Key not set in root `.env`                                        | Add `ELEVASIS_PLATFORM_KEY=sk_...` to `.env`. Provision from Command Center > Settings > API Keys.            |
+| `401 Unauthorized`              | Key is malformed or revoked                                       | Verify the key starts with `sk_` and is 67 chars. Re-provision if needed.                                     |
+| `403 Forbidden`                 | Key's org lacks access to issue reporting                         | Contact the platform operator to verify the key's org permissions.                                            |
+| `Invalid issue body`            | Report failed CLI-side Zod validation before the request was sent | Read the field errors printed by the CLI. Common causes: missing `title`/`description`, invalid enum.         |
+| `400 Bad Request`               | Body passed CLI validation but failed server-side validation      | Read the response body for the specific field error.                                                          |
+| Connection refused              | API server unreachable                                            | Default target is `https://api.elevasis.io` — check network. For local dev, set `ELEVASIS_API_URL` in `.env`. |

package/reference/scaffold/reference/contracts.md

@@ -1,4 +1,4 @@
-<!-- Auto-generated on 2026-04-19T10:24:34.890Z by scripts/monorepo/generate-scaffold-contracts.js -->
+<!-- Auto-generated on 2026-04-19T10:47:49.477Z by scripts/monorepo/generate-scaffold-contracts.js -->
 ---
 title: Reference Contracts
 description: Auto-generated TypeScript contracts for SDK consumers. Do not edit manually.