chore: rename lean-spec → leanspec / @leanspec/cli (Part of codervisor/leanspec#254) (#7)

Sync to the upstream codebase rename in codervisor/leanspec#254.

Substitutions applied across en + zh-Hans content (.mdx / .md / .json /
.ts), driven by an ordered ruleset to avoid clobbering things that did
NOT rename:

- `lean-spec.dev`        — domain stays (leanspec.dev is taken)
- `lean-spec-docs`       — this repo's slug stays
- `lean-spec-desktop`    — separate repo
- `.lean-spec/`          — project config directory unchanged

Renamed:

- GitHub URLs: codervisor/lean-spec → codervisor/leanspec
- npm CLI package: lean-spec → @leanspec/cli (anti-typosquatting fallback)
- MCP server package: lean-spec (bin) → @leanspec/mcp (separate package)
- Bare CLI invocation: `lean-spec <cmd>` → `leanspec <cmd>` (incl. --flags
  and shell pipes)
- MCP config key in JSON examples: "lean-spec" → "leanspec"
- Multi-project MCP keys: "lean-spec-projectA" → "leanspec-projectA"
- Anchor links: #lean-spec-<cmd> → #leanspec-<cmd>
- docusaurus.config.ts projectName + editUrl + footer links
- AGENTS.md + footer translations

Build verified: `tsc --noEmit` clean, `docusaurus build` clean for both
en and zh-Hans (config has `onBrokenLinks: 'throw'`, so any broken
internal anchor would have failed the build).

82 files changed.

Co-authored-by: Marvin Zhang <tikazyq@gmail.com>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: 3 people

AGENTS.md

@@ -34,14 +34,14 @@ Every English `.mdx` file needs a Chinese translation in `i18n/zh-Hans/docusauru
 Never translate these terms - they are technical concepts with established English usage:
 
 - **Core terms**: Spec, LeanSpec, CLI, Token, README, frontmatter, MCP
-- **Commands**: `lean-spec create`, `lean-spec update`, `lean-spec board`, etc.
+- **Commands**: `leanspec create`, `leanspec update`, `leanspec board`, etc.
 - **Status values**: `planned`, `in-progress`, `complete`, `archived`
 - **File types**: `.md`, `.mdx`, `.json`, `.yaml`
 - **Technical terms**: SDD (Spec-Driven Development), API, JWT, URL, JSON
 
 **Examples:**
 ```markdown
-✅ "使用 `lean-spec create` 创建新 Spec"
+✅ "使用 `leanspec create` 创建新 Spec"
 ❌ "使用 `精益规范创建` 创建新规格说明"
 
 ✅ "Spec 文件使用 Markdown 格式"
@@ -164,8 +164,8 @@ Balance readability with precision:
 ✅ "LeanSpec 是一种轻量级的规格驱动开发 (SDD) 方法论"
 ❌ "LeanSpec 是一个轻量级规范驱动的开发方法"
 
-✅ "使用 `lean-spec board` 查看 Spec 看板"
-❌ "使用 `lean-spec board` 查看规格说明看板"
+✅ "使用 `leanspec board` 查看 Spec 看板"
+❌ "使用 `leanspec board` 查看规格说明看板"
 ```
 
 **Technical Explanations:**
@@ -183,7 +183,7 @@ Balance readability with precision:
 Before committing Chinese translations, verify:
 
 - [ ] All "Spec" references use "Spec" (not "规格" or "规范")
-- [ ] All commands remain in English (e.g., `lean-spec create`)
+- [ ] All commands remain in English (e.g., `leanspec create`)
 - [ ] Technical terms have English references on first use
 - [ ] Chinese text reads naturally (not word-by-word translation)
 - [ ] Full-width punctuation used consistently

blog/2025-11-10-ai-agent-performance.mdx

@@ -154,7 +154,7 @@ We built LeanSpec using LeanSpec itself—the ultimate test of whether this meth
 - Full-featured CLI with 15+ commands
 - MCP server for Cursor, GitHub Copilot integration
 - Documentation site with comprehensive guides
-- [60+ specs](https://github.com/codervisor/lean-spec/tree/main/specs) written and implemented with AI agents
+- [60+ specs](https://github.com/codervisor/leanspec/tree/main/specs) written and implemented with AI agents
 
 **Then we violated our own principles**: Some specs grew to 1,166 lines. We hit the exact problems we were solving:
 - AI agents started corrupting specs during edits
@@ -212,21 +212,21 @@ CLI commands help you detect and fix context issues:
 
 ```bash
 # Install
-npm install -g lean-spec
+npm install -g @leanspec/cli
 
 # Initialize in your project
 cd your-project
-lean-spec init
+leanspec init
 
 # Detect issues
-lean-spec validate              # Check for problems
-lean-spec complexity <spec>     # Analyze size/structure
+leanspec validate              # Check for problems
+leanspec complexity <spec>     # Analyze size/structure
 
 # Fix issues  
-lean-spec split <spec>          # Guided splitting workflow
+leanspec split <spec>          # Guided splitting workflow
 
 # Track progress
-lean-spec board                 # Kanban view of all specs
+leanspec board                 # Kanban view of all specs
 ```
 
 ### Start Simple, Grow as Needed
@@ -242,10 +242,10 @@ The structure adapts to your needs—you never add complexity "just in case."
 ### Try It Today
 
 ```bash
-npm install -g lean-spec
+npm install -g @leanspec/cli
 cd your-project  
-lean-spec init
-lean-spec create user-authentication
+leanspec init
+leanspec create user-authentication
 ```
 
 Your AI coding assistant will thank you.
@@ -269,7 +269,7 @@ LeanSpec is a context engineering methodology for human-AI collaboration on soft
 ---
 
 **Learn more**:
-- GitHub: [github.com/codervisor/lean-spec](https://github.com/codervisor/lean-spec)
+- GitHub: [github.com/codervisor/leanspec](https://github.com/codervisor/leanspec)
 - Docs: [lean-spec.dev](https://lean-spec.dev)
 - Research: [Context Engineering Guide](/docs/advanced/context-engineering)
 

blog/2025-11-25-recent-updates.mdx

@@ -19,10 +19,10 @@ The best way to understand LeanSpec is to use it. That's why we built **example
 
 ```bash
 # See what's available
-npx lean-spec examples
+npx -p @leanspec/cli leanspec examples
 
 # Scaffold an example project
-npx lean-spec init --example dark-theme
+npx -p @leanspec/cli leanspec init --example dark-theme
 cd dark-theme
 npm install
 npm start
@@ -68,7 +68,7 @@ We extracted `@leanspec/mcp` into its own npm package. Setup is now cleaner:
 ```json
 {
   "mcpServers": {
-    "lean-spec": {
+    "leanspec": {
       "command": "npx",
       "args": ["@leanspec/mcp"]
     }
@@ -84,13 +84,13 @@ New commands make relationship management clearer:
 
 ```bash
 # Link specs with clear dependencies
-lean-spec link feature-123 --depends-on auth-system
+leanspec link feature-123 --depends-on auth-system
 
 # See the full dependency graph
-lean-spec deps feature-123
+leanspec deps feature-123
 
 # Remove relationships
-lean-spec unlink feature-123 --from auth-system
+leanspec unlink feature-123 --from auth-system
 ```
 
 Better validation catches circular dependencies before they cause problems.
@@ -101,13 +101,13 @@ Every major command now supports `--json` for programmatic use:
 
 ```bash
 # Integrate with dashboards
-lean-spec board --json | jq '.columns[] | select(.status=="in-progress")'
+leanspec board --json | jq '.columns[] | select(.status=="in-progress")'
 
 # Build custom workflows
-lean-spec list --json --status=complete | jq -r '.[] | .name'
+leanspec list --json --status=complete | jq -r '.[] | .name'
 
 # Export for reporting
-lean-spec timeline --json > project-timeline.json
+leanspec timeline --json > project-timeline.json
 ```
 
 Use LeanSpec data in your CI/CD pipelines, project dashboards, or custom tooling.
@@ -149,7 +149,7 @@ Read [Why Your AI Agent Gets Dumber with Large Specs](/blog/ai-agent-performance
 ### 2. Spin Up an Example (2 minutes)
 
 ```bash
-npx lean-spec init --example dark-theme
+npx -p @leanspec/cli leanspec init --example dark-theme
 cd dark-theme
 npm install
 ```
@@ -171,8 +171,8 @@ Open the [Your First Spec with AI](/docs/tutorials/first-spec-with-ai) tutorial.
 
 ```bash
 cd your-existing-project
-npx lean-spec init
-lean-spec create user-authentication
+npx -p @leanspec/cli leanspec init
+leanspec create user-authentication
 ```
 
 Now apply what you learned. Start simple (status + created), add structure as needed (tags, priority, custom fields).
@@ -193,16 +193,16 @@ We're focused on making LeanSpec work seamlessly with more AI tools and developm
 - **Project management integrations** - Jira, Linear, and GitHub Projects sync
 - **More example projects** - Backend APIs, mobile apps, infrastructure
 
-**Feedback shapes the roadmap**. What would make LeanSpec more useful for your workflow? [Open an issue](https://github.com/codervisor/lean-spec/issues) or [join the discussion](https://github.com/codervisor/lean-spec/discussions).
+**Feedback shapes the roadmap**. What would make LeanSpec more useful for your workflow? [Open an issue](https://github.com/codervisor/leanspec/issues) or [join the discussion](https://github.com/codervisor/leanspec/discussions).
 
 ## Try It Today
 
 ```bash
 # Install globally
-npm install -g lean-spec
+npm install -g @leanspec/cli
 
 # Or use npx for one-off commands
-npx lean-spec init --example dark-theme
+npx -p @leanspec/cli leanspec init --example dark-theme
 ```
 
 The fastest way to learn is to build. Pick an example, follow a tutorial, see how AI-assisted spec-driven development changes your workflow.
@@ -211,9 +211,9 @@ The fastest way to learn is to build. Pick an example, follow a tutorial, see ho
 
 **Links**:
 - [Documentation](https://lean-spec.dev)
-- [GitHub Repository](https://github.com/codervisor/lean-spec)
+- [GitHub Repository](https://github.com/codervisor/leanspec)
 - [Example Projects](https://lean-spec.dev/docs/tutorials/first-spec-with-ai#quick-start)
 - [Getting Started Guide](https://lean-spec.dev/docs/guide/getting-started)
 - [Full Tutorial Collection](https://lean-spec.dev/docs/tutorials/first-spec-with-ai)
 
-**Changelog**: See [CHANGELOG.md](https://github.com/codervisor/lean-spec/blob/main/CHANGELOG.md) for detailed version history.
+**Changelog**: See [CHANGELOG.md](https://github.com/codervisor/leanspec/blob/main/CHANGELOG.md) for detailed version history.

docs/advanced/ai-assisted-spec-writing.mdx

@@ -145,7 +145,7 @@ Once refined, the spec becomes a **checkpoint** - a formalized agreement between
 **Mark as checkpoint:**
 - Save the spec file
 - Mark status as "planned" or "in-progress"
-- Use `lean-spec create` or update frontmatter
+- Use `leanspec create` or update frontmatter
 - Reference spec in commits and PRs
 
 **The spec now serves as:**
@@ -412,7 +412,7 @@ Specs should capture intent and constraints, not prescribe every implementation
 
 ### DON'T: Forget to Update Status
 
-Use `lean-spec update <spec> --status <status>` to track progress. AI can help draft, but you manage lifecycle.
+Use `leanspec update <spec> --status <status>` to track progress. AI can help draft, but you manage lifecycle.
 
 ## Common Pitfalls