mapify-cli 3.5.0__tar.gz → 3.7.0__tar.gz

{mapify_cli-3.5.0 → mapify_cli-3.7.0}/.gitignore

@@ -42,11 +42,13 @@ coverage.json
 .claude/sessions/
 .claude/metrics/
 .claude/cache/
+.claude/worktrees/
 
 # MAP runtime files (but keep static-analysis and orchestrator scripts)
 .map/*
 !.map/static-analysis/
 !.map/scripts/
+.map/scripts/.map/
 
 # Temporary verification files
 mapify_cli_verification_*.json

{mapify_cli-3.5.0 → mapify_cli-3.7.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mapify-cli
-Version: 3.5.0
+Version: 3.7.0
 Summary: MAP Framework installer - Modular Agentic Planner for Claude Code
 Project-URL: Homepage, https://github.com/azalio/map-framework
 Project-URL: Repository, https://github.com/azalio/map-framework.git
@@ -41,10 +41,11 @@ Based on [MAP cognitive architecture](https://github.com/Shanka123/MAP) (Nature
 
 ## Why MAP?
 
-- **Structured workflows** — 12 specialized agents instead of single-prompt chaos
+- **Structured workflows** — 11 specialized agents instead of single-prompt chaos
 - **Quality gates** — automatic validation catches errors before they compound
 - **40-60% cost savings** — prevents circular reasoning and scope creep
 - **Learning system** — captures patterns for reuse across projects
+- **Persistent artifacts** — `/map-plan`, `/map-efficient`, and `/map-check` keep branch-scoped research, session, review, QA, and verification artifacts inside `.map/<branch>/`
 
 ## Quick Start
 
@@ -79,16 +80,25 @@ claude
 | `/map-efficient` | Production features, refactoring, complex tasks (recommended) |
 | `/map-debug` | Bug fixes and debugging |
 | `/map-fast` | Small, low-risk changes |
-| `/map-debate` | Complex decisions with multi-variant synthesis |
 | `/map-review` | Pre-commit code review |
 | `/map-check` | Quality gates and verification |
 | `/map-plan` | Task decomposition without implementation |
+| `/map-task` | Execute a single subtask from an existing plan |
+| `/map-tdd` | Test-first implementation workflow |
 | `/map-release` | Package release workflow |
 | `/map-resume` | Resume interrupted workflows |
 | `/map-learn` | Extract lessons after workflow completion |
 
 [Detailed usage and options →](docs/USAGE.md)
 
+Canonical MAP flows:
+
+- Standard: `/map-plan` -> `/map-efficient` -> `/map-check` -> `/map-review`
+- Full TDD: `/map-plan` -> `/map-tdd` -> `/map-check` -> `/map-review`
+- Targeted subtask TDD: `/map-plan` -> `/map-tdd ST-001` -> `/map-task ST-001` -> ... -> `/map-check` -> `/map-review`
+
+These workflows maintain branch-scoped artifacts like `code-review-001.md`, `qa-001.md`, `verification-summary.md`, `pr-draft.md`, and run dossiers under `.map/<branch>/`.
+
 ## How It Works
 
 MAP orchestrates specialized agents through slash commands:
@@ -114,11 +124,16 @@ The orchestration lives in `.claude/commands/map-*.md` prompts created by `mapif
 | [Installation](docs/INSTALL.md) | All install methods, PATH setup, troubleshooting |
 | [Usage Guide](docs/USAGE.md) | Workflows, examples, cost optimization, playbook |
 | [Architecture](docs/ARCHITECTURE.md) | Agents, MCP integration, customization |
+| [Platform Spec](docs/MAP_PLATFORM_SPEC.md) | Platform refactor roadmap, codebase analysis |
+
+## Case Study
+
+- [DevOpsConf 2026 case study](https://github.com/azalio/devopsconf-ai-develop) — real production case: SPEC -> PLAN -> TEST -> CODE -> REVIEW -> LEARN
 
 ## Trouble?
 
 - **Command not found** → Run `mapify init` in your project first
-- **Agent errors** → Check `.claude/agents/` has all 12 `.md` files
+- **Agent errors** → Check `.claude/agents/` has all 11 shipped agent `.md` files
 - [More help →](docs/INSTALL.md#troubleshooting)
 
 ## Contributing

{mapify_cli-3.5.0 → mapify_cli-3.7.0}/README.md

@@ -9,10 +9,11 @@ Based on [MAP cognitive architecture](https://github.com/Shanka123/MAP) (Nature
 
 ## Why MAP?
 
-- **Structured workflows** — 12 specialized agents instead of single-prompt chaos
+- **Structured workflows** — 11 specialized agents instead of single-prompt chaos
 - **Quality gates** — automatic validation catches errors before they compound
 - **40-60% cost savings** — prevents circular reasoning and scope creep
 - **Learning system** — captures patterns for reuse across projects
+- **Persistent artifacts** — `/map-plan`, `/map-efficient`, and `/map-check` keep branch-scoped research, session, review, QA, and verification artifacts inside `.map/<branch>/`
 
 ## Quick Start
 
@@ -47,16 +48,25 @@ claude
 | `/map-efficient` | Production features, refactoring, complex tasks (recommended) |
 | `/map-debug` | Bug fixes and debugging |
 | `/map-fast` | Small, low-risk changes |
-| `/map-debate` | Complex decisions with multi-variant synthesis |
 | `/map-review` | Pre-commit code review |
 | `/map-check` | Quality gates and verification |
 | `/map-plan` | Task decomposition without implementation |
+| `/map-task` | Execute a single subtask from an existing plan |
+| `/map-tdd` | Test-first implementation workflow |
 | `/map-release` | Package release workflow |
 | `/map-resume` | Resume interrupted workflows |
 | `/map-learn` | Extract lessons after workflow completion |
 
 [Detailed usage and options →](docs/USAGE.md)
 
+Canonical MAP flows:
+
+- Standard: `/map-plan` -> `/map-efficient` -> `/map-check` -> `/map-review`
+- Full TDD: `/map-plan` -> `/map-tdd` -> `/map-check` -> `/map-review`
+- Targeted subtask TDD: `/map-plan` -> `/map-tdd ST-001` -> `/map-task ST-001` -> ... -> `/map-check` -> `/map-review`
+
+These workflows maintain branch-scoped artifacts like `code-review-001.md`, `qa-001.md`, `verification-summary.md`, `pr-draft.md`, and run dossiers under `.map/<branch>/`.
+
 ## How It Works
 
 MAP orchestrates specialized agents through slash commands:
@@ -82,11 +92,16 @@ The orchestration lives in `.claude/commands/map-*.md` prompts created by `mapif
 | [Installation](docs/INSTALL.md) | All install methods, PATH setup, troubleshooting |
 | [Usage Guide](docs/USAGE.md) | Workflows, examples, cost optimization, playbook |
 | [Architecture](docs/ARCHITECTURE.md) | Agents, MCP integration, customization |
+| [Platform Spec](docs/MAP_PLATFORM_SPEC.md) | Platform refactor roadmap, codebase analysis |
+
+## Case Study
+
+- [DevOpsConf 2026 case study](https://github.com/azalio/devopsconf-ai-develop) — real production case: SPEC -> PLAN -> TEST -> CODE -> REVIEW -> LEARN
 
 ## Trouble?
 
 - **Command not found** → Run `mapify init` in your project first
-- **Agent errors** → Check `.claude/agents/` has all 12 `.md` files
+- **Agent errors** → Check `.claude/agents/` has all 11 shipped agent `.md` files
 - [More help →](docs/INSTALL.md#troubleshooting)
 
 ## Contributing

{mapify_cli-3.5.0 → mapify_cli-3.7.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "mapify-cli"
-version = "3.5.0"
+version = "3.7.0"
 description = "MAP Framework installer - Modular Agentic Planner for Claude Code"
 authors = [{ name = "MAP Framework Contributors" }]
 readme = "README.md"
@@ -49,6 +49,16 @@ include = [
 [tool.hatch.build.targets.wheel]
 packages = ["src/mapify_cli"]
 
+[tool.mypy]
+ignore_missing_imports = false
+exclude = [
+    "src/mapify_cli/templates/map/scripts/",
+]
+
+[[tool.mypy.overrides]]
+module = "yaml"
+ignore_missing_imports = true
+
 [project.urls]
 Homepage = "https://github.com/azalio/map-framework"
 Repository = "https://github.com/azalio/map-framework.git"