@elevasis/sdk 1.5.5 → 1.6.0

package/dist/index.d.ts

@@ -3232,7 +3232,7 @@ type Database = {
                     }
                 ];
             };
-            reported_issues: {
+            reported_requests: {
                 Row: {
                     affected_page: string | null;
                     category: string;
@@ -3251,6 +3251,7 @@ type Database = {
                     status: string;
                     task_id: string | null;
                     title: string;
+                    type: string;
                     updated_at: string;
                 };
                 Insert: {
@@ -3271,6 +3272,7 @@ type Database = {
                     status?: string;
                     task_id?: string | null;
                     title: string;
+                    type: string;
                     updated_at?: string;
                 };
                 Update: {
@@ -3291,25 +3293,26 @@ type Database = {
                     status?: string;
                     task_id?: string | null;
                     title?: string;
+                    type?: string;
                     updated_at?: string;
                 };
                 Relationships: [
                     {
-                        foreignKeyName: "reported_issues_organization_id_fkey";
+                        foreignKeyName: "reported_requests_organization_id_fkey";
                         columns: ["organization_id"];
                         isOneToOne: false;
                         referencedRelation: "organizations";
                         referencedColumns: ["id"];
                     },
                     {
-                        foreignKeyName: "reported_issues_project_id_fkey";
+                        foreignKeyName: "reported_requests_project_id_fkey";
                         columns: ["project_id"];
                         isOneToOne: false;
                         referencedRelation: "prj_projects";
                         referencedColumns: ["id"];
                     },
                     {
-                        foreignKeyName: "reported_issues_task_id_fkey";
+                        foreignKeyName: "reported_requests_task_id_fkey";
                         columns: ["task_id"];
                         isOneToOne: false;
                         referencedRelation: "prj_tasks";

package/package.json

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

package/reference/_navigation.md

@@ -2,7 +2,7 @@
 
 Auto-generated from the package reference manifests.
 
-Package entries indexed: 41.
+Package entries indexed: 42.
 
 ## @elevasis/core / Core
 
@@ -55,6 +55,7 @@ Package entries indexed: 41.
 | Features Lead Gen | `packages/ui/src/features/README.md` | Published lead generation feature surface for downstream shells. | (not specified) |
 | Features Operations | `packages/ui/src/features/README.md` | Published operations feature surface for downstream shells. | (not specified) |
 | Features Monitoring | `packages/ui/src/features/README.md` | Published monitoring feature surface for downstream shells. | (not specified) |
+| Features Monitoring Requests | `packages/ui/src/features/README.md` | Published submitted-requests list, detail, and triage surface for downstream shells. | (not specified) |
 | Features SEO | `packages/ui/src/features/README.md` | Published SEO feature surface for downstream shells. | (not specified) |
 | Features Settings | `packages/ui/src/features/README.md` | Published settings feature surface for downstream shells. | (not specified) |
 

package/reference/_reference-manifest.json

@@ -239,6 +239,20 @@
       "referencePath": "packages/ui/src/features/README.md",
       "publishedExportPath": "./dist/features/monitoring/index.js"
     },
+    {
+      "packageName": "@elevasis/ui",
+      "packageDir": "packages/ui",
+      "subpath": "./features/monitoring/requests",
+      "kind": "subpath",
+      "title": "Features Monitoring Requests",
+      "description": "Published submitted-requests list, detail, and triage surface for downstream shells.",
+      "group": "Features",
+      "order": 8,
+      "sourcePath": "packages/ui/src/features/monitoring/requests/index.ts",
+      "docPath": "packages/ui/src/features/README.md",
+      "referencePath": "packages/ui/src/features/README.md",
+      "publishedExportPath": "./dist/features/monitoring/requests/index.js"
+    },
     {
       "packageName": "@elevasis/ui",
       "packageDir": "packages/ui",
@@ -247,7 +261,7 @@
       "title": "Features SEO",
       "description": "Published SEO feature surface for downstream shells.",
       "group": "Features",
-      "order": 8,
+      "order": 9,
       "sourcePath": "packages/ui/src/features/seo/index.ts",
       "docPath": "packages/ui/src/features/README.md",
       "referencePath": "packages/ui/src/features/README.md",
@@ -261,7 +275,7 @@
       "title": "Features Settings",
       "description": "Published settings feature surface for downstream shells.",
       "group": "Features",
-      "order": 9,
+      "order": 10,
       "sourcePath": "packages/ui/src/features/settings/index.ts",
       "docPath": "packages/ui/src/features/README.md",
       "referencePath": "packages/ui/src/features/README.md",

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

@@ -0,0 +1,11 @@
+# Submit Request
+
+**Usage:** `/submit-request [optional one-line description]`
+
+**Goal:** File a structured request report to the Elevasis platform after agent-driven pre-analysis.
+
+**EXECUTE:** `.claude/skills/submit-request/SKILL.md`
+
+## Env Requirements
+
+- `ELEVASIS_PLATFORM_KEY` (same key used by all `elevasis-sdk` commands — no extra setup if deploy already works)

package/reference/claude-config/skills/project/SKILL.md

@@ -35,6 +35,58 @@ allowed-tools: Bash, Read, Write, Edit, Glob, Grep
 - `/project checklist <client> "<milestone>"` — View checklist for a milestone.
 - `/project delete <client>` — Delete project (cascades milestones, tasks, notes).
 
+## Prerequisites
+
+**Run from the project root** (the directory containing `.elevasis`). Before issuing any other commands, run:
+
+```bash
+pnpm elevasis-sdk doctor
+```
+
+If `doctor` fails, **stop immediately and surface the error** — do not retry other commands. Fix the reported issue first (missing `.env`, bad API key, wrong directory, etc.), then re-run `doctor` before proceeding.
+
+---
+
+## Invocation Contract
+
+All `elevasis-sdk` commands in this skill use the wrapper script form:
+
+```bash
+pnpm elevasis-sdk <subcommand> [flags]
+```
+
+This form is available from the **project root** — the directory that contains the `.elevasis` marker file. The `.elevasis` file is the project-root anchor: `elevasis-sdk` walks up from its invocation directory until it finds this file, then resolves `.env` and all relative paths from that location. After the project-root refactor, CWD within the project tree matters less — but you must still be somewhere inside the project directory tree.
+
+The long form `pnpm -C operations exec elevasis-sdk <subcommand>` still works and is equivalent. Use the short wrapper form (`pnpm elevasis-sdk`) in all new automation and agent scripts.
+
+**If the `.elevasis` marker is missing**, the CLI exits with:
+
+```
+Not inside an Elevasis project. Run this command from a project directory (an Elevasis project has a .elevasis file at its root).
+```
+
+If you see this error, confirm you are inside a project that was created from the template and has the `.elevasis` marker at its root.
+
+---
+
+## Transient Input Files (`tmp/`)
+
+Agents that need to pass structured JSON to `request:submit` or `exec` should write the file to `<projectRoot>/tmp/` rather than to an arbitrary path. The `tmp/` directory is tracked in git (via `tmp/.gitkeep`) but its contents are gitignored, so transient files never pollute the commit history.
+
+**Workflow:**
+
+1. Write the input payload to `tmp/<descriptive-name>.json` from the project root.
+2. Pass the path to the CLI command using the relative form — it resolves against the project root automatically:
+
+   ```bash
+   pnpm elevasis-sdk request:submit -f tmp/request-report.json --cleanup-input
+   pnpm elevasis-sdk exec my-workflow -f tmp/exec-payload.json --cleanup-input
+   ```
+
+3. The `--cleanup-input` flag deletes the file automatically after a successful command. On failure the file is left intact for inspection.
+
+**Safety guard:** `--cleanup-input` only deletes files that are under `<projectRoot>/tmp/`. If the resolved path is outside `tmp/`, the CLI prints a warning to stderr and leaves the file untouched. Files passed via `--input <json>` (inline JSON, no file) are never affected.
+
 ---
 
 ## Orientation Mode (bare `/project` invocation)
@@ -43,10 +95,11 @@ When invoked without a subcommand, enter **project mode**: present the portfolio
 
 ### Flow
 
-1. **List active work** — run:
+1. **List active work** — `--status` accepts exactly one value. Run two calls and merge the results:
 
    ```bash
-   pnpm -C operations exec elevasis-sdk project:list --status active,blocked --format brief
+   pnpm elevasis-sdk project:list --status active --pretty
+   pnpm elevasis-sdk project:list --status blocked --pretty
    ```
 
    Show a compact table: client, status, last-touched.
@@ -154,13 +207,16 @@ No `--prod` flag is needed — the template targets production by default via `E
 
 ### CLI Invocation
 
-All project operations go through the `elevasis-sdk` CLI installed in `operations/`. Run every
-command from the template project root using `-C operations`:
+All project operations go through the `elevasis-sdk` CLI. Use the wrapper script form from the
+project root:
 
 ```bash
-pnpm -C operations exec elevasis-sdk project:<command> [args]
+pnpm elevasis-sdk project:<command> [args]
 ```
 
+The long form `pnpm -C operations exec elevasis-sdk project:<command> [args]` is equivalent and
+still works — use it if the wrapper script is not yet available in an older project.
+
 Organization scoping is handled server-side via `ELEVASIS_PLATFORM_KEY`. No org header or
 `--org` flag is required.
 
@@ -239,7 +295,7 @@ To clear a checklist: `--checklist '[]'`.
 For a plain project table without resume context or next-action suggestions (use the bare `/project` orientation mode above when the user wants the full hub experience):
 
 ```bash
-pnpm -C operations exec elevasis-sdk project:list --kind client_engagement --pretty
+pnpm elevasis-sdk project:list --kind client_engagement --pretty
 ```
 
 Present as:
@@ -261,7 +317,7 @@ For progress detail (milestones/tasks), follow up with `project:milestone:list`
 Wraps `project:work` for fuzzy-matched resume. Used by intent-detection "resume" classification.
 
 ```bash
-pnpm -C operations exec elevasis-sdk project:work <query> --pretty
+pnpm elevasis-sdk project:work <query> --pretty
 ```
 
 Prints the matched project/task brief with current `resume_context`. If multiple matches, show top 3 and ask which.
@@ -274,16 +330,16 @@ If client specified, show full detail for that project. If not, show all.
 
 ```bash
 # Get project details
-pnpm -C operations exec elevasis-sdk project:get <project-id>
+pnpm elevasis-sdk project:get <project-id>
 
 # Milestones (ordered by sequence)
-pnpm -C operations exec elevasis-sdk project:milestone:list --project <project-id> --pretty
+pnpm elevasis-sdk project:milestone:list --project <project-id> --pretty
 
 # Tasks (grouped by milestone)
-pnpm -C operations exec elevasis-sdk project:task:list --project <project-id> --pretty
+pnpm elevasis-sdk project:task:list --project <project-id> --pretty
 
 # Recent notes
-pnpm -C operations exec elevasis-sdk project:note:list --project <project-id> --pretty
+pnpm elevasis-sdk project:note:list --project <project-id> --pretty
 ```
 
 Present as:
@@ -431,21 +487,21 @@ Create everything in sequence using the CLI:
 
 ```bash
 # 1. Create project
-pnpm -C operations exec elevasis-sdk project:create \
+pnpm elevasis-sdk project:create \
   --name "<name>" \
   --kind client_engagement \
   --status active \
   --description "<desc>"
 
 # 2. Create milestones
-pnpm -C operations exec elevasis-sdk project:milestone:create \
+pnpm elevasis-sdk project:milestone:create \
   --project <project-id> \
   --name "<milestone-name>" \
   --status upcoming \
   --due-date <date>
 
 # 3. Create kickoff note (if provided)
-pnpm -C operations exec elevasis-sdk project:note:create \
+pnpm elevasis-sdk project:note:create \
   --project <project-id> \
   --content "<note-content>" \
   --type call_note
@@ -454,7 +510,7 @@ pnpm -C operations exec elevasis-sdk project:note:create \
 If `--company` or `--deal` linking was confirmed, use `project:update` after creation:
 
 ```bash
-pnpm -C operations exec elevasis-sdk project:update <project-id> --description "<updated with link info>"
+pnpm elevasis-sdk project:update <project-id> --description "<updated with link info>"
 ```
 
 (Note: company/deal linking fields are set via the API. If the CLI `project:update` command
@@ -498,7 +554,7 @@ Next: /project status acme
 - `--kind <kind>` (default: `client_engagement`)
 
 ```bash
-pnpm -C operations exec elevasis-sdk project:create \
+pnpm elevasis-sdk project:create \
   --name "<name>" \
   --kind client_engagement \
   --status active \
@@ -514,7 +570,7 @@ pnpm -C operations exec elevasis-sdk project:create \
 First resolve the client (see Client Inference below), then:
 
 ```bash
-pnpm -C operations exec elevasis-sdk project:update <project-id> --status <status>
+pnpm elevasis-sdk project:update <project-id> --status <status>
 ```
 
 ### `milestone add <client> "<name>" [options]` — Add Milestone
@@ -526,7 +582,7 @@ pnpm -C operations exec elevasis-sdk project:update <project-id> --status <statu
 - `--description "<text>"`
 
 ```bash
-pnpm -C operations exec elevasis-sdk project:milestone:create \
+pnpm elevasis-sdk project:milestone:create \
   --project <project-id> \
   --name "<name>" \
   --status upcoming \
@@ -540,13 +596,13 @@ Resolve milestone by name (see Client Inference for project resolution, then use
 
 ```bash
 # List milestones to find ID
-pnpm -C operations exec elevasis-sdk project:milestone:list --project <project-id>
+pnpm elevasis-sdk project:milestone:list --project <project-id>
 
 # Update status
-pnpm -C operations exec elevasis-sdk project:milestone:update <milestone-id> --status completed
+pnpm elevasis-sdk project:milestone:update <milestone-id> --status completed
 
 # Update checklist (full replace)
-pnpm -C operations exec elevasis-sdk project:milestone:update <milestone-id> \
+pnpm elevasis-sdk project:milestone:update <milestone-id> \
   --checklist '[{"id":"uuid","label":"Item label","completed":false}]'
 ```
 
@@ -606,10 +662,10 @@ Onboarding & Scope — Checklist (2/3 complete)
 
 ```bash
 # Resolve milestone ID first if --milestone provided
-pnpm -C operations exec elevasis-sdk project:milestone:list --project <project-id>
+pnpm elevasis-sdk project:milestone:list --project <project-id>
 
 # Create task
-pnpm -C operations exec elevasis-sdk project:task:create \
+pnpm elevasis-sdk project:task:create \
   --project <project-id> \
   --title "<name>" \
   --status planned \
@@ -617,7 +673,7 @@ pnpm -C operations exec elevasis-sdk project:task:create \
   --milestone <milestone-id>
 
 # Create task with initial checklist
-pnpm -C operations exec elevasis-sdk project:task:create \
+pnpm elevasis-sdk project:task:create \
   --project <project-id> \
   --title "<name>" \
   --checklist '[{"id":"1","label":"Step one","completed":false}]'
@@ -629,17 +685,17 @@ Resolve task by name within the project using `project:task:list`, then update b
 
 ```bash
 # Find the task ID
-pnpm -C operations exec elevasis-sdk project:task:list --project <project-id>
+pnpm elevasis-sdk project:task:list --project <project-id>
 
 # Update status (positional <id> comes first, then flags)
-pnpm -C operations exec elevasis-sdk project:task:update <task-id> --status <status>
+pnpm elevasis-sdk project:task:update <task-id> --status <status>
 
 # Update checklist (full replace)
-pnpm -C operations exec elevasis-sdk project:task:update <task-id> \
+pnpm elevasis-sdk project:task:update <task-id> \
   --checklist '[{"id":"uuid","label":"Step","completed":false}]'
 
 # Clear checklist
-pnpm -C operations exec elevasis-sdk project:task:update <task-id> --checklist '[]'
+pnpm elevasis-sdk project:task:update <task-id> --checklist '[]'
 ```
 
 **Options:** `--status`, `--title`, `--milestone`, `--description`, `--checklist <json>`
@@ -663,13 +719,13 @@ If status changes to `approved`, the API auto-sets `completed_at`.
 - `--milestone <milestone-id>` — attach to a milestone (UUID)
 
 ```bash
-pnpm -C operations exec elevasis-sdk project:note:create \
+pnpm elevasis-sdk project:note:create \
   --project <project-id> \
   --content "<content>" \
   --type <type>
 
 # Attach to a task
-pnpm -C operations exec elevasis-sdk project:note:create \
+pnpm elevasis-sdk project:note:create \
   --project <project-id> \
   --content "<content>" \
   --type agent_learning \
@@ -679,7 +735,7 @@ pnpm -C operations exec elevasis-sdk project:note:create \
 ### `notes <client>` — List Notes
 
 ```bash
-pnpm -C operations exec elevasis-sdk project:note:list --project <project-id> --pretty
+pnpm elevasis-sdk project:note:list --project <project-id> --pretty
 ```
 
 ### `delete <client>` — Delete Project
@@ -688,7 +744,7 @@ pnpm -C operations exec elevasis-sdk project:note:list --project <project-id> --
 note count) using the list commands, then ask for confirmation.
 
 ```bash
-pnpm -C operations exec elevasis-sdk project:delete <project-id>
+pnpm elevasis-sdk project:delete <project-id>
 ```
 
 Cascade deletes all milestones, tasks, and notes.
@@ -730,11 +786,12 @@ When in doubt and no project context is resolvable, global auto-memory is the sa
 Before writing a note, the agent resolves which project (and optionally task) to attach it to:
 
 1. **Explicit in session** — a project/task UUID was mentioned or returned by a recent `project:work <id>` or `project:task:*` invocation in this session. Use it directly.
-2. **Implicit from task list** — if step 1 yields nothing, run:
+2. **Implicit from task list** — if step 1 yields nothing, run (`--status` accepts one value; run both calls and merge):
 
    ```bash
-   pnpm -C operations exec elevasis-sdk project:list --status active,blocked --format brief
-   pnpm -C operations exec elevasis-sdk project:task:list --project <top-project-id> --status in_progress
+   pnpm elevasis-sdk project:list --status active --pretty
+   pnpm elevasis-sdk project:list --status blocked --pretty
+   pnpm elevasis-sdk project:task:list --project <top-project-id> --status in_progress
    ```
 
    Use the most-recently-touched project's in-progress task if there is exactly one. If multiple in-progress tasks exist, prefer the one that most closely matches the current conversation topic.
@@ -754,7 +811,7 @@ When the agent recognizes a project-scoped learning (an API quirk, an undocument
 3. Write the note:
 
    ```bash
-   pnpm -C operations exec elevasis-sdk project:note:create \
+   pnpm elevasis-sdk project:note:create \
      --project <project-id> \
      --type agent_learning \
      --task <task-id> \
@@ -792,7 +849,7 @@ When the user or agent says any of the following in the context of a project tas
 Resolve the active task from session context (see Project-Scope Resolution), confirm once ("Mark `<task name>` as completed?"), then fire:
 
 ```bash
-pnpm -C operations exec elevasis-sdk project:task:update <task-id> --status completed
+pnpm elevasis-sdk project:task:update <task-id> --status completed
 ```
 
 If no task resolves, ask the user which task to complete rather than silently skipping.
@@ -817,7 +874,7 @@ Resolve which project the user means using these rules (in priority order):
 1. **Exact ID** — if the argument looks like a UUID, use it directly with `project:get`
 2. **Name match** — list projects filtered by `client_engagement` kind, then match by name:
    ```bash
-   pnpm -C operations exec elevasis-sdk project:list --kind client_engagement
+   pnpm elevasis-sdk project:list --kind client_engagement
    ```
    Filter results by partial name match against the user's input (case-insensitive).
 3. **Single active project** — if only one non-completed `client_engagement` project exists,
@@ -862,7 +919,7 @@ For creating a standard milestone set, run `project:milestone:create` in sequenc
 
 ```bash
 for name in "Discovery" "Implementation" "Testing" "Launch"; do
-  pnpm -C operations exec elevasis-sdk project:milestone:create \
+  pnpm elevasis-sdk project:milestone:create \
     --project <project-id> \
     --name "$name" \
     --status upcoming

package/reference/claude-config/skills/{submit-issue → submit-request}/SKILL.md

@@ -1,13 +1,13 @@
 ---
-name: submit-issue
-description: Submit a structured issue report to the Elevasis platform via CLI — enforces pre-analysis before posting
+name: submit-request
+description: Submit a structured request report to the Elevasis platform via CLI — enforces pre-analysis before posting
 ---
 
-# Submit Issue
+# Submit Request
 
-Submit a structured issue report to the Elevasis platform. The agent performs a six-phase analysis before posting so that every submitted issue includes meaningful context, not just a one-liner.
+Submit a structured request report to the Elevasis platform. The agent performs a six-phase analysis before posting so that every submitted request includes meaningful context, not just a one-liner.
 
-**Usage:** `/submit-issue [optional description]`
+**Usage:** `/submit-request [optional description]`
 
 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.
 
@@ -31,7 +31,7 @@ Gather available context:
 
 ### Phase 2: Identify Source
 
-Pinpoint where the issue originates:
+Pinpoint where the request originates:
 
 - File paths (if a code or config file is involved)
 - Workflow or agent resource IDs (if a platform execution failed)
@@ -42,18 +42,27 @@ Record these for the `evidence` and `affected_page` fields.
 
 ### Phase 3: Gather Errors
 
-Extract concrete error signals:
+Extract concrete error signals (if applicable):
 
 - Full error messages and stack traces (truncated to the relevant portion)
 - HTTP status codes and response bodies
 - Log lines with timestamps if available
 - Screenshots or screenshot file references if the user provided them
 
-These go into the `evidence` object.
+These go into the `evidence` object. For feature requests or questions, this phase may produce an empty `evidence` object — that is expected.
 
-### Phase 4: Classify Severity and Category
+### Phase 4: Select Type and Classify Severity and Category
 
-Select exactly one value for each:
+Select exactly one value for **type first**, then **severity**, then **category**:
+
+**Type:**
+
+| Value      | When to use                                        |
+| ---------- | -------------------------------------------------- |
+| `bug`      | Something is broken or behaving incorrectly        |
+| `feature`  | A new capability or enhancement request            |
+| `question` | Asking for clarification, guidance, or explanation |
+| `other`    | Doesn't fit the above                              |
 
 **Severity:**
 
@@ -65,14 +74,18 @@ Select exactly one value for each:
 
 **Category:**
 
-| Value                | When to use                                            |
-| -------------------- | ------------------------------------------------------ |
-| `ui_bug`             | Frontend rendering or interaction problem              |
-| `data_inconsistency` | DB records, API responses, or UI state don't match     |
-| `performance`        | Slow load, timeout, high resource usage                |
-| `error_pattern`      | Recurring or systematic error across executions        |
-| `configuration`      | Misconfigured resource, credential, env var, or policy |
-| `other`              | Doesn't fit above                                      |
+| Value                 | When to use                                            |
+| --------------------- | ------------------------------------------------------ |
+| `ui_bug`              | Frontend rendering or interaction problem              |
+| `data_inconsistency`  | DB records, API responses, or UI state don't match     |
+| `performance`         | Slow load, timeout, high resource usage                |
+| `error_pattern`       | Recurring or systematic error across executions        |
+| `configuration`       | Misconfigured resource, credential, env var, or policy |
+| `feature_request`     | New feature or enhancement being requested             |
+| `api_design`          | Feedback on API contract, naming, or behavior          |
+| `documentation`       | Missing, incorrect, or unclear documentation           |
+| `integration_request` | Request for a new integration or adapter               |
+| `other`               | Doesn't fit above                                      |
 
 ### Phase 5: Build Structured Report
 
@@ -82,6 +95,7 @@ Assemble the report body from phases 1–4:
 {
   "title": "One-line summary — specific, not vague",
   "description": "What happened. What was expected. Steps to reproduce if applicable.",
+  "type": "<bug|feature|question|other>",
   "severity": "<critical|warning|info>",
   "category": "<category value>",
   "affected_page": "<route or page path, omit if not a UI issue>",
@@ -99,7 +113,7 @@ Assemble the report 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.
+Omit any field that has nothing meaningful to record. `project_id` and `task_id` are optional UUID fields — include them only if the request is clearly scoped to a specific project or task visible in context.
 
 Do NOT include `source` or `organization_id` — the server sets both automatically.
 
@@ -108,9 +122,10 @@ Do NOT include `source` or `organization_id` — the server sets both automatica
 Unless the command was invoked with `--auto`, present the assembled report to the user before submitting:
 
 ```
-Issue Report (ready to submit)
+Request Report (ready to submit)
 ================================
 Title:    <title>
+Type:     <type>
 Severity: <severity>
 Category: <category>
 Page:     <affected_page or "—">
@@ -137,20 +152,20 @@ Once confirmed (or `--auto`), write the assembled JSON body to a temp file then
 
 ```bash
 # Write the report body to a temp file
-# (Use the Write tool to create issue-report.json at the project root)
+# (Use the Write tool to create request-report.json at the project root)
 
-pnpm exec elevasis-sdk issue:submit --input-file ./issue-report.json --pretty
+pnpm exec elevasis-sdk request:submit --input-file ./request-report.json --pretty
 ```
 
 Delete the temp file after submission succeeds or fails.
 
 ## Report Back
 
-On success, the CLI prints the issue ID. Surface it to the user:
+On success, the CLI prints the request ID. Surface it to the user:
 
 ```
 Submitted — id: <uuid>
-Track it in Command Center > Issues.
+Track it in Command Center > Requests.
 ```
 
 ## Troubleshooting
@@ -159,7 +174,7 @@ Track it in Command Center > Issues.
 | ------------------------------- | ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
 | `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.         |
+| `403 Forbidden`                 | Key's org lacks access to request reporting                       | Contact the platform operator to verify the key's org permissions.                                            |
+| `Invalid request 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`/`type`, 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:47:49.477Z by scripts/monorepo/generate-scaffold-contracts.js -->
+<!-- Auto-generated on 2026-04-20T07:18:04.491Z by scripts/monorepo/generate-scaffold-contracts.js -->
 ---
 title: Reference Contracts
 description: Auto-generated TypeScript contracts for SDK consumers. Do not edit manually.

package/reference/scaffold/reference/feature-registry.md

@@ -25,7 +25,7 @@ Feature IDs defined in `DEFAULT_ORGANIZATION_MODEL.features` (`packages/core/src
 
 ```typescript
 // FeatureSchema: { id, label, enabled, color?, icon?, entityIds, surfaceIds, resourceIds, capabilityIds }
-type DefaultFeatureId = 
+type DefaultFeatureId = 'submitted-requests'
 ```
 
 These are the built-in feature IDs. The `featureId` field on a `FeatureModule` manifest must match the `id` of a feature in the organization model to enable access-flag gating.

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

@@ -1,11 +0,0 @@
-# Submit Issue
-
-**Usage:** `/submit-issue [optional one-line description]`
-
-**Goal:** File a structured issue report to the Elevasis platform after agent-driven pre-analysis.
-
-**EXECUTE:** `.claude/skills/submit-issue/SKILL.md`
-
-## Env Requirements
-
-- `ELEVASIS_PLATFORM_KEY` (same key used by all `elevasis-sdk` commands — no extra setup if deploy already works)