refactor: rename configuration directory from .lspec to .lean-spec

- Updated all references in documentation and code to reflect the new configuration directory name.
- Changed paths for configuration files and templates from `.lspec/config.json` and `.lspec/templates/` to `.lean-spec/config.json` and `.lean-spec/templates/`.
- Ensured backward compatibility by updating initialization and template handling processes.

Author: Marvin Zhang

.npmignore

@@ -5,7 +5,7 @@ src/
 # Development files
 coverage/
 specs/
-.lspec/
+.lean-spec/
 examples/
 docs/
 

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

@@ -66,7 +66,7 @@ Zero configuration using standard template. Gets you up and running in seconds.
 ```
 
 This creates:
-- `.lspec/config.json` with minimal configuration
+- `.lean-spec/config.json` with minimal configuration
 - `specs/` directory for your specs
 - `AGENTS.md` with AI agent integration guidance (if not present)
 
@@ -94,7 +94,7 @@ After initialization, your project will have:
 
 ```
 your-project/
-├── .lspec/
+├── .lean-spec/
 │   ├── config.json         # LeanSpec configuration
 │   └── templates/          # Custom spec templates (optional)
 │       └── spec-template.md
@@ -106,21 +106,21 @@ your-project/
 └── ... (your project files)
 ```
 
-**Note**: Default structure is flat with global numbering (`001-name/`, `002-name/`). For date-based grouping, configure the `structure.pattern` in `.lspec/config.json`.
+**Note**: Default structure is flat with global numbering (`001-name/`, `002-name/`). For date-based grouping, configure the `structure.pattern` in `.lean-spec/config.json`.
 
 ## Integrating with Existing Projects
 
 If you already have `AGENTS.md`, `.cursorrules`, or other system prompts, `lean-spec init` will detect them and offer three options:
 
 1. **Merge** - Appends LeanSpec guidance to your existing `AGENTS.md` (preserves your content)
 2. **Backup** - Saves existing files as `.backup` and creates fresh ones
-3. **Skip** - Only adds `.lspec` config and `specs/` directory, keeps your files untouched
+3. **Skip** - Only adds `.lean-spec` config and `specs/` directory, keeps your files untouched
 
 This makes it easy to adopt LeanSpec incrementally without disrupting your existing AI agent setup.
 
-## Configuration File
+## Configuration
 
-The `.lspec/config.json` file controls LeanSpec behavior:
+The `.lean-spec/config.json` file controls LeanSpec behavior:
 
 ```json
 {

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

@@ -13,7 +13,7 @@ Add project-specific metadata to your specs.
 
 ### Defining Custom Fields
 
-Edit `.lspec/config.json`:
+Edit `.lean-spec/config.json`:
 
 ```json
 {
@@ -118,7 +118,7 @@ Available automatically:
 
 ### Custom Variables
 
-Define in `.lspec/config.json`:
+Define in `.lean-spec/config.json`:
 
 ```json
 {
@@ -133,7 +133,7 @@ Define in `.lspec/config.json`:
 
 ### Using Variables in Templates
 
-Create or edit `.lspec/templates/spec-template.md`:
+Create or edit `.lean-spec/templates/spec-template.md`:
 
 ```markdown
 ---

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

@@ -105,7 +105,7 @@ This is automatically added when you set `status: complete`.
 
 ## Custom Fields
 
-You can define custom fields in `.lspec/config.json`:
+You can define custom fields in `.lean-spec/config.json`:
 
 ```json
 {

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

@@ -132,14 +132,14 @@ lean-spec init
 
 ## Custom Templates
 
-You can create your own templates in `.lspec/templates/`.
+You can create your own templates in `.lean-spec/templates/`.
 
 ### Creating a Custom Template
 
 1. Create template file:
 ```bash
-mkdir -p .lspec/templates
-touch .lspec/templates/my-template.md
+mkdir -p .lean-spec/templates
+touch .lean-spec/templates/my-template.md
 ```
 
 2. Edit template with placeholders:
@@ -159,7 +159,7 @@ created: {date}
 [Your custom sections...]
 ```
 
-3. Configure in `.lspec/config.json`:
+3. Configure in `.lean-spec/config.json`:
 ```json
 {
   "template": "my-template.md"
@@ -221,7 +221,7 @@ Customize sections to fit your needs.
 
 To change templates mid-project:
 
-1. Update `.lspec/config.json`:
+1. Update `.lean-spec/config.json`:
 ```json
 {
   "template": "new-template.md"
@@ -247,7 +247,7 @@ Not every spec needs every section. Use what adds value, skip what doesn't.
 :::
 
 :::tip Share Templates
-Export your `.lspec/templates/` directory to share with other teams or projects.
+Export your `.lean-spec/templates/` directory to share with other teams or projects.
 :::
 
 ---

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

@@ -97,7 +97,7 @@ Repository name from git remote URL.
 
 ## Custom Variables
 
-Define your own variables in `.lspec/config.json`:
+Define your own variables in `.lean-spec/config.json`:
 
 ```json
 {
@@ -120,7 +120,7 @@ Use in templates:
 
 ### 1. Create or Edit Template
 
-`.lspec/templates/spec-template.md`:
+`.lean-spec/templates/spec-template.md`:
 
 ```markdown
 ---
@@ -145,7 +145,7 @@ Questions? Reach out to \{default_reviewer\} or \{git_email\}
 
 ### 2. Configure Variables
 
-`.lspec/config.json`:
+`.lean-spec/config.json`:
 
 ```json
 {
@@ -276,7 +276,7 @@ Add comments in config explaining what each variable is for.
 2. Typo in variable name
 3. Config file not saved
 
-**Solution:** Check `.lspec/config.json` has the variable defined.
+**Solution:** Check `.lean-spec/config.json` has the variable defined.
 
 ### Wrong Value
 

docs-site/docs/reference/cli.mdx

@@ -30,8 +30,8 @@ lean-spec init
 3. Configure initial settings
 
 **What it creates:**
-- `.lspec/config.json` - Configuration file
-- `.lspec/templates/` - Custom templates directory
+- `.lean-spec/config.json` - Configuration file
+- `.lean-spec/templates/` - Custom templates directory
 - `specs/` - Specs directory
 - `AGENTS.md` - AI agent integration guidance (if not present)
 
@@ -86,7 +86,7 @@ lean-spec create user-auth --field epic=PROJ-123 --field sprint=42
 - Assigns sequential number (NNN) globally across all specs
 - Sets frontmatter with metadata
 
-**Note**: Default is flat structure. For date-based grouping, configure `pattern: "custom"` in `.lspec/config.json`.
+**Note**: Default is flat structure. For date-based grouping, configure `pattern: "custom"` in `.lean-spec/config.json`.
 
 ---
 
@@ -551,7 +551,7 @@ LeanSpec will find the spec regardless of which format you use.
 
 ## Configuration
 
-Commands respect settings in `.lspec/config.json`:
+Commands respect settings in `.lean-spec/config.json`:
 
 ```json
 {

docs-site/docs/reference/config.mdx

@@ -5,11 +5,11 @@ sidebar_position: 2
 ---
 # Configuration
 
-Complete reference for `.lspec/config.json`.
+Complete reference for `.lean-spec/config.json`.
 
 ## Configuration File
 
-LeanSpec configuration is stored in `.lspec/config.json` in your project root.
+LeanSpec configuration is stored in `.lean-spec/config.json` in your project root.
 
 ## Default Configuration
 
@@ -43,7 +43,7 @@ Primary template file to use for new specs.
 **Type:** `string`  
 **Default:** `"spec-template.md"`
 
-Path to the template file within `.lspec/templates/` directory.
+Path to the template file within `.lean-spec/templates/` directory.
 
 ```json
 {
@@ -421,7 +421,7 @@ LeanSpec validates configuration on load:
 
 - Required structure fields must be valid
 - Custom field types must be valid (`string`, `number`, `boolean`, `array`)
-- Template files must exist in `.lspec/templates/`
+- Template files must exist in `.lean-spec/templates/`
 - Spec directory is created if missing
 
 Invalid configuration will show an error with details.
@@ -430,7 +430,7 @@ Invalid configuration will show an error with details.
 
 When updating configuration:
 
-1. Edit `.lspec/config.json`
+1. Edit `.lean-spec/config.json`
 2. New specs will use new configuration
 3. Existing specs are not automatically updated
 4. Manually update existing specs if needed

docs-site/docs/reference/frontmatter.mdx

@@ -97,7 +97,7 @@ Auto-added when status is set to `complete`.
 
 ## Custom Fields
 
-Define in `.lspec/config.json`:
+Define in `.lean-spec/config.json`:
 
 ```json
 {

docs-site/docs/reference/mcp-server.mdx

@@ -246,7 +246,7 @@ Show me what would be backfilled without making changes
 
 ### Server won't start
 
-- Verify the `cwd` path in your configuration points to a valid LeanSpec project (has `.lspec/config.json`)
+- Verify the `cwd` path in your configuration points to a valid LeanSpec project (has `.lean-spec/config.json`)
 - If using `npx`, ensure you have internet access for the first run
 - If using global installation, check that `lean-spec` is in your PATH
 - Try running `npx -y lean-spec mcp` or `lean-spec mcp` directly from your project directory