@shepai/cli 1.156.0-pr487.27d2745 → 1.156.0-pr489.56abb36

package/README.md

@@ -1,259 +1,356 @@
 <div align="center">
 
-# Shep AI
+<h1>
+  <picture>
+    <source media="(prefers-color-scheme: dark)" srcset="src/presentation/web/public/favicon-light.svg">
+    <source media="(prefers-color-scheme: light)" srcset="src/presentation/web/public/favicon-dark.svg">
+    <img src="src/presentation/web/public/favicon-light.svg" alt="Shep logo" width="28" valign="middle" />
+  </picture>
+  Shep
+</h1>
 
-### One command. Full lifecycle. Merged PR.
+### Run multiple AI agents in parallel. Each in its own worktree.
 
-_Describe a feature in plain English — Shep researches, plans, codes, tests, and opens a PR. You approve when you want to, or let it run hands-free._
+_Manage 10 features at once — isolated branches, automatic commits, CI watching, and PRs — from a dashboard or the terminal._
 
 [![CI](https://github.com/shep-ai/cli/actions/workflows/ci.yml/badge.svg)](https://github.com/shep-ai/cli/actions/workflows/ci.yml)
 [![npm version](https://img.shields.io/npm/v/@shepai/cli.svg?color=cb3837&logo=npm)](https://www.npmjs.com/package/@shepai/cli)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
-[![TypeScript](https://img.shields.io/badge/TypeScript-5.3+-3178c6.svg?logo=typescript&logoColor=white)](https://www.typescriptlang.org/)
-[![Node.js](https://img.shields.io/badge/Node.js-≥18-339933.svg?logo=node.js&logoColor=white)](https://nodejs.org/)
-[![pnpm](https://img.shields.io/badge/pnpm-≥8-f69220.svg?logo=pnpm&logoColor=white)](https://pnpm.io/)
-[![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg)](https://github.com/shep-ai/cli/pulls)
-[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-fe5196.svg?logo=conventionalcommits&logoColor=white)](https://conventionalcommits.org)
 
-<br />
-
-[Features](#features) · [Quick Start](#quick-start) · [CLI Reference](#cli-reference) · [Architecture](#architecture) · [Contributing](#contributing)
+[Quick Start](#quick-start) · [How It Works](#how-it-works) · [Features](#features) · [Trust & Safety](#trust--safety) · [FAQ](#faq)
 
 <br />
 
-<img src="docs/screenshots/cover.png" alt="Shep AI" width="900" />
+<img src="docs/screenshots/cover.png" alt="Shep — Parallel AI Agent Sessions" width="900" />
 
 </div>
 
 ---
 
+## Why Shep?
+
+You're already using AI coding agents. The problem isn't the coding — it's everything around it.
+
+Switching branches. Stashing changes. Watching CI. Assembling PRs. Losing context when you juggle three things at once. One agent session is fine. Five is chaos.
+
+**Shep gives each feature its own isolated world** — a git worktree, a branch, an agent session — and handles the boring parts: committing, pushing, opening PRs, watching CI, and fixing failures. You manage it all from one dashboard or the CLI.
+
+```bash
+shep feat new "add stripe payments" --push --pr
+shep feat new "add dark mode toggle" --push --pr
+shep feat new "fix login redirect bug" --push --pr
+# Three agents running in parallel. Zero branch conflicts. You monitor from one place.
+```
+
+---
+
 ## Quick Start
 
+### Prerequisites
+
+- **Node.js 22+** and **npm** (or install via `nvm`)
+- **Git** and **GitHub CLI** (`gh`) — [install guide](https://cli.github.com/)
+- **An AI coding agent**, authenticated and ready:
+  - **Claude Code**: `claude` · **Cursor CLI**: `cursor` · **Gemini CLI**: `gemini`
+  - If prompted to log in, complete auth first — Shep can't authenticate on your behalf.
+
+> **Sandbox mode note:** Some agents restrict network access by default. If operations like `npm install` fail, configure allowed hosts in your agent's settings or disable sandbox for Shep features. See [Agent Permissions](#agent-permissions).
+
+### Install and run
+
 ```bash
 # Try it instantly — no install needed
 npx @shepai/cli
 
 # Or install globally
 npm i -g @shepai/cli
+
+# Start Shep — opens the web dashboard at localhost:4050
 shep
+```
+
+### Your first feature
 
-# Browser opens at http://localhost:4050 — you're in
+```bash
+cd ~/projects/my-app        # Any git repo. Shep uses the repo you're in.
+shep feat new "add a /health endpoint that returns uptime and version" --push --pr
+
+# Shep creates a worktree, runs your agent, commits, pushes, and opens a PR.
 ```
 
----
+Not in a git repo? Shep initializes one for you — `git init`, creates a branch, and starts working.
 
-## Features
+### Go parallel
 
 ```bash
-shep feat new "add stripe payments" --allow-all --push --pr
-# ↳ PRD → research → plan → code → tests → PR → CI watch — done.
+shep feat new "add stripe payments" --push --pr
+shep feat new "add dark mode toggle" --push --pr
+shep feat new "refactor auth middleware" --push --pr
+# All three run simultaneously in the same repo. Each in its own worktree.
 ```
 
-- **Full lifecycle in one shot** — From idea to merged PR: requirements, technical research, implementation plan, code with tests, PR creation, and CI fix loop
-- **Approve or go hands-free** — Three review gates (PRD, Plan, Merge) you can enable, disable, or skip entirely with `--allow-all`
-- **Run 10 features in parallel** — Each gets its own git worktree — switch context instantly, no stashing, no branch juggling, no conflicts
-- **Pick your agent** — Claude Code, Cursor CLI, or Gemini CLI — swap per feature, per repo, anytime
-- **Live dashboard** — Interactive graph of every repo and feature — review diffs, approve merges, launch dev servers, all in-browser
-- **100% local, zero signup** — SQLite in `~/.shep/`, nothing leaves your machine, no account needed
+Or work across multiple repos:
 
-> **[See the full Features Guide with screenshots →](./docs/FEATURES.md)**
+```bash
+shep feat new "add payments" --repo ~/projects/backend --push --pr
+shep feat new "add checkout UI" --repo ~/projects/frontend --push --pr
+```
 
 ---
 
-## CLI Reference
+## How It Works
 
-### Daemon
+The default flow is simple: **prompt → implement → commit → push → PR**.
 
 ```
-shep                                  Start daemon + onboarding (first run)
-shep start [--port <number>]          Start web UI daemon (background, default port 4050)
-shep stop                             Stop the running daemon
-shep restart                          Restart the daemon
-shep status                           Show daemon status and live metrics
-shep ui [--port] [--no-open]          Start the web UI in the foreground
+ You describe       Agent codes         Shep commits        Shep pushes         Shep opens
+ a feature    →     in a worktree  →    the changes    →    to remote      →    a PR
+```
+
+Shep creates an isolated git worktree, hands your prompt to the agent, and handles everything after: committing, pushing, and opening a PR. If CI fails, Shep reads the logs, fixes the issue, and retries (configurable).
+
+### Configure everything
+
+Every step of the pipeline is configurable. Turn things on or off per feature or set defaults:
+
+| Flag | What it does | Default |
+|------|-------------|---------|
+| `--push` | Auto-push after implementation | off |
+| `--pr` | Auto-create PR after push | off |
+| `--fast` | Skip spec-driven phases, go straight to coding | on |
+| `--allow-merge` | Auto-merge the PR after CI passes | off |
+| `--allow-all` | Enable all automations | off |
+| `--model` | Choose which AI model to use | agent default |
+| `--attach` | Attach reference files for context | — |
+
+Use `shep settings workflow` to set your defaults so you don't repeat flags.
+
+### Optional: Spec-Driven Development
+
+For complex features, enable the full structured pipeline with requirements, research, and planning phases:
+
+```bash
+# Disable --fast to get the full pipeline
+shep feat new "redesign the payment system" --no-fast --push --pr
 ```
 
-### Feature Management
+This adds **approval gates** where Shep pauses for your review:
 
 ```
-shep feat new <description>           Create a new feature
-      [--repo] [--push] [--pr]
-      [--allow-prd] [--allow-plan] [--allow-merge] [--allow-all]
-      [--parent] [--fast] [--model] [--attach]
-shep feat ls [--repo]                 List features
-shep feat show <id>                   Show feature details
-shep feat del <id>                    Delete a feature
-shep feat resume <id>                 Resume a paused feature
-shep feat review <id>                 Review a feature
-shep feat approve <id> [--comments]   Approve a feature
-shep feat reject <id> [--feedback]    Reject a feature
-shep feat logs <id>                   View feature logs
+ Prompt  →  Requirements  →  Research  →  Plan  →  Implement  →  Commit  →  PR
+                 ▲                          ▲                                ▲
+             Gate 1: PRD              Gate 2: Plan                    Gate 3: Merge
 ```
 
-### Agent Management
+Each gate produces a YAML artifact you can read, edit, and approve before the agent continues. Use `--allow-prd` and `--allow-plan` to auto-approve individual gates, or keep them manual for full control.
+
+> **[Spec-Driven Development guide →](./docs/development/spec-driven-workflow.md)**
+
+---
+
+## Features
+
+### Parallel Sessions
+
+Run multiple features at once. Each gets its own git worktree — isolated branch, isolated files, zero conflicts. Monitor all of them from one dashboard.
+
+### Prompt to PR
+
+One command: `shep feat new "do X" --push --pr`. Agent implements, Shep commits, pushes, opens a PR. Done.
+
+### Agent-Agnostic
+
+Use Claude Code, Cursor CLI, or Gemini CLI. Swap per feature, per repo, anytime. If it runs in a terminal, Shep can orchestrate it.
+
+### Web Dashboard + CLI
+
+Two ways to manage everything. The dashboard at `localhost:4050` shows a visual graph of all repos and features with real-time status, diff review, and interactive chat. The CLI gives you the same control from the terminal.
+
+### CI Watch & Auto-Fix
+
+Shep watches your CI pipeline after push. If it fails, the agent reads the logs, diagnoses the problem, and pushes a fix. Retries are configurable (default: 3). Works best when CI produces clear error messages.
+
+### Everything Configurable
+
+Push, PR, merge, CI watch, CI fix retries, timeouts, model selection, agent type — configure per feature with flags or set global defaults with `shep settings`. Nothing is hardcoded.
+
+### 100% Local
+
+All data lives in `~/.shep/` as SQLite. No cloud, no account, no tracking. Your code is only sent to whichever AI agent you configure, under that agent's own terms.
+
+### Optional: Spec-Driven Development
+
+When you need more structure — requirements, technical research, implementation plans with approval gates. Produces versioned YAML artifacts you review before any code is written. Enable per feature with `--no-fast`.
+
+---
+
+## What Happens When Things Go Wrong
+
+- **CI fails.** Shep reads the logs, diagnoses the problem, and pushes a fix. Retries up to 3 times (configurable), then pauses and asks you.
+- **Agent gets stuck.** The feature enters a `Blocked` state. You get notified and can provide feedback or restart from a checkpoint.
+- **You need to stop immediately.** Run `shep agent stop <id>` or hit the stop button in the dashboard. The worktree is preserved — resume or take over manually.
+- **You want to take over.** The code lives in a standard git worktree on a named branch. Open it in your IDE at any point.
+- **Too many features in flight.** Each feature is independent. Stop, pause, or delete any of them without affecting the others.
+
+---
+
+## Trust & Safety
+
+Shep runs entirely on your machine.
+
+| Concern | How Shep handles it |
+|---------|-------------------|
+| **Data stays local** | All data in `~/.shep/` as SQLite. Nothing sent to Shep servers — there are none. |
+| **Agent permissions** | Shep runs your agent with permission-bypass flags to avoid blocking the automated pipeline. See [Agent Permissions](#agent-permissions) below. |
+| **Git isolation** | Every feature runs in its own worktree branched from main. Your working directory is never modified. |
+| **No credential access** | Shep never reads, stores, or transmits your API keys. |
+| **Agent mistakes** | Shep creates a draft PR. Your CI, linters, and security scanners run before any merge. Shep does not merge code that fails CI. |
+| **Review before merge** | Unless you pass `--allow-merge`, no code is merged without your approval. |
+| **Full audit trail** | Every action and state transition is logged. View with `shep feat logs <id>`. |
+
+### Agent Permissions
+
+Shep runs your agent non-interactively — it can't pause for "allow this command?" prompts mid-pipeline. By default, it passes permission-bypass flags (e.g., `--dangerously-skip-permissions` for Claude Code — each agent has an equivalent).
+
+**Your safety net is three layers deep:**
+1. **Worktree isolation** — the agent works on a copy, not your checkout
+2. **Draft PRs** — you review the diff before anything is merged
+3. **CI pipeline** — your tests, linters, and security scanners run before merge
+
+The skip-permissions flag is a default, not a requirement. Configure your agent's permission model independently if you need tighter control.
+
+**What Shep does NOT protect you from:** If your CI doesn't catch a vulnerability, Shep won't either. Shep is an orchestration layer, not a security scanner.
+
+---
+
+## Supported Agents & Tools
+
+| Category | Supported |
+|----------|-----------|
+| **AI Agents** | Claude Code, Cursor CLI, Gemini CLI |
+| **IDEs** | VS Code, Cursor, Zed, Windsurf, and more |
+| **Required** | Git, GitHub CLI (`gh`) |
+
+---
+
+## CLI Reference
+
+### Core Commands
 
 ```
-shep agent ls                         List agents
-shep agent show <id>                  Show agent details
-shep agent stop <id>                  Stop a running agent
-shep agent logs <id>                  View agent logs
-shep agent delete <id>                Delete an agent
-shep agent approve <id>               Approve an agent action
-shep agent reject <id>                Reject an agent action
+shep                              Start daemon + onboarding (first run)
+shep feat new <description>       Create a new feature
+      [--push] [--pr] [--fast] [--model] [--attach]
+      [--allow-prd] [--allow-plan] [--allow-merge] [--allow-all]
+shep feat ls                      List features
+shep feat show <id>               Show feature details
+shep feat resume <id>             Resume a paused feature
+shep feat approve <id>            Approve current phase (spec-driven mode)
+shep feat reject <id> --feedback  Reject with feedback (spec-driven mode)
+shep feat logs <id>               View feature logs
 ```
 
-### Repository & Session Management
+### Stopping a Feature
 
 ```
-shep repo ls                          List repositories
-shep repo show <id>                   Show repository details
-shep session ls                       List sessions
-shep session show <id>                Show session details
+shep agent stop <id>              Stop a running agent immediately
+shep agent ls                     Find the agent ID for a feature
 ```
 
-### Settings
+The web dashboard also has a stop button on every in-progress feature.
+
+### Daemon & Dashboard
 
 ```
-shep settings                         Launch setup wizard
-shep settings show                    Display current configuration
-shep settings init                    Initialize settings
-shep settings agent                   Configure AI coding agent
-shep settings ide                     Configure IDE
-shep settings workflow                Configure workflow
-shep settings model                   Configure model
+shep start [--port]               Start web daemon (default: 4050)
+shep stop                         Stop the daemon
+shep status                       Show daemon status and metrics
+shep ui                           Start web UI in foreground
 ```
 
-### Tools
+### Settings & Configuration
 
 ```
-shep tools list                       List tools with install status
-shep install <tool> [--how]           Install a dev tool
-shep ide-open [--ide] [--dir]         Open IDE in directory
+shep settings                     Launch setup wizard
+shep settings workflow            Configure default flags (push, pr, ci watch, etc.)
+shep settings agent               Configure AI coding agent
+shep settings ide                 Configure IDE
+shep settings model               Configure default model
 ```
 
-### Other
+### Agent & Repo Management
 
 ```
-shep version                          Show version info
-shep upgrade                          Upgrade to latest version
-shep run <agent> [-p prompt] [-r repo] [-s]   Run an agent directly
+shep agent ls                     List agent runs
+shep agent stop <id>              Stop a running agent
+shep agent logs <id>              View agent logs
+shep repo ls                      List repositories
 ```
 
+> **[Full CLI reference →](./docs/cli/architecture.md)**
+
 ---
 
-## Architecture
+## FAQ
 
-Clean Architecture with four layers. Dependencies point inward — domain has zero external deps.
+**How is this different from just using an AI coding agent directly?**
 
-```mermaid
-flowchart TB
-    P["<b>Presentation</b><br/>CLI · Web UI · TUI"]
-    A["<b>Application</b><br/>Use Cases · Orchestration · Ports"]
-    D["<b>Domain</b><br/>Entities · Value Objects · Services"]
-    I["<b>Infrastructure</b><br/>SQLite · LangGraph · DI"]
+Your agent writes the code. Shep manages the session: creating the worktree, committing, pushing, opening PRs, watching CI, and retrying failures. The difference is most obvious when you're running 3-5 features in parallel — Shep keeps them organized and isolated while you focus on what matters.
 
-    P --> A --> D
-    I --> A
+**How is this different from Superset?**
 
-    style P fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
-    style A fill:#fef3c7,stroke:#f59e0b,color:#78350f
-    style D fill:#d1fae5,stroke:#10b981,color:#064e3b
-    style I fill:#ede9fe,stroke:#8b5cf6,color:#4c1d95
-```
+Superset is a terminal multiplexer for agents — it runs them in parallel tabs. Shep manages the development lifecycle: worktrees, commits, pushes, PRs, CI. They're complementary. Use Superset for the execution environment, Shep for the workflow.
 
-| Layer          | Path                                | Responsibility                                    |
-| -------------- | ----------------------------------- | ------------------------------------------------- |
-| Domain         | `packages/core/src/domain/`         | Business logic, TypeSpec-generated types          |
-| Application    | `packages/core/src/application/`    | Use cases, output port interfaces                 |
-| Infrastructure | `packages/core/src/infrastructure/` | SQLite repos, LangGraph agents, DI (tsyringe)     |
-| Presentation   | `src/presentation/`                 | CLI (Commander), TUI (Inquirer), Web UI (Next.js) |
+**What happens if the agent writes bad code?**
 
-### Feature Lifecycle
+Shep creates a draft PR. Your CI runs. If tests fail, the agent reads the logs and attempts a fix (up to 3 retries, configurable). If that fails, the feature pauses and you're notified. The agent never merges code that fails CI.
 
-Every feature progresses through a structured SDLC pipeline with 9 states:
+**What about agent sandbox / permission modes?**
 
-```
-Started -> Analyze -> Requirements -> Research -> Planning -> Implementation -> Review -> Maintain
-                                                                                   |
-                                                                               (Blocked)
-```
+Shep runs the agent with permission-bypass flags by default so the pipeline isn't blocked by interactive prompts. Your protection is worktree isolation, draft PRs, and your CI pipeline. See [Agent Permissions](#agent-permissions).
 
-Human approval gates are configurable at PRD, Plan, and Merge phases. In `--allow-all` mode the agent handles everything autonomously.
+**Does this work on large codebases?**
 
-### Tech Stack
+Yes. The practical limit is the underlying agent's context window, not Shep. If your agent handles your repo well directly, Shep will too. For monorepos, scope features to specific packages with `--repo`.
 
-| Component       | Technology                                                                |
-| --------------- | ------------------------------------------------------------------------- |
-| Language        | TypeScript (ES2022)                                                       |
-| Package Manager | pnpm                                                                      |
-| CLI Framework   | Commander                                                                 |
-| TUI Framework   | [@inquirer/prompts](https://github.com/SBoudrias/Inquirer.js)             |
-| Web UI          | Next.js 16 + React 19 + shadcn/ui + Tailwind CSS 4                        |
-| Graph Viz       | React Flow (XYFlow) 12                                                    |
-| Design System   | Storybook 8.x                                                             |
-| Build Tool      | tsc + tsc-alias (prod), tsx (CLI dev), Next.js (web dev)                  |
-| Database        | SQLite (better-sqlite3, per-repo)                                         |
-| Domain Models   | TypeSpec -> generated TypeScript                                          |
-| Agent System    | [LangGraph](https://www.langchain.com/langgraph) (`@langchain/langgraph`) |
-| DI Container    | tsyringe                                                                  |
-| Testing         | Vitest (unit/integration) + Playwright (e2e)                              |
-| Methodology     | TDD (Red-Green-Refactor)                                                  |
+**Can I use this on a team?**
 
-### Supported Tools
+Shep runs locally on your git repo. Multiple team members can run Shep independently. Features are just branches and PRs — your existing review process applies.
 
-Shep can detect, install, and manage the following tools:
+**Is my code sent anywhere?**
 
-| Category   | Tools                                                                             |
-| ---------- | --------------------------------------------------------------------------------- |
-| IDEs       | Alacritty, Antigravity, Cursor, iTerm2, Kitty, TMux, VS Code, Warp, Windsurf, Zed |
-| CLI Agents | Claude Code, Cursor CLI, Gemini CLI                                               |
-| Dev Tools  | Git, GitHub CLI                                                                   |
+Not by Shep. Your code is sent to whichever AI agent you configure, under that agent's own privacy terms. Shep stores everything locally and makes no network calls.
 
-### Web UI
+**What's the spec-driven mode?**
 
-The web dashboard runs at `http://localhost:4050` and provides:
+An optional structured pipeline that adds requirements, research, and planning phases with approval gates before any code is written. Useful for complex features where you want to review the approach first. Enable with `--no-fast`. [Learn more →](./docs/development/spec-driven-workflow.md)
 
-- **Dashboard canvas** — Interactive React Flow graph with feature and repository nodes
-- **Feature drawer** — Tabs for overview, activity, approval, rejection, PR info, deployment, and timeline
-- **Create feature form** — Start new features from the UI
-- **Settings, Tools, Skills, and Version pages**
-- **Real-time updates** via Server-Sent Events (SSE)
+**How do I stop a feature that's running?**
 
-### Data Model
+CLI: `shep agent stop <id>`. Dashboard: click the stop button. The worktree is preserved — resume with `shep feat resume <id>` or work on it manually.
 
-```
-Repository --+-- Feature --+-- Plan --+-- Task -- ActionItem
-             |             |          +-- Artifact
-             |             +-- Requirement -- Research
-```
+---
 
-All data lives locally in `~/.shep/`. Per-repo SQLite databases. No cloud dependency.
+## Architecture
 
----
+Shep follows Clean Architecture with four layers. For contributors and the curious:
+
+| Layer | Responsibility |
+|-------|---------------|
+| **Domain** | Business logic, TypeSpec-generated types |
+| **Application** | Use cases, port interfaces |
+| **Infrastructure** | SQLite, LangGraph agents, DI |
+| **Presentation** | CLI, Web UI |
 
-## Documentation
-
-| Document                                           | Description                                |
-| -------------------------------------------------- | ------------------------------------------ |
-| [Features Guide](./docs/FEATURES.md)               | Full features overview with screenshots    |
-| [Competitive Landscape](./docs/competitors/)       | How Shep fits in the AI dev tool ecosystem |
-| [CLAUDE.md](./CLAUDE.md)                           | Guidance for Claude Code instances         |
-| [AGENTS.md](./AGENTS.md)                           | Agent system architecture                  |
-| [CONTRIBUTING-AGENTS.md](./CONTRIBUTING-AGENTS.md) | AI agent contribution guidelines           |
-| [Architecture](./docs/architecture/)               | System design and patterns                 |
-| [Concepts](./docs/concepts/)                       | Core domain concepts                       |
-| [UI](./docs/ui/)                                   | Web UI architecture and design system      |
-| [Guides](./docs/guides/)                           | User guides and tutorials                  |
-| [Development](./docs/development/)                 | Contributing and development setup         |
-| [API Reference](./docs/api/)                       | Interface and model documentation          |
+> **[Full architecture docs →](./docs/architecture/overview.md)**
+
+---
 
 ## Contributing
 
-We welcome contributions from humans and AI agents alike.
+See [CONTRIBUTING.md](./CONTRIBUTING.md) for humans and [CONTRIBUTING-AGENTS.md](./CONTRIBUTING-AGENTS.md) for AI agents.
 
-- **Humans**: See [CONTRIBUTING.md](./CONTRIBUTING.md)
-- **AI Agents**: See [CONTRIBUTING-AGENTS.md](./CONTRIBUTING-AGENTS.md)
-- **Spec-driven workflow**: All features start with `/shep-kit:new-feature` — see [Spec-Driven Workflow](./docs/development/spec-driven-workflow.md)
+---
 
 ## License
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@shepai/cli",
-  "version": "1.156.0-pr487.27d2745",
+  "version": "1.156.0-pr489.56abb36",
   "description": "Autonomous AI Native SDLC Platform - Automate the development cycle from idea to deploy",
   "type": "module",
   "license": "MIT",

package/web/.next/BUILD_ID

@@ -1 +1 @@
-YJAjXJ0PmVhoQ7S_uBBDz
+KB8KOezkUq0uueUEtffWG

package/web/.next/build-manifest.json

@@ -7,8 +7,8 @@
     "static/chunks/a6dad97d9634a72d.js"
   ],
   "lowPriorityFiles": [
-    "static/YJAjXJ0PmVhoQ7S_uBBDz/_ssgManifest.js",
-    "static/YJAjXJ0PmVhoQ7S_uBBDz/_buildManifest.js"
+    "static/KB8KOezkUq0uueUEtffWG/_ssgManifest.js",
+    "static/KB8KOezkUq0uueUEtffWG/_buildManifest.js"
   ],
   "rootMainFiles": [
     "static/chunks/40b6bcf1a2de4a0f.js",

package/web/.next/fallback-build-manifest.json

@@ -5,8 +5,8 @@
   "devFiles": [],
   "polyfillFiles": [],
   "lowPriorityFiles": [
-    "static/YJAjXJ0PmVhoQ7S_uBBDz/_ssgManifest.js",
-    "static/YJAjXJ0PmVhoQ7S_uBBDz/_buildManifest.js"
+    "static/KB8KOezkUq0uueUEtffWG/_ssgManifest.js",
+    "static/KB8KOezkUq0uueUEtffWG/_buildManifest.js"
   ],
   "rootMainFiles": []
 }

package/web/.next/prerender-manifest.json

@@ -29,8 +29,8 @@
   "dynamicRoutes": {},
   "notFoundRoutes": [],
   "preview": {
-    "previewModeId": "1d451a3c2e243cb27e5eece34a79805d",
-    "previewModeSigningKey": "001b187ba6b4dce6523b730adb690cf965e808029d0bf1bd1ef75820a00b3923",
-    "previewModeEncryptionKey": "0491450cae0a1ed19ad10f052db346a5f5f0980fbf5636b5505a1ad85f678c30"
+    "previewModeId": "afb097a152698f92f1d18b2232664fc4",
+    "previewModeSigningKey": "ff5f87535773ce01b078c0f91ac62ec9e1bee6b7ea3661e12713cd2f3143d9fa",
+    "previewModeEncryptionKey": "30799d8c52838aa7a943d545dfed8280ec09dde1062d6940041c8a5078e925d6"
   }
 }

package/web/.next/required-server-files.js

@@ -6,7 +6,7 @@ self.__SERVER_FILES_MANIFEST={
       "NEXT_PUBLIC_SHEP_PACKAGE_NAME": "@shepai/cli",
       "NEXT_PUBLIC_SHEP_DESCRIPTION": "Autonomous AI Native SDLC Platform - Automate the development cycle from idea to deploy",
       "NEXT_PUBLIC_SHEP_BRANCH": "HEAD",
-      "NEXT_PUBLIC_SHEP_COMMIT": "27d274531164a8f64cf59159a496e4cfcc651ad9",
+      "NEXT_PUBLIC_SHEP_COMMIT": "56abb369ad9bca4bbc6f0fafee246c2aff87bc6d",
       "NEXT_PUBLIC_SHEP_INSTANCE_PATH": "/home/runner/work/cli/cli/src/presentation/web"
     },
     "webpack": null,

package/web/.next/required-server-files.json

@@ -6,7 +6,7 @@
       "NEXT_PUBLIC_SHEP_PACKAGE_NAME": "@shepai/cli",
       "NEXT_PUBLIC_SHEP_DESCRIPTION": "Autonomous AI Native SDLC Platform - Automate the development cycle from idea to deploy",
       "NEXT_PUBLIC_SHEP_BRANCH": "HEAD",
-      "NEXT_PUBLIC_SHEP_COMMIT": "27d274531164a8f64cf59159a496e4cfcc651ad9",
+      "NEXT_PUBLIC_SHEP_COMMIT": "56abb369ad9bca4bbc6f0fafee246c2aff87bc6d",
       "NEXT_PUBLIC_SHEP_INSTANCE_PATH": "/home/runner/work/cli/cli/src/presentation/web"
     },
     "webpack": null,