refactor: migrate documentation to new site and remove old files

chore: update command references from 'lspec' to 'lean-spec'

fix: adjust temporary directory naming in tests for consistency

docs: remove migration guide and custom fields guide from docs

style: update README and templates to reflect new command structure

test: clean up integration test scripts and remove obsolete files

Author: Marvin Zhang

.github/workflows/copilot-setup-steps.yml

@@ -43,12 +43,12 @@ jobs:
       - name: Build project
         run: pnpm run build
 
-      - name: Install lspec CLI globally
+      - name: Install lean-spec CLI globally
         run: pnpm link --global
 
-      - name: Verify lspec installation
+      - name: Verify lean-spec installation
         run: |
-          echo "lspec version:"
-          lspec --version
+          echo "lean-spec version:"
+          lean-spec --version
           echo ""
-          echo "lspec is now available globally for Copilot coding agent to use"
+          echo "lean-spec is now available globally for Copilot coding agent to use"

.vscode/mcp.json

@@ -2,7 +2,7 @@
 	"servers": {
 		"lean-spec": {
 			"type": "stdio",
-			"command": "lspec",
+			"command": "lean-spec",
 			"args": ["mcp"]
 		}
 	},

AGENTS.md

@@ -83,10 +83,10 @@ When practices conflict, apply principles in priority order:
 
 1. **Read README.md first** - Understand project context
 2. **Check specs/** - Review existing specs before starting
-3. **Use `lspec --help`** - When unsure about commands, check the built-in help
+3. **Use `lean-spec --help`** - When unsure about commands, check the built-in help
 4. **Follow LeanSpec principles** - Clarity over documentation
 5. **Keep it minimal** - If it doesn't add clarity, cut it
-6. **NEVER manually edit system-managed frontmatter** - Fields like `status`, `priority`, `tags`, `assignee`, `transitions`, `created_at`, `updated_at`, `completed_at` are system-managed. Always use `lspec update` or `lspec create` commands. Manual edits will cause metadata corruption and tracking issues. **Exception**: Relationship fields (`depends_on`, `related`) must currently be edited manually as no CLI command exists yet.
+6. **NEVER manually edit system-managed frontmatter** - Fields like `status`, `priority`, `tags`, `assignee`, `transitions`, `created_at`, `updated_at`, `completed_at` are system-managed. Always use `lean-spec update` or `lean-spec create` commands. Manual edits will cause metadata corruption and tracking issues. **Exception**: Relationship fields (`depends_on`, `related`) must currently be edited manually as no CLI command exists yet.
 7. **Never use nested code blocks** - Markdown doesn't support code blocks within code blocks. If you need to show code examples in documentation, use indentation or describe the structure instead of nesting backticks.
 
 ## When to Use Specs
@@ -204,7 +204,7 @@ Required By:
 **Critical - Frontmatter Editing Rules**:
 
 **NEVER manually edit these system-managed fields:**
-- `status`, `priority`, `tags`, `assignee` - Use `lspec update` commands only
+- `status`, `priority`, `tags`, `assignee` - Use `lean-spec update` commands only
 - `transitions`, `created_at`, `updated_at`, `completed_at` - Automatically managed by the system
 - Manual edits will corrupt metadata, break tracking, and cause validation failures
 

docs-site/docs/guide/getting-started.mdx

@@ -185,7 +185,7 @@ For a complete command reference, see [CLI Commands](/docs/reference/cli).
 
 ## AI Integration (Optional)
 
-LeanSpec works great with AI coding agents. When you ran `lspec init`, it created `AGENTS.md` with instructions for AI agents.
+LeanSpec works great with AI coding agents. When you ran `lean-spec init`, it created `AGENTS.md` with instructions for AI agents.
 
 ### Quick AI Setup
 

docs-site/docs/guide/usage/advanced-features/custom-fields.mdx

@@ -43,19 +43,19 @@ Edit `.lean-spec/config.json`:
 
 **When creating specs:**
 ```bash
-lspec create user-auth --field epic=PROJ-123 --field sprint=42
+lean-spec create user-auth --field epic=PROJ-123 --field sprint=42
 ```
 
 **When updating specs:**
 ```bash
-lspec update 001 --field reviewer=alice --field estimate=large
+lean-spec update 001 --field reviewer=alice --field estimate=large
 ```
 
 **When filtering:**
 ```bash
-lspec list --field epic=PROJ-123
-lspec list --field sprint=42
-lspec search "API" --field team=backend
+lean-spec list --field epic=PROJ-123
+lean-spec list --field sprint=42
+lean-spec search "API" --field team=backend
 ```
 
 ### Example Configuration
@@ -164,7 +164,7 @@ Documentation: {docs_url}
 When you create a spec, all variables are automatically resolved:
 
 ```bash
-lspec create user-authentication
+lean-spec create user-authentication
 ```
 
 Results in:
@@ -197,7 +197,7 @@ Documentation: https://docs.acme.com
 
 **Basic custom field usage:**
 ```bash
-lspec create user-authentication \
+lean-spec create user-authentication \
   --field epic=AUTH-2024 \
   --field sprint=5 \
   --field estimate=3d \
@@ -206,7 +206,7 @@ lspec create user-authentication \
 
 **With all options:**
 ```bash
-lspec create payment-integration \
+lean-spec create payment-integration \
   --title "Stripe Payment Integration" \
   --description "Integrate Stripe for subscription payments" \
   --tags backend,payment,api \
@@ -222,12 +222,12 @@ lspec create payment-integration \
 **Updating custom fields:**
 ```bash
 # Update custom fields only
-lspec update 001-user-authentication \
+lean-spec update 001-user-authentication \
   --field sprint=6 \
   --field estimate=2d
 
 # Update standard and custom fields together
-lspec update 001-user-authentication \
+lean-spec update 001-user-authentication \
   --status in-progress \
   --priority high \
   --field sprint=6
@@ -236,19 +236,19 @@ lspec update 001-user-authentication \
 **Filtering by custom fields:**
 ```bash
 # Filter by epic
-lspec list --field epic=AUTH-2024
+lean-spec list --field epic=AUTH-2024
 
 # Filter by sprint
-lspec list --field sprint=5
+lean-spec list --field sprint=5
 
 # Combine with standard filters
-lspec list --status in-progress --field sprint=6
+lean-spec list --status in-progress --field sprint=6
 
 # Multiple custom fields
-lspec list --field epic=AUTH-2024 --field sprint=6
+lean-spec list --field epic=AUTH-2024 --field sprint=6
 
 # Search with custom field filter
-lspec search "authentication" --field epic=AUTH-2024
+lean-spec search "authentication" --field epic=AUTH-2024
 ```
 
 ### Agile Team Setup
@@ -386,13 +386,13 @@ LeanSpec automatically coerces values to the correct type:
 
 ```bash
 # "42" is converted to number 42
-lspec create feature --field sprint=42
+lean-spec create feature --field sprint=42
 
 # "true" is converted to boolean true
-lspec create feature --field needs_review=true
+lean-spec create feature --field needs_review=true
 
 # Arrays work with comma separation
-lspec create feature --field teams=backend,frontend
+lean-spec create feature --field teams=backend,frontend
 ```
 
 ## Limitations
@@ -408,7 +408,7 @@ If you add custom fields to existing specs:
 
 ```bash
 # Update existing specs manually or with a script
-lspec update 001 --field epic=PROJ-123
+lean-spec update 001 --field epic=PROJ-123
 
 # Or edit frontmatter directly in each README.md
 ```

docs-site/docs/guide/usage/advanced-features/frontmatter.mdx

@@ -52,7 +52,7 @@ Date when spec was created (ISO 8601 format).
 created: 2025-11-02
 ```
 
-This is auto-filled when you use `lspec create`.
+This is auto-filled when you use `lean-spec create`.
 
 ## Optional Fields
 
@@ -67,7 +67,7 @@ tags: [api, security, mvp]
 
 **Usage:**
 ```bash
-lspec list --tag=api
+lean-spec list --tag=api
 ```
 
 ### priority
@@ -87,7 +87,7 @@ priority: high
 
 **Usage:**
 ```bash
-lspec list --priority=high
+lean-spec list --priority=high
 ```
 
 ### completed
@@ -129,8 +129,8 @@ You can define custom fields in `.lean-spec/config.json`:
 
 **Usage:**
 ```bash
-lspec create feature --field assignee=alice --field sprint=42
-lspec list --field epic=PROJ-123
+lean-spec create feature --field assignee=alice --field sprint=42
+lean-spec list --field epic=PROJ-123
 ```
 
 See [Custom Fields](/docs/guide/usage/advanced-features/custom-fields) for details.
@@ -149,7 +149,7 @@ LeanSpec auto-generates visual badges from frontmatter:
 - ✅ Complete
 - 📦 Archived
 
-These badges are automatically updated when you use `lspec update`.
+These badges are automatically updated when you use `lean-spec update`.
 
 ## Full Example
 
@@ -181,7 +181,7 @@ sprint: 42
 Recommended approach:
 
 ```bash
-lspec update 001 --status=complete --priority=critical
+lean-spec update 001 --status=complete --priority=critical
 ```
 
 This updates both frontmatter and visual badges.
@@ -194,7 +194,7 @@ You can also edit frontmatter directly in the file:
 2. Modify YAML between `---` markers
 3. Save file
 
-Note: Manual edits don't auto-update visual badges. Run `lspec update` to sync.
+Note: Manual edits don't auto-update visual badges. Run `lean-spec update` to sync.
 
 ## Best Practices
 
@@ -207,7 +207,7 @@ Establish tag conventions for your team. Examples: `api`, `ui`, `backend`, `secu
 :::
 
 :::tip Update Status Regularly
-Keep status current. Use `lspec list` to see what's in progress.
+Keep status current. Use `lean-spec list` to see what's in progress.
 :::
 
 :::tip Don't Over-Customize

docs-site/docs/guide/usage/advanced-features/variables.mdx

@@ -31,10 +31,10 @@ These variables are available automatically:
 
 ### \{name\}
 
-The spec name provided to `lspec create`.
+The spec name provided to `lean-spec create`.
 
 ```bash
-lspec create user-authentication
+lean-spec create user-authentication
 ```
 
 Results in:

docs-site/docs/guide/usage/ai-assisted/agent-configuration.mdx

@@ -9,7 +9,7 @@ Configure AI coding agents to work effectively with LeanSpec through AGENTS.md i
 
 ## AGENTS.md Overview
 
-`AGENTS.md` serves as permanent instructions for AI coding agents in your repository. When you run `lspec init`, this file is created with LeanSpec guidance.
+`AGENTS.md` serves as permanent instructions for AI coding agents in your repository. When you run `lean-spec init`, this file is created with LeanSpec guidance.
 
 **Purpose:**
 - Provide context about your project
@@ -48,22 +48,22 @@ Skip specs for:
 ## Essential Commands
 
 **Discovery:**
-- `lspec list` - See all specs
-- `lspec search "<query>"` - Find relevant specs
-- `lspec board` - Kanban view with project health
-- `lspec stats` - Quick project metrics
+- `lean-spec list` - See all specs
+- `lean-spec search "<query>"` - Find relevant specs
+- `lean-spec board` - Kanban view with project health
+- `lean-spec stats` - Quick project metrics
 
 **Viewing specs:**
-- `lspec view <spec>` - View a spec (formatted)
-- `lspec view <spec> --raw` - Get raw markdown
-- `lspec view <spec> --json` - Get structured JSON
-- `lspec open <spec>` - Open spec in editor
-- `lspec files <spec>` - List all files in a spec
+- `lean-spec view <spec>` - View a spec (formatted)
+- `lean-spec view <spec> --raw` - Get raw markdown
+- `lean-spec view <spec> --json` - Get structured JSON
+- `lean-spec open <spec>` - Open spec in editor
+- `lean-spec files <spec>` - List all files in a spec
 
 **Working with specs:**
-- `lspec create <name>` - Create a new spec
-- `lspec update <spec> --status <status>` - Update status
-- `lspec deps <spec>` - Show dependencies
+- `lean-spec create <name>` - Create a new spec
+- `lean-spec update <spec> --status <status>` - Update status
+- `lean-spec deps <spec>` - Show dependencies
 
 ## Spec Frontmatter
 
@@ -78,14 +78,14 @@ priority: low|medium|high  # optional
 ---
 ```
 
-**IMPORTANT**: Always use `lspec update` to modify status, priority, tags, and assignee. Never edit frontmatter manually for these system-managed fields.
+**IMPORTANT**: Always use `lean-spec update` to modify status, priority, tags, and assignee. Never edit frontmatter manually for these system-managed fields.
 
 ## SDD Workflow
 
-1. **Discover** - Check existing specs with `lspec list`
-2. **Plan** - Create spec with `lspec create <name>` when needed
+1. **Discover** - Check existing specs with `lean-spec list`
+2. **Plan** - Create spec with `lean-spec create <name>` when needed
 3. **Implement** - Write code, keep spec in sync as you learn
-4. **Update** - Mark progress with `lspec update <spec> --status <status>`
+4. **Update** - Mark progress with `lean-spec update <spec> --status <status>`
 5. **Complete** - Mark complete when done
 
 ## Quality Standards
@@ -94,7 +94,7 @@ priority: low|medium|high  # optional
 - Tests cover critical paths
 - Specs stay in sync with implementation
 - Always validate before completing work:
-  - Run `lspec validate` to check spec structure
+  - Run `lean-spec validate` to check spec structure
   - Fix any validation errors before marking complete
 
 ## [Project-Specific Rules]
@@ -281,25 +281,25 @@ Ask your AI agent:
 ```
 List all specs in this repository.
 ```
-Expected: Agent uses `lspec list`
+Expected: Agent uses `lean-spec list`
 
 **Test 2: Can it read specs?**
 ```
 What does spec 001 describe?
 ```
-Expected: Agent uses `lspec view 001`
+Expected: Agent uses `lean-spec view 001`
 
 **Test 3: Can it follow workflow?**
 ```
 Create a spec for user authentication.
 ```
-Expected: Agent uses `lspec create user-authentication`
+Expected: Agent uses `lean-spec create user-authentication`
 
 **Test 4: Can it update status?**
 ```
 Mark spec 001 as in-progress.
 ```
-Expected: Agent uses `lspec update 001 --status in-progress`
+Expected: Agent uses `lean-spec update 001 --status in-progress`
 
 ## Common Pitfalls
 
@@ -316,7 +316,7 @@ It's important to...
 ✅ **Good:**
 ```markdown
 1. Read README.md first
-2. Check existing specs with `lspec list`
+2. Check existing specs with `lean-spec list`
 3. Follow LeanSpec principles (see AGENTS.md)
 ```
 

docs-site/docs/guide/usage/ai-assisted/mcp-integration.mdx

@@ -104,7 +104,7 @@ Ask your AI assistant:
 List all specs in this project.
 ```
 
-Expected: AI uses MCP to call `lspec list` and shows results.
+Expected: AI uses MCP to call `lean-spec list` and shows results.
 
 ```
 What does spec 042 describe?
@@ -256,7 +256,7 @@ The LeanSpec MCP server provides these tools to AI assistants:
 **Check:**
 1. MCP server is configured in settings
 2. `cwd` points to correct project directory
-3. Project has specs (run `lspec list` manually)
+3. Project has specs (run `lean-spec list` manually)
 4. Restart AI tool after config changes
 
 ### MCP Commands Not Working