lsd-pi 1.1.2 → 1.1.3

package/{src/resources/skills/create-gsd-extension → dist/resources/skills/create-lsd-extension}/references/key-rules-gotchas.md

@@ -1,5 +1,5 @@
 <overview>
-Non-negotiable rules and common gotchas when building GSD extensions.
+Non-negotiable rules and common gotchas when building LSD extensions.
 </overview>
 
 <must_follow>
@@ -22,16 +22,16 @@ Non-negotiable rules and common gotchas when building GSD extensions.
 - Overlay components are **disposed when closed** — create fresh instances each time
 - Treat `ctx.reload()` as terminal — code after runs from pre-reload version
 - Check `ctx.hasUI` before dialog methods (false in print/JSON mode)
-- Extension errors are logged but don't crash GSD — tool_call handler errors fail-safe (block the tool)
+- Extension errors are logged but don't crash LSD — tool_call handler errors fail-safe (block the tool)
 </common_patterns>
 
 <gsd_paths>
-**GSD extension paths (community/user-installed extensions):**
+**LSD extension paths (community/user-installed extensions):**
 - Global: `~/.pi/agent/extensions/*.ts`
 - Global (subdir): `~/.pi/agent/extensions/*/index.ts`
 - Project-local: `.gsd/extensions/*.ts`
 - Project-local (subdir): `.gsd/extensions/*/index.ts`
 
-Note: `~/.gsd/agent/extensions/` is reserved for bundled extensions synced from the gsd-pi package.
+Note: `~/.gsd/agent/extensions/` is reserved for bundled extensions synced from the lsd-pi package.
 Community extensions placed there are silently ignored by the loader.
 </gsd_paths>

package/dist/resources/skills/{create-gsd-extension → create-lsd-extension}/references/packaging-distribution.md

@@ -1,5 +1,5 @@
 <overview>
-Packaging extensions for distribution via npm, git, or local paths. Creating GSD/pi packages.
+Packaging extensions for distribution via npm, git, or local paths. Creating LSD/pi packages.
 </overview>
 
 <package_manifest>
@@ -7,7 +7,7 @@ Add a `pi` manifest to `package.json`:
 
 ```json
 {
-  "name": "my-gsd-package",
+  "name": "my-lsd-package",
   "keywords": ["pi-package"],
   "pi": {
     "extensions": ["./extensions"],
@@ -21,12 +21,12 @@ Add a `pi` manifest to `package.json`:
 
 <installing>
 ```bash
-gsd install npm:@foo/bar@1.0.0
-gsd install git:github.com/user/repo@v1
-gsd install ./local/path
+lsd install npm:@foo/bar@1.0.0
+lsd install git:github.com/user/repo@v1
+lsd install ./local/path
 
 # Try without installing:
-gsd -e npm:@foo/bar
+lsd -e npm:@foo/bar
 ```
 </installing>
 

package/dist/resources/skills/{create-gsd-extension → create-lsd-extension}/workflows/create-extension.md

@@ -12,7 +12,7 @@
 ## Step 1: Determine Scope and Placement
 
 Ask the user:
-- **Global** (`~/.pi/agent/extensions/`) — Available in all GSD sessions
+- **Global** (`~/.pi/agent/extensions/`) — Available in all LSD sessions
 - **Project-local** (`.gsd/extensions/`) — Available only in this project
 
 ## Step 2: Determine Extension Capabilities
@@ -124,14 +124,14 @@ pi.on("tool_call", async (event, ctx) => {
 
 ```bash
 # Quick test without installing
-gsd -e ./path/to/my-extension.ts
+lsd -e ./path/to/my-extension.ts
 
 # Or place in extensions dir and reload
 /reload
 ```
 
 Verify:
-- Extension loads without errors (check GSD startup output)
+- Extension loads without errors (check LSD startup output)
 - Tools appear when LLM is asked to use them
 - Commands respond to `/mycommand`
 - Event hooks trigger at expected points

package/dist/resources/skills/{create-gsd-extension → create-lsd-extension}/workflows/debug-extension.md

@@ -24,10 +24,10 @@
 
 ```bash
 # Test in isolation
-gsd -e ./path/to/extension.ts
+lsd -e ./path/to/extension.ts
 
-# Check GSD startup output for errors
-# Extension errors are logged but don't crash GSD
+# Check LSD startup output for errors
+# Extension errors are logged but don't crash LSD
 ```
 
 ## Step 3: Verify File Location
@@ -38,7 +38,7 @@ Community extensions must be in auto-discovery paths:
 - `.gsd/extensions/*.ts`
 - `.gsd/extensions/*/index.ts`
 
-Note: `~/.gsd/agent/extensions/` is reserved for bundled extensions synced from the gsd-pi package.
+Note: `~/.gsd/agent/extensions/` is reserved for bundled extensions synced from the lsd-pi package.
 
 The file must `export default function(pi: ExtensionAPI) { ... }`.
 
@@ -49,7 +49,7 @@ Read `../references/key-rules-gotchas.md` and verify each rule against the exten
 ## Step 5: Add Debugging
 
 ```typescript
-// Temporary: log to stderr (visible in GSD output)
+// Temporary: log to stderr (visible in LSD output)
 console.error("[my-ext] Loading...");
 
 pi.on("session_start", async (_event, ctx) => {

package/dist/resources/skills/teams-debug/SKILL.md

@@ -1,18 +1,17 @@
 ---
 name: teams-debug
 description: "Fix any bug related to an active Teams plan. Can be triggered by the user at any time or automatically from teams-verify on failure. Reads the plan for context, spawns a targeted builder subagent to fix the issue, then appends a debug status update to the plan."
-user-invocable: true
 ---
 
 # Teams: Debug
 
 Fix a bug related to the current Teams plan. This skill can be triggered:
-- **By the user at any time** — e.g. "something's broken, use `/teams-debug`"
-- **Automatically from `/teams-verify`** — when a scenario fails during manual verification
+- **By the user at any time** — e.g. "something's broken, use `/skill:teams-debug`"
+- **Automatically from `/skill:teams-verify`** — when a scenario fails during manual verification
 
 It reads the plan (which contains all review and verification history) before fixing.
 
-**Prerequisite:** A `.lsd/plan/PLAN-*.md` file must exist. If none found, stop and tell the user to run `/teams-plan` first.
+**Prerequisite:** A `.lsd/plan/PLAN-*.md` file must exist. If none found, stop and tell the user to run `/skill:teams-plan` first.
 
 ---
 
@@ -32,7 +31,7 @@ Otherwise, ask:
 
 > **What's the bug?**
 >
-> Describe what went wrong, what you expected, and what you saw. Include the scenario name if it came from `/teams-verify`.
+> Describe what went wrong, what you expected, and what you saw. Include the scenario name if it came from `/skill:teams-verify`.
 
 Wait for their response.
 
@@ -127,4 +126,4 @@ Print:
 ```
 
 Then ask:
-> **Want to re-verify this scenario? Run `/teams-verify` to continue from where you left off.**
+> **Want to re-verify this scenario? Run `/skill:teams-verify` to continue from where you left off.**

package/dist/resources/skills/teams-document/SKILL.md

@@ -1,7 +1,6 @@
 ---
 name: teams-document
 description: "Update existing project docs (README.md, ARCHITECTURE.md, etc.) and the active plan file to reflect the latest build. Spawns a worker subagent scribe to find and update relevant documentation files and ensure the plan is accurate, then appends a docs status update to the plan."
-user-invocable: true
 ---
 
 # Teams: Document
@@ -9,7 +8,7 @@ user-invocable: true
 Update existing project documentation to reflect what was built in the current plan. Spawns a worker subagent that finds relevant docs and updates them — no new files created unless explicitly needed.
 
 **Prerequisite:** A `.lsd/plan/PLAN-*.md` file must exist. If none found, stop:
-> No plan files found in `.lsd/plan/`. Run `/teams-plan` first.
+> No plan files found in `.lsd/plan/`. Run `/skill:teams-plan` first.
 
 ---
 

package/dist/resources/skills/teams-plan/SKILL.md

@@ -1,7 +1,6 @@
 ---
 name: teams-plan
 description: "Plan and build a feature. Orchestrator plans, spawns sequential builder subagents per phase (with Playwright/Maestro verification), then a reviewer subagent, then a builder to apply fixes. Supports parallel mode for independent phases."
-user-invocable: true
 ---
 
 # Teams: Plan + Build
@@ -41,7 +40,7 @@ mkdir -p .lsd/plan
 - Check for existing plan files: `.lsd/plan/PLAN-*.md`
 - Count existing files to determine N (next plan number = count + 1)
 - If plans exist, inform the user:
-  > **Found [N-1] existing plan(s). Creating Plan #[N]. Use `/teams-run` to resume an existing plan.**
+  > **Found [N-1] existing plan(s). Creating Plan #[N]. Use `/skill:teams-run` to resume an existing plan.**
 - If no existing plans: plan number = 1
 
 Write `.lsd/plan/PLAN-[N].md`:
@@ -291,7 +290,7 @@ Final summary format:
 ```
 
 Then suggest:
-> **Build done. Run `/teams-verify` to walk through manual E2E verification.**
+> **Build done. Run `/skill:teams-verify` to walk through manual E2E verification.**
 
 ---
 
@@ -299,7 +298,7 @@ Then suggest:
 
 Ask the user:
 
-> **"Would you like to update your documentation? Run `/teams-document` to have the scribe update your README, ARCHITECTURE.md, and other docs."**
+> **"Would you like to update your documentation? Run `/skill:teams-document` to have the scribe update your README, ARCHITECTURE.md, and other docs."**
 
 If yes, invoke the `teams-document` skill.
 

package/dist/resources/skills/teams-run/SKILL.md

@@ -1,7 +1,6 @@
 ---
 name: teams-run
 description: "Resume building a single Teams plan. Orchestrator spawns sequential or parallel builder subagents per incomplete phase, then a reviewer subagent, then applies fixes."
-user-invocable: true
 ---
 
 # Teams: Run (Resume Build)
@@ -13,7 +12,7 @@ You are the orchestrator. Resume an existing build by running all incomplete pha
 ## Step 1: Find the Plan
 
 List all files matching `.lsd/plan/PLAN-*.md`. If none exist:
-> No plan files found in `.lsd/plan/`. Use `/teams-plan` to create a plan first.
+> No plan files found in `.lsd/plan/`. Use `/skill:teams-plan` to create a plan first.
 
 If multiple plan files exist, show the list and ask the user which plan to resume. Default to the highest-numbered plan.
 
@@ -216,7 +215,7 @@ Final summary:
 ```
 
 Then suggest:
-> **Build done. Run `/teams-verify` to walk through manual E2E verification.**
+> **Build done. Run `/skill:teams-verify` to walk through manual E2E verification.**
 
 ---
 
@@ -224,7 +223,7 @@ Then suggest:
 
 Ask the user:
 
-> **"Would you like to update your documentation? Run `/teams-document` to have the scribe update your README, ARCHITECTURE.md, and other docs."**
+> **"Would you like to update your documentation? Run `/skill:teams-document` to have the scribe update your README, ARCHITECTURE.md, and other docs."**
 
 If yes, invoke the `teams-document` skill.
 

package/dist/resources/skills/teams-verify/SKILL.md

@@ -1,7 +1,6 @@
 ---
 name: teams-verify
 description: "Guide the user through manually verifying the build E2E — walks through each scenario step-by-step, records pass/fail, and appends a verification status update to the plan file."
-user-invocable: true
 ---
 
 # Teams: Manual Verify
@@ -13,7 +12,7 @@ You guide the user through manually verifying the completed build end-to-end. On
 ## Step 1: Load the Plan
 
 Find and read the most recent `.lsd/plan/PLAN-*.md` (highest number). Store as `PLAN_FILE`. If none exist:
-> No plan files found in `.lsd/plan/`. Run `/teams-plan` first.
+> No plan files found in `.lsd/plan/`. Run `/skill:teams-plan` first.
 
 Extract:
 - Plan ID (the `Plan ID:` field — e.g. `#2`)
@@ -63,7 +62,7 @@ Then ask:
 
 - **pass** → record it, move to next scenario
 - **fail** → ask: *"What went wrong?"* Record their description. Then immediately offer:
-  > **Bug detected. Run `/teams-debug` to fix it now, or continue verifying the rest first?**
+  > **Bug detected. Run `/skill:teams-debug` to fix it now, or continue verifying the rest first?**
 
   If they say **fix now**: invoke the `teams-debug` skill directly, passing the scenario name and their failure description as context. After the fix is applied, re-run this scenario before continuing.
 
@@ -115,9 +114,9 @@ Print the final result:
 If there are failures, offer:
 
 > **N scenario(s) failed. Options:**
-> - `/teams-debug` — fix bugs one at a time with full plan context (recommended)
+> - `/skill:teams-debug` — fix bugs one at a time with full plan context (recommended)
 > - **Fix all** — I spawn a single builder to address all failures at once
 
-If they choose **`/teams-debug`**: invoke the `teams-debug` skill for each failed scenario in order, passing the scenario name and failure description. After each fix, update the `## Verification` section in the plan to mark the scenario as `FIXED`.
+If they choose **`/skill:teams-debug`**: invoke the `teams-debug` skill for each failed scenario in order, passing the scenario name and failure description. After each fix, update the `## Verification` section in the plan to mark the scenario as `FIXED`.
 
 If they choose **fix all**: read the failures from the plan's `## Verification` section and spawn a **Sonnet** builder subagent with the full list of issues. Then offer to re-run verification on just the failed scenarios.

package/dist/startup-model-validation.js

@@ -35,6 +35,7 @@ export function validateConfiguredModel(modelRegistry, settingsManager) {
             ? availableModels.find((m) => m.provider === piDefault.provider && m.id === piDefault.model)
             : undefined) ||
             availableModels.find((m) => m.provider === 'openai' && m.id === 'gpt-5.4') ||
+            availableModels.find((m) => m.provider === 'openai' && m.id === 'gpt-5.4-mini') ||
             availableModels.find((m) => m.provider === 'openai') ||
             availableModels.find((m) => m.provider === 'anthropic' && m.id === 'claude-opus-4-6') ||
             availableModels.find((m) => m.provider === 'anthropic' && m.id.includes('opus')) ||

package/dist/welcome-screen.js

@@ -9,6 +9,7 @@ import os from 'node:os';
 import chalk from 'chalk';
 import { GSD_LOGO_SEGMENTS } from './logo.js';
 import { brandNameChalk, LSD_BLUE, LSD_PINK, LSD_YELLOW } from './lsd-brand.js';
+import { accentHex } from './cli-theme.js';
 function getShortCwd() {
     const cwd = process.cwd();
     const home = os.homedir();
@@ -37,6 +38,7 @@ export function printWelcomeScreen(opts) {
     const YELLOW = LSD_YELLOW;
     const BLUE = LSD_BLUE;
     const PINK = LSD_PINK;
+    const ACCENT = accentHex();
     // ── Panel widths ────────────────────────────────────────────────────────────
     // Layout: 1 leading space + LEFT_INNER logo content + 1 inner divider + RIGHT_INNER info
     // Total: 1 + LEFT_INNER + 1 + RIGHT_INNER = termWidth
@@ -63,23 +65,23 @@ export function printWelcomeScreen(opts) {
     if (process.env.CONTEXT7_API_KEY)
         toolParts.push('Context7 ✓');
     // Tools summary row
-    const toolsLeft = toolParts.length > 0 ? chalk.hex(PINK).dim('  ' + toolParts.join('  ·  ')) : '';
+    const toolsLeft = toolParts.length > 0 ? chalk.hex(PINK)('  ' + toolParts.join('  ·  ')) : '';
     const footerRow = rpad(toolsLeft, RIGHT_INNER);
     const DIVIDER = null;
     const rightRows = [
         titleRow,
         DIVIDER,
-        modelName ? `  Model      ${chalk.hex(BLUE).dim(modelName)}` : '',
-        provider ? `  Provider   ${chalk.hex(BLUE).dim(provider)}` : '',
-        `  Directory  ${chalk.hex(BLUE).dim(shortCwd)}`,
+        modelName ? `  Model      ${chalk.hex(ACCENT)(modelName)}` : '',
+        provider ? `  Provider   ${chalk.hex(ACCENT)(provider)}` : '',
+        `  Directory  ${chalk.hex(ACCENT)(shortCwd)}`,
         DIVIDER,
         footerRow,
         '',
     ];
     // ── Render ──────────────────────────────────────────────────────────────────
     const out = [''];
-    // Top bar — full-width blue separator
-    out.push(chalk.hex(BLUE)(H.repeat(termWidth)));
+    // Top bar — full-width accent separator
+    out.push(chalk.hex(ACCENT)(H.repeat(termWidth)));
     for (let i = 0; i < 8; i++) {
         const row = leftRows[i];
         const lContent = row
@@ -87,16 +89,16 @@ export function printWelcomeScreen(opts) {
             : ' '.repeat(LEFT_INNER);
         const rRow = rightRows[i];
         if (rRow === null) {
-            // Section divider: left logo area + blue ├────... extending right
-            out.push(' ' + lContent + chalk.hex(BLUE).dim(DS + H.repeat(RIGHT_INNER)));
+            // Section divider: left logo area + accent ├────... extending right
+            out.push(' ' + lContent + chalk.hex(ACCENT)(DS + H.repeat(RIGHT_INNER)));
         }
         else {
             // Content row: 1 space + logo │ info (no outer vertical borders)
-            out.push(' ' + lContent + chalk.hex(BLUE).dim(DV) + rpad(rRow, RIGHT_INNER));
+            out.push(' ' + lContent + chalk.hex(ACCENT)(DV) + rpad(rRow, RIGHT_INNER));
         }
     }
-    // Bottom bar — full-width blue separator
-    out.push(chalk.hex(BLUE)(H.repeat(termWidth)));
+    // Bottom bar — full-width accent separator
+    out.push(chalk.hex(ACCENT)(H.repeat(termWidth)));
     out.push('');
     process.stderr.write(out.join('\n') + '\n');
 }

package/dist/wizard.js

@@ -1,3 +1,4 @@
+import { BEDROCK_PROVIDER_ID, applyBedrockCredentialToEnv, decodeBedrockCredential } from './bedrock-auth.js';
 // ─── Env hydration ────────────────────────────────────────────────────────────
 /**
  * Hydrate process.env from stored auth.json credentials for optional tool keys.
@@ -5,6 +6,17 @@
  * wizard on prior launches.
  */
 export function loadStoredEnvKeys(authStorage) {
+    const hasExplicitBedrockAuth = Boolean(process.env.AWS_PROFILE ||
+        process.env.AWS_ACCESS_KEY_ID ||
+        process.env.AWS_SECRET_ACCESS_KEY);
+    const bedrockCred = authStorage.getCredentialsForProvider(BEDROCK_PROVIDER_ID)
+        .find((cred) => cred.type === 'api_key' && typeof cred.key === 'string' && cred.key);
+    if (!hasExplicitBedrockAuth && bedrockCred?.type === 'api_key') {
+        const parsed = decodeBedrockCredential(bedrockCred.key);
+        if (parsed) {
+            applyBedrockCredentialToEnv(parsed);
+        }
+    }
     const providers = [
         ['brave', 'BRAVE_API_KEY'],
         ['brave_answers', 'BRAVE_ANSWERS_KEY'],

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "lsd-pi",
-  "version": "1.1.2",
+  "version": "1.1.3",
   "description": "LSD — let stuff develop coding agent",
   "license": "MIT",
   "repository": {