@elevasis/sdk 1.21.0 → 1.22.0

package/reference/claude-config/skills/run-ui/SKILL.md

@@ -1,73 +1,73 @@
----
-name: run-ui
-description: Start the project's Vite UI dev server on port 4300 in the background, surfacing the URL once it's ready. Detects port conflicts and asks before killing the holder.
----
-
-# Run UI
-
-Start `ui/` dev server (`pnpm -C ui dev`) in the background on port 4300 and surface the URL when Vite reports ready.
-
-**Usage:** `/run-ui`
-
-The Vite config in `ui/vite.config.ts` pins port 4300 with `strictPort: true`, so a conflict is a hard fail — the skill resolves the conflict before launching.
-
-## Process
-
-### Step 1: Probe port 4300
-
-Run via PowerShell tool (Windows-native, cleanest):
-
-```powershell
-$conn = Get-NetTCPConnection -LocalPort 4300 -State Listen -ErrorAction SilentlyContinue | Select-Object -First 1
-if ($conn) {
-  $proc = Get-Process -Id $conn.OwningProcess -ErrorAction SilentlyContinue
-  $cmd = (Get-CimInstance Win32_Process -Filter "ProcessId = $($conn.OwningProcess)" -ErrorAction SilentlyContinue).CommandLine
-  "PID=$($conn.OwningProcess) NAME=$($proc.ProcessName) CMD=$cmd"
-} else {
-  "FREE"
-}
-```
-
-### Step 2: Branch on probe result
-
-- **`FREE`** → go to Step 3.
-- **Holder is our Vite** (CMD contains `vite` or `node` running from this project's `ui/`) → port is already serving the app. Skip launch and surface `http://localhost:4300/` directly. Done.
-- **Holder is something else** → ask the user:
-
-  > "Port 4300 is held by `<NAME>` (PID `<PID>`). Kill it and start the dev server? (y/n)"
-
-  On `n`, abort with no further action. On `y`, run `Stop-Process -Id <PID> -Force` then continue to Step 3.
-
-### Step 3: Launch dev server in background
-
-Use Bash tool with `run_in_background: true`:
-
-```bash
-pnpm -C ui dev
-```
-
-Capture the returned shell ID.
-
-### Step 4: Wait for ready signal
-
-Poll the background shell output (read every ~2s) for Vite's ready line — typically:
-
-```
-  ➜  Local:   http://localhost:4300/
-```
-
-or `ready in <N>ms`.
-
-Stop polling on the first match. Hard cap: ~15 seconds (≈7 reads). If no ready signal arrives, surface the last 20 lines of background output so the user can debug, and leave the background process running.
-
-### Step 5: Report
-
-On success:
-
-```
-UI dev server running
-  Local:  http://localhost:4300/
-  Shell:  <bg-shell-id>
-```
-
-On timeout, prepend a one-line note ("Vite did not report ready within 15s — last output:") before the captured tail.
+---
+name: run-ui
+description: Start the project's Vite UI dev server on port 4300 in the background, surfacing the URL once it's ready. Detects port conflicts and asks before killing the holder.
+---
+
+# Run UI
+
+Start `ui/` dev server (`pnpm -C ui dev`) in the background on port 4300 and surface the URL when Vite reports ready.
+
+**Usage:** `/run-ui`
+
+The Vite config in `ui/vite.config.ts` pins port 4300 with `strictPort: true`, so a conflict is a hard fail — the skill resolves the conflict before launching.
+
+## Process
+
+### Step 1: Probe port 4300
+
+Run via PowerShell tool (Windows-native, cleanest):
+
+```powershell
+$conn = Get-NetTCPConnection -LocalPort 4300 -State Listen -ErrorAction SilentlyContinue | Select-Object -First 1
+if ($conn) {
+  $proc = Get-Process -Id $conn.OwningProcess -ErrorAction SilentlyContinue
+  $cmd = (Get-CimInstance Win32_Process -Filter "ProcessId = $($conn.OwningProcess)" -ErrorAction SilentlyContinue).CommandLine
+  "PID=$($conn.OwningProcess) NAME=$($proc.ProcessName) CMD=$cmd"
+} else {
+  "FREE"
+}
+```
+
+### Step 2: Branch on probe result
+
+- **`FREE`** → go to Step 3.
+- **Holder is our Vite** (CMD contains `vite` or `node` running from this project's `ui/`) → port is already serving the app. Skip launch and surface `http://localhost:4300/` directly. Done.
+- **Holder is something else** → ask the user:
+
+  > "Port 4300 is held by `<NAME>` (PID `<PID>`). Kill it and start the dev server? (y/n)"
+
+  On `n`, abort with no further action. On `y`, run `Stop-Process -Id <PID> -Force` then continue to Step 3.
+
+### Step 3: Launch dev server in background
+
+Use Bash tool with `run_in_background: true`:
+
+```bash
+pnpm -C ui dev
+```
+
+Capture the returned shell ID.
+
+### Step 4: Wait for ready signal
+
+Poll the background shell output (read every ~2s) for Vite's ready line — typically:
+
+```
+  ➜  Local:   http://localhost:4300/
+```
+
+or `ready in <N>ms`.
+
+Stop polling on the first match. Hard cap: ~15 seconds (≈7 reads). If no ready signal arrives, surface the last 20 lines of background output so the user can debug, and leave the background process running.
+
+### Step 5: Report
+
+On success:
+
+```
+UI dev server running
+  Local:  http://localhost:4300/
+  Shell:  <bg-shell-id>
+```
+
+On timeout, prepend a one-line note ("Vite did not report ready within 15s — last output:") before the captured tail.

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

@@ -48,11 +48,11 @@ Review the current conversation to identify:
    - `core/config/organization-model.ts` -> Foundations layer, Organization Model
    - `core/types/index.ts` -> Foundations layer, Workflow Contracts
    - `ui/src/routes/__root.tsx` -> UI Shell Runtime composition
-   - `ui/src/features/**/manifest.ts` or any file defining a `SystemModule` -> Systems layer
+   - `ui/src/features/**/manifest.ts` or any file defining a `SystemModule` -> Systems layer
    - `operations/src/index.ts` or `operations/elevasis.config.ts` -> core/Deployment (DeploymentSpec)
    - Any file inside `ui/src/features/<feature>/` combined with manifest, nav, or sidebar changes -> Features + Toolkit layers
 
-   Record which OS layers were touched: `foundations`, `systems`, `shell-runtime`, `toolkit`, `deployment`. If none matched, OS awareness stays dormant for the rest of this run.
+   Record which OS layers were touched: `foundations`, `systems`, `shell-runtime`, `toolkit`, `deployment`. If none matched, OS awareness stays dormant for the rest of this run.
 
 ### Step 3: Update Knowledge Docs
 
@@ -115,7 +115,7 @@ pnpm elevasis-sdk project:task:save <task-uuid> \
   --current-state "<concise prose summary of where we are>" \
   --next-steps "<concise prose of the next concrete action>" \
   --files-modified '["path/one.ts","path/two.tsx"]' \
-  --key-docs '["operations/src/foo/index.ts","core/config/organization-model.ts"]' \
+  --key-docs '["operations/src/foo/index.ts","core/config/organization-model.ts"]' \
   --tools '["project:task:save","project:note:create"]'
 ```