mapify-cli 3.26.0__tar.gz → 3.27.0__tar.gz

{mapify_cli-3.26.0 → mapify_cli-3.27.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: mapify-cli
-Version: 3.26.0
+Version: 3.27.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
@@ -129,6 +129,26 @@ That's the whole golden path.
 
 > Codex CLI users invoke the same skills with `$`: `$map-plan`, `$map-efficient`, `$map-check`. See the [Usage Guide](docs/USAGE.md#codex-cli-provider).
 
+**Framework updates.** Automatic stable updates are enabled by default. Normal
+MAP skills check at most once per project every 24 hours, apply eligible patch
+and minor releases, and ask before a major release after showing its official
+feature highlights. Rejecting a major offer is remembered per project for that
+exact version, so it is not offered again; any different patch, minor, or major
+version is offered normally. Use these project controls and provider-specific
+manual skills when needed:
+
+```text
+mapify init . --no-auto-update   # persist updates.auto: false
+mapify init . --auto-update      # re-enable automatic checks
+/map-upgrade                     # Claude manual check/upgrade
+$map-upgrade                     # Codex manual check/upgrade
+```
+
+Automatic failures stay silent so they do not block the requested workflow;
+manual checks report errors explicitly. The public `mapify upgrade` command is
+separate and unchanged: it upgrades only the CLI and does not refresh project
+files. See [Automatic and manual framework updates](docs/USAGE.md#automatic-and-manual-framework-updates).
+
 ## Case Study: 90 days → 7 days
 
 The DevOpsConf 2026 case study applies this process to a production Kubernetes Project Operator:

{mapify_cli-3.26.0 → mapify_cli-3.27.0}/README.md

@@ -84,6 +84,26 @@ That's the whole golden path.
 
 > Codex CLI users invoke the same skills with `$`: `$map-plan`, `$map-efficient`, `$map-check`. See the [Usage Guide](docs/USAGE.md#codex-cli-provider).
 
+**Framework updates.** Automatic stable updates are enabled by default. Normal
+MAP skills check at most once per project every 24 hours, apply eligible patch
+and minor releases, and ask before a major release after showing its official
+feature highlights. Rejecting a major offer is remembered per project for that
+exact version, so it is not offered again; any different patch, minor, or major
+version is offered normally. Use these project controls and provider-specific
+manual skills when needed:
+
+```text
+mapify init . --no-auto-update   # persist updates.auto: false
+mapify init . --auto-update      # re-enable automatic checks
+/map-upgrade                     # Claude manual check/upgrade
+$map-upgrade                     # Codex manual check/upgrade
+```
+
+Automatic failures stay silent so they do not block the requested workflow;
+manual checks report errors explicitly. The public `mapify upgrade` command is
+separate and unchanged: it upgrades only the CLI and does not refresh project
+files. See [Automatic and manual framework updates](docs/USAGE.md#automatic-and-manual-framework-updates).
+
 ## Case Study: 90 days → 7 days
 
 The DevOpsConf 2026 case study applies this process to a production Kubernetes Project Operator:

{mapify_cli-3.26.0 → mapify_cli-3.27.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "mapify-cli"
-version = "3.26.0"
+version = "3.27.0"
 description = "MAP Framework installer - Modular Agentic Planner for Claude Code"
 authors = [{ name = "MAP Framework Contributors" }]
 readme = "README.md"
@@ -132,6 +132,12 @@ ignore = [
     "TRY004",
 ]
 
+[tool.ruff.lint.per-file-ignores]
+# Test modules intentionally adjust sys.path before importing generated scripts.
+"tests/**/*.py" = ["E402"]
+# These standalone generated scripts resolve sibling map_utils imports at runtime.
+"src/mapify_cli/templates/map/scripts/*.py" = ["E402"]
+
 [tool.ruff.lint.flake8-bugbear]
 # typer's CLI parameter declarations require typer.Option(...)/typer.Argument(...)
 # as argument defaults -- that's the framework's own idiomatic API, not the