feat(#291): mapify preset remove/enable/disable/resolve commands (Slice 2)

[azalio]

Summary

Second slice of SpecKit-style preset composition (#291). Builds on Slice 1 (PR #370) which added mapify preset list and mapify preset add.

New commands:

• mapify preset remove <id> — uninstalls a preset from .map/presets/; confirmation prompt unless --yes
• mapify preset enable <id> — marks a preset active via .map/presets/<id>/.state.json sidecar
• mapify preset disable <id> — marks a preset inactive without uninstalling it
• mapify preset resolve <template> — shows the 3-tier resolution stack for a template (project overrides → enabled presets → core templates) including strategy, enabled status, and file path per layer; --json for machine-readable output

Implementation notes

• Enabled/disabled state persists to .map/presets/<id>/.state.json (JSON sidecar, not manifest.json — presets are read-only once installed)
• resolve shows disabled presets with enabled: false so operators see the full resolution picture
• Project overrides live at .map/overrides/<template> (tier 1, highest priority)
• Preset templates live at .map/presets/<id>/templates/<template> (tier 2)
• Core templates from get_templates_dir() (tier 3, lowest priority)

Tests

16 new tests (PC9–PC11) added to tests/test_preset_commands.py. 45 total tests in the file.

Full suite: 3931 passed, 4 skipped, 0 failures.

Part of #291 (composition/rendering engine — prepend/append/wrap strategies applied at render time — follows in Slice 3).

---

Generated by Claude Code

[coderabbitai]

Warning

Review limit reached

@azalio, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 18 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: ddba1cfd-25b7-4b8f-8701-7f9012e9e2d1

📥 Commits

Reviewing files that changed from the base of the PR and between f05ba1d and cfc1eda.

📒 Files selected for processing (3)

• docs/ARCHITECTURE.md
• src/mapify_cli/__init__.py
• tests/test_preset_commands.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/compassionate-cerf-eynfn6

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}