spec-kitty-cli 2.1.3__tar.gz → 3.0.1__tar.gz

{spec_kitty_cli-2.1.3 → spec_kitty_cli-3.0.1}/.gitignore

@@ -54,9 +54,12 @@ env/
 .kittify/missions/
 .kittify/scripts/
 .kittify/runtime/
+.kittify/derived/
 .kittify/merge-state.json
 .kittify/events/
 .kittify/dossiers/
+.kittify/derived/
+.kittify/.migration-backup/
 kitty-specs/**/.kittify/dossiers/
 .kittify/constitution/context-state.json
 .kittify/constitution/directives.yaml
@@ -127,3 +130,5 @@ tmp/**
 pytest-of-*/
 .kittify/missions/__pycache__/
 .spec-kitty/
+.claude/
+.agent/

{spec_kitty_cli-2.1.3 → spec_kitty_cli-3.0.1}/CHANGELOG.md

@@ -11,6 +11,76 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 _No unreleased changes._
 
+## [3.0.1] - 2026-03-31
+
+### Fixed
+
+- **Canonical status hard cutover completed.** Work-package lane state is now consistently sourced from `status.events.jsonl` across active CLI commands, packaged task tooling, templates, docs, and standalone helpers. Frontmatter lane fallbacks and `lane=` body-log writes are removed from active 3.0 flows.
+- **Canonical bootstrap and hard-fail behavior hardened.** `finalize-tasks` now seeds canonical `planned` state for generated WPs, while runtime commands fail explicitly when canonical status is missing instead of silently reconstructing it from abandoned frontmatter state.
+- **Release automation updated for 3.x.** GitHub release validation, maintainer docs, and workflow tag handling now use semantic `vX.Y.Z` tags generically, so `v3.0.1` publishes correctly to GitHub Releases and PyPI.
+
+## [3.0.0] - 2026-03-30
+
+### Breaking Changes
+
+- **Event log is sole authority for mutable WP state.** Frontmatter `lane`, `review_status`, `reviewed_by`, and `progress` fields are no longer written or read at runtime. Status is read from `status.events.jsonl` via the reducer.
+- **`feature_detection.py` deleted.** All commands require explicit `--feature <slug>` in multi-feature repos. No branch scanning, no env var detection, no cwd walking.
+- **Sparse checkout removed.** `planning_artifact` WPs work in-repo; `code_change` WPs use standard worktrees without sparse checkout.
+- **Command templates restored as hybrid.** Planning commands (specify, plan, tasks, etc.) install as full prompts; execution commands (implement, review, merge, etc.) install as thin CLI-dispatch shims.
+
+### Added
+
+- **MissionContext** — opaque token-based bound identity for all workflow commands (`src/specify_cli/context/`)
+- **WP Ownership Manifest** — `execution_mode`, `owned_files`, `authoritative_surface` per WP (`src/specify_cli/ownership/`)
+- **Lane-weighted progress** — `planned=0.0`, `in_progress=0.3`, `for_review=0.6`, `done=1.0` (`src/specify_cli/status/progress.py`)
+- **`spec-kitty materialize`** command for CI/debugging regeneration of derived views
+- **Dedicated merge workspace** at `.kittify/runtime/merge/` with per-mission state and atomic lock
+- **Merge conflict auto-resolution** for event logs (append-merge) and metadata (take-theirs)
+- **Thin agent shims** for CLI-driven commands with `spec-kitty agent shim <command>` entrypoints
+- **Schema version gate** (disabled until 3.0.0 migration ships to consumers)
+- **One-shot migration framework** — `backfill_identity`, `backfill_ownership`, `rebuild_state`, `strip_frontmatter`
+- **`--validate-only`** flag on `finalize-tasks`
+- **`spec-kitty next`** hint in `tasks status` output
+- **Integration Verification** section in WP prompt template
+- **Doctor `command-files`** check — detects stale/missing/wrong-type agent command files
+- **Version markers** in generated command files (`<!-- spec-kitty-command-version: X.Y.Z -->`)
+- **Migration `m_2_1_4`** — unconditionally enforces correct hybrid command file state
+
+### Removed
+
+- `feature_detection.py` (668 lines) — replaced by MissionContext tokens
+- `status/legacy_bridge.py`, `status/phase.py`, `status/reconcile.py`, `status/migrate.py`
+- `merge/executor.py`, `merge/forecast.py`, `merge/status_resolver.py`
+- `core/agent_context.py` — tech-stack parsing no longer needed
+- ~56 command template files (replaced by 9 canonical prompts + 7 thin shims)
+- Sparse checkout policy enforcement
+- Frontmatter lane/review_status read/write throughout codebase
+- Dual-write (event log + frontmatter) behavior
+
+### Fixed
+
+- "planning repository" → "project root checkout" terminology (migration included)
+- Template path references removed from agent prompts (agents no longer search for `.kittify/missions/` files)
+- Workflow `implement`/`review` now emit status events (was silently failing)
+- Merge reconciliation marks ALL ancestor WPs as done (not just effective tips)
+- `require_explicit_feature()` lists available features in error message
+- YAML parse errors in frontmatter now logged as warnings (not silently swallowed)
+- Merge engine uses `git reset --hard` on detached HEAD (not `git checkout` which fails when branch is checked out elsewhere)
+- Migration backup covers `kitty-specs/` and `.gitignore` (not just `.kittify/`)
+- `rebuild_state.py` uses max timestamp (not last file line) for terminal state
+- Merge lock uses atomic `open('x')` (not TOCTOU `exists()` + `write_text()`)
+- `merge --resume` errors when multiple paused merges exist (not silently picks first)
+
+## [2.1.4] - 2026-03-27
+
+### Added
+
+**Enforce correct command file state**: Version markers and migration to guarantee all agent command files are always in the correct state.
+
+- `<!-- spec-kitty-command-version: X.Y.Z -->` marker added as the first line of every generated command file (both full prompts and thin shims)
+- Migration `m_2_1_4_enforce_command_file_state` unconditionally writes all 16 command files per configured agent; idempotent on subsequent runs when version markers match
+- `spec-kitty doctor command-files` subcommand checks all agent command files for missing files, stale version markers, and wrong file type (full prompt vs thin shim)
+
 ## [2.1.3] - 2026-03-27
 
 ### 🐛 Fixed

{spec_kitty_cli-2.1.3 → spec_kitty_cli-3.0.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: spec-kitty-cli
-Version: 2.1.3
+Version: 3.0.1
 Summary: Spec Kitty, a tool for Specification Driven Development (SDD) agentic projects, with kanban and git worktree isolation.
 Project-URL: Repository, https://github.com/Priivacy-ai/spec-kitty
 Project-URL: Issues, https://github.com/Priivacy-ai/spec-kitty/issues
@@ -185,18 +185,17 @@ graph LR
 
 </div>
 
-**Current stable release line:** `v2.1.1` (`main`, GitHub Releases, and PyPI)
+**Current stable release line:** `v3.0.1` (`main`, GitHub Releases, and PyPI)
 
-**2.1.1 highlights:**
-- Hotfix for PyPI wheels to bundle the canonical doctrine skill pack correctly
-- Upgrade repair migration for `2.1.0` projects that missed the managed skill pack
-- Release guardrails now fail if a wheel omits doctrine files or bundled skills
+**3.0.1 highlights:**
+- Canonical status hard cutover completed: active runtime paths no longer fall back to WP frontmatter lane state
+- `finalize-tasks` bootstraps canonical `planned` state for generated work packages
+- Release automation and maintainer tooling now accept semantic `vX.Y.Z` tags for 3.x publishing
 
-**2.1.0 highlights:**
-- Agent Skills Pack with bundled skills, installer/verification flow, and upgrade migration coverage
-- Structured requirement mapping from requirements into work-package planning
-- Deterministic branch intent injection in planning templates
-- `1.x` is now deprecated and retained only as `1.x-maintenance` for critical fixes
+**3.0.0 highlights:**
+- Event log is now the sole authority for mutable work-package status
+- Explicit feature targeting, MissionContext identity, and ownership manifests land on the 3.x stable line
+- Sparse checkout is removed in favor of in-repo planning artifacts and standard worktrees
 
 **Jump to:**
 [Getting Started](#-getting-started-complete-workflow) •
@@ -210,16 +209,16 @@ graph LR
 
 ## 📌 Release Track
 
-Spec Kitty now uses `main` as the stable `2.x` release line.
+Spec Kitty now uses `main` as the stable `3.x` release line.
 The former `1.x` line is deprecated and moves to `1.x-maintenance` for maintenance-only fixes.
 
 | Branch | Version | Status | Install |
 |--------|---------|--------|---------|
-| **main** | **2.1.x** | Current stable line | `pip install spec-kitty-cli` |
+| **main** | **3.0.x** | Current stable line | `pip install spec-kitty-cli` |
 | **1.x-maintenance** | **1.x** | Deprecated, maintenance-only | Install from a pinned maintenance tag or source checkout |
 
 **For users:** install the stable line from PyPI with `pip install spec-kitty-cli`.
-**For existing 1.x users:** migrate to `2.1.x` where possible; `1.x-maintenance` is only for critical maintenance and will no longer publish new PyPI releases.
+**For existing 1.x or 2.x users:** migrate to `3.0.x` where possible; `1.x-maintenance` is only for critical maintenance and will no longer publish new PyPI releases.
 
 ---
 
@@ -1237,10 +1236,10 @@ cat .kittify/metadata.yaml
 If you encounter issues with an agent, please open an issue so we can refine the integration.
 
 <details>
-<summary><h2>🚀 Releasing 2.x on GitHub and PyPI (Maintainers)</h2></summary>
+<summary><h2>🚀 Releasing Stable Versions on GitHub and PyPI (Maintainers)</h2></summary>
 
-The stable `2.x` line now lives on `main` and publishes from semantic tags in the form `v2.<minor>.<patch>`.
-Starting with `2.1.0`, the release workflow publishes both GitHub release artifacts and the PyPI package.
+The stable `3.x` line now lives on `main` and publishes from semantic tags in the form `vX.Y.Z`.
+The release workflow publishes both GitHub release artifacts and the PyPI package.
 
 ### 0. One-Time Setup
 
@@ -1261,7 +1260,7 @@ git checkout -b release/vX.Y.Z
 ### 2. Validate Locally
 
 ```bash
-python scripts/release/validate_release.py --mode branch --tag-pattern "v2.*.*"
+python scripts/release/validate_release.py --mode branch --tag-pattern "v*.*.*"
 python -m pytest
 python -m build
 twine check dist/*
@@ -1298,8 +1297,8 @@ python -m pip index versions spec-kitty-cli
 
 ### Guardrails
 
-- `release-readiness.yml`: runs on PRs to `main` (and `2.x` during the cutover window) to validate version/changelog/tests.
-- `release.yml`: runs on `v2.*.*` tags and performs:
+- `release-readiness.yml`: runs on PRs to `main` (and `2.x` if the maintenance branch is still active) to validate version/changelog/tests.
+- `release.yml`: runs on `v*.*.*` tags and performs:
   - test execution
   - release metadata validation
   - artifact build and checksums
@@ -1309,7 +1308,7 @@ python -m pip index versions spec-kitty-cli
 ### Troubleshooting
 
 **Validation fails**: "Version does not advance beyond latest tag"
-- Check latest tag: `git tag --list 'v2.*.*' --sort=-version:refname | head -1`
+- Check latest tag: `git tag --list 'v*.*.*' --sort=-version:refname | head -1`
 - Bump `pyproject.toml` to a higher semantic version
 
 **Validation fails**: "CHANGELOG.md lacks a populated section"

{spec_kitty_cli-2.1.3 → spec_kitty_cli-3.0.1}/README.md

@@ -96,18 +96,17 @@ graph LR
 
 </div>
 
-**Current stable release line:** `v2.1.1` (`main`, GitHub Releases, and PyPI)
+**Current stable release line:** `v3.0.1` (`main`, GitHub Releases, and PyPI)
 
-**2.1.1 highlights:**
-- Hotfix for PyPI wheels to bundle the canonical doctrine skill pack correctly
-- Upgrade repair migration for `2.1.0` projects that missed the managed skill pack
-- Release guardrails now fail if a wheel omits doctrine files or bundled skills
+**3.0.1 highlights:**
+- Canonical status hard cutover completed: active runtime paths no longer fall back to WP frontmatter lane state
+- `finalize-tasks` bootstraps canonical `planned` state for generated work packages
+- Release automation and maintainer tooling now accept semantic `vX.Y.Z` tags for 3.x publishing
 
-**2.1.0 highlights:**
-- Agent Skills Pack with bundled skills, installer/verification flow, and upgrade migration coverage
-- Structured requirement mapping from requirements into work-package planning
-- Deterministic branch intent injection in planning templates
-- `1.x` is now deprecated and retained only as `1.x-maintenance` for critical fixes
+**3.0.0 highlights:**
+- Event log is now the sole authority for mutable work-package status
+- Explicit feature targeting, MissionContext identity, and ownership manifests land on the 3.x stable line
+- Sparse checkout is removed in favor of in-repo planning artifacts and standard worktrees
 
 **Jump to:**
 [Getting Started](#-getting-started-complete-workflow) •
@@ -121,16 +120,16 @@ graph LR
 
 ## 📌 Release Track
 
-Spec Kitty now uses `main` as the stable `2.x` release line.
+Spec Kitty now uses `main` as the stable `3.x` release line.
 The former `1.x` line is deprecated and moves to `1.x-maintenance` for maintenance-only fixes.
 
 | Branch | Version | Status | Install |
 |--------|---------|--------|---------|
-| **main** | **2.1.x** | Current stable line | `pip install spec-kitty-cli` |
+| **main** | **3.0.x** | Current stable line | `pip install spec-kitty-cli` |
 | **1.x-maintenance** | **1.x** | Deprecated, maintenance-only | Install from a pinned maintenance tag or source checkout |
 
 **For users:** install the stable line from PyPI with `pip install spec-kitty-cli`.
-**For existing 1.x users:** migrate to `2.1.x` where possible; `1.x-maintenance` is only for critical maintenance and will no longer publish new PyPI releases.
+**For existing 1.x or 2.x users:** migrate to `3.0.x` where possible; `1.x-maintenance` is only for critical maintenance and will no longer publish new PyPI releases.
 
 ---
 
@@ -1148,10 +1147,10 @@ cat .kittify/metadata.yaml
 If you encounter issues with an agent, please open an issue so we can refine the integration.
 
 <details>
-<summary><h2>🚀 Releasing 2.x on GitHub and PyPI (Maintainers)</h2></summary>
+<summary><h2>🚀 Releasing Stable Versions on GitHub and PyPI (Maintainers)</h2></summary>
 
-The stable `2.x` line now lives on `main` and publishes from semantic tags in the form `v2.<minor>.<patch>`.
-Starting with `2.1.0`, the release workflow publishes both GitHub release artifacts and the PyPI package.
+The stable `3.x` line now lives on `main` and publishes from semantic tags in the form `vX.Y.Z`.
+The release workflow publishes both GitHub release artifacts and the PyPI package.
 
 ### 0. One-Time Setup
 
@@ -1172,7 +1171,7 @@ git checkout -b release/vX.Y.Z
 ### 2. Validate Locally
 
 ```bash
-python scripts/release/validate_release.py --mode branch --tag-pattern "v2.*.*"
+python scripts/release/validate_release.py --mode branch --tag-pattern "v*.*.*"
 python -m pytest
 python -m build
 twine check dist/*
@@ -1209,8 +1208,8 @@ python -m pip index versions spec-kitty-cli
 
 ### Guardrails
 
-- `release-readiness.yml`: runs on PRs to `main` (and `2.x` during the cutover window) to validate version/changelog/tests.
-- `release.yml`: runs on `v2.*.*` tags and performs:
+- `release-readiness.yml`: runs on PRs to `main` (and `2.x` if the maintenance branch is still active) to validate version/changelog/tests.
+- `release.yml`: runs on `v*.*.*` tags and performs:
   - test execution
   - release metadata validation
   - artifact build and checksums
@@ -1220,7 +1219,7 @@ python -m pip index versions spec-kitty-cli
 ### Troubleshooting
 
 **Validation fails**: "Version does not advance beyond latest tag"
-- Check latest tag: `git tag --list 'v2.*.*' --sort=-version:refname | head -1`
+- Check latest tag: `git tag --list 'v*.*.*' --sort=-version:refname | head -1`
 - Bump `pyproject.toml` to a higher semantic version
 
 **Validation fails**: "CHANGELOG.md lacks a populated section"

spec_kitty_cli-3.0.1/kitty-specs/057-canonical-context-architecture-cleanup/tasks/README.md

@@ -0,0 +1,75 @@
+# Tasks Directory
+
+This directory contains work package (WP) prompt files with lane status in frontmatter.
+
+## Directory Structure (v0.9.0+)
+
+```
+tasks/
+├── WP01-setup-infrastructure.md
+├── WP02-user-authentication.md
+├── WP03-api-endpoints.md
+└── README.md
+```
+
+All WP files are stored flat in `tasks/`. The lane (planned, doing, for_review, approved, done) is stored in the YAML frontmatter `lane:` field.
+
+## Work Package File Format
+
+Each WP file **MUST** use YAML frontmatter:
+
+```yaml
+---
+work_package_id: "WP01"
+title: "Work Package Title"
+lane: "planned"
+dependencies: []
+planning_base_branch: "2.x"
+merge_target_branch: "2.x"
+branch_strategy: "Planning artifacts were generated on 2.x; completed changes must merge back into 2.x."
+subtasks:
+  - "T001"
+  - "T002"
+phase: "Phase 1 - Setup"
+assignee: ""
+agent: ""
+shell_pid: ""
+review_status: ""
+reviewed_by: ""
+review_feedback: ""
+history:
+  - timestamp: "2025-01-01T00:00:00Z"
+    lane: "planned"
+    agent: "system"
+    action: "Prompt generated via /spec-kitty.tasks"
+---
+
+# Work Package Prompt: WP01 – Work Package Title
+
+[Content follows...]
+```
+
+## Valid Lane Values
+
+- `planned` - Ready for implementation
+- `doing` - Currently being worked on
+- `for_review` - Awaiting review
+- `approved` - Review passed; awaiting merge-complete recording
+- `done` - Completed
+
+## Moving Between Lanes
+
+Use the CLI (updates frontmatter only, no file movement):
+```bash
+spec-kitty agent tasks move-task <WPID> --to <lane>
+```
+
+Example:
+```bash
+spec-kitty agent tasks move-task WP01 --to doing
+```
+
+## File Naming
+
+- Format: `WP01-kebab-case-slug.md`
+- Examples: `WP01-setup-infrastructure.md`, `WP02-user-auth.md`

spec_kitty_cli-3.0.1/kitty-specs/058-hybrid-prompt-and-shim-agent-surface/tasks/README.md

@@ -0,0 +1,75 @@
+# Tasks Directory
+
+This directory contains work package (WP) prompt files with lane status in frontmatter.
+
+## Directory Structure (v0.9.0+)
+
+```
+tasks/
+├── WP01-setup-infrastructure.md
+├── WP02-user-authentication.md
+├── WP03-api-endpoints.md
+└── README.md
+```
+
+All WP files are stored flat in `tasks/`. The lane (planned, doing, for_review, approved, done) is stored in the YAML frontmatter `lane:` field.
+
+## Work Package File Format
+
+Each WP file **MUST** use YAML frontmatter:
+
+```yaml
+---
+work_package_id: "WP01"
+title: "Work Package Title"
+lane: "planned"
+dependencies: []
+planning_base_branch: "2.x"
+merge_target_branch: "2.x"
+branch_strategy: "Planning artifacts were generated on 2.x; completed changes must merge back into 2.x."
+subtasks:
+  - "T001"
+  - "T002"
+phase: "Phase 1 - Setup"
+assignee: ""
+agent: ""
+shell_pid: ""
+review_status: ""
+reviewed_by: ""
+review_feedback: ""
+history:
+  - timestamp: "2025-01-01T00:00:00Z"
+    lane: "planned"
+    agent: "system"
+    action: "Prompt generated via /spec-kitty.tasks"
+---
+
+# Work Package Prompt: WP01 – Work Package Title
+
+[Content follows...]
+```
+
+## Valid Lane Values
+
+- `planned` - Ready for implementation
+- `doing` - Currently being worked on
+- `for_review` - Awaiting review
+- `approved` - Review passed; awaiting merge-complete recording
+- `done` - Completed
+
+## Moving Between Lanes
+
+Use the CLI (updates frontmatter only, no file movement):
+```bash
+spec-kitty agent tasks move-task <WPID> --to <lane>
+```
+
+Example:
+```bash
+spec-kitty agent tasks move-task WP01 --to doing
+```
+
+## File Naming
+
+- Format: `WP01-kebab-case-slug.md`
+- Examples: `WP01-setup-infrastructure.md`, `WP02-user-auth.md`

spec_kitty_cli-3.0.1/kitty-specs/059-saas-mediated-cli-tracker-reflow/tasks/README.md

@@ -0,0 +1,75 @@
+# Tasks Directory
+
+This directory contains work package (WP) prompt files with lane status in frontmatter.
+
+## Directory Structure (v0.9.0+)
+
+```
+tasks/
+├── WP01-setup-infrastructure.md
+├── WP02-user-authentication.md
+├── WP03-api-endpoints.md
+└── README.md
+```
+
+All WP files are stored flat in `tasks/`. The lane (planned, doing, for_review, approved, done) is stored in the YAML frontmatter `lane:` field.
+
+## Work Package File Format
+
+Each WP file **MUST** use YAML frontmatter:
+
+```yaml
+---
+work_package_id: "WP01"
+title: "Work Package Title"
+lane: "planned"
+dependencies: []
+planning_base_branch: "2.x"
+merge_target_branch: "2.x"
+branch_strategy: "Planning artifacts were generated on 2.x; completed changes must merge back into 2.x."
+subtasks:
+  - "T001"
+  - "T002"
+phase: "Phase 1 - Setup"
+assignee: ""
+agent: ""
+shell_pid: ""
+review_status: ""
+reviewed_by: ""
+review_feedback: ""
+history:
+  - timestamp: "2025-01-01T00:00:00Z"
+    lane: "planned"
+    agent: "system"
+    action: "Prompt generated via /spec-kitty.tasks"
+---
+
+# Work Package Prompt: WP01 – Work Package Title
+
+[Content follows...]
+```
+
+## Valid Lane Values
+
+- `planned` - Ready for implementation
+- `doing` - Currently being worked on
+- `for_review` - Awaiting review
+- `approved` - Review passed; awaiting merge-complete recording
+- `done` - Completed
+
+## Moving Between Lanes
+
+Use the CLI (updates frontmatter only, no file movement):
+```bash
+spec-kitty agent tasks move-task <WPID> --to <lane>
+```
+
+Example:
+```bash
+spec-kitty agent tasks move-task WP01 --to doing
+```
+
+## File Naming
+
+- Format: `WP01-kebab-case-slug.md`
+- Examples: `WP01-setup-infrastructure.md`, `WP02-user-auth.md`

spec_kitty_cli-3.0.1/kitty-specs/060-canonical-status-model-cleanup/tasks/README.md

@@ -0,0 +1,65 @@
+# Tasks Directory
+
+This directory contains work package (WP) prompt files with static definitions in frontmatter.
+
+## Directory Structure
+
+```
+tasks/
+├── WP01-setup-infrastructure.md
+├── WP02-user-authentication.md
+├── WP03-api-endpoints.md
+└── README.md
+```
+
+All WP files are stored flat in `tasks/`.
+
+## Status Authority
+
+WP status (lane) is NOT stored in frontmatter. The sole authority for WP lane state is `status.events.jsonl` in the feature directory, materialized as `status.json` by the reducer.
+
+- To read WP status: `spec-kitty agent tasks status`
+- To move a WP: `spec-kitty agent tasks move-task <WPID> --to <lane>`
+
+Both commands operate on the canonical event log, not on WP files.
+
+## Work Package File Format
+
+Each WP file uses YAML frontmatter for **static definition only**:
+
+```yaml
+---
+work_package_id: "WP01"
+title: "Work Package Title"
+dependencies: []
+planning_base_branch: "main"
+merge_target_branch: "main"
+branch_strategy: "Branch from main."
+subtasks:
+  - "T001"
+  - "T002"
+execution_mode: "code_change"
+owned_files:
+  - "src/myapp/feature.py"
+authoritative_surface: "src/myapp/"
+requirement_refs:
+  - "FR-001"
+history:
+  - at: "2026-01-01T00:00:00Z"
+    actor: "planner"
+    action: "Prompt generated via /spec-kitty.tasks"
+---
+
+# Work Package Prompt: WP01 - Work Package Title
+
+[Content follows...]
+```
+
+Frontmatter does NOT include `lane`, `review_status`, `reviewed_by`, `review_feedback`, or `progress`. Those are managed by the canonical status model.
+
+Operational metadata (`agent`, `assignee`, `shell_pid`) may be present for runtime coordination.
+
+## File Naming
+
+- Format: `WP01-kebab-case-slug.md`
+- Examples: `WP01-setup-infrastructure.md`, `WP02-user-auth.md`

{spec_kitty_cli-2.1.3 → spec_kitty_cli-3.0.1}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "spec-kitty-cli"
-version = "2.1.3"
+version = "3.0.1"
 description = "Spec Kitty, a tool for Specification Driven Development (SDD) agentic projects, with kanban and git worktree isolation."
 readme = "README.md"
 license = { file = "LICENSE" }