mapify-cli 3.31.4__tar.gz → 3.32.0__tar.gz

{mapify_cli-3.31.4 → mapify_cli-3.32.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: mapify-cli
-Version: 3.31.4
+Version: 3.32.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
@@ -134,7 +134,7 @@ That's the whole golden path.
 - **Starting from a PRD?** Run `/map-prd-review` directly, or accept `/map-plan`'s optional readiness preflight. A non-ready result shows the gaps and asks whether to revise or continue planning anyway.
 - **Already scoped?** Go straight to `/map-efficient`.
 - **Tiny edit?** `/map-plan` off-ramps you to a direct edit or `/map-fast` instead of forcing full planning.
-- **Too foggy to plan?** `/map-wayfind` resolves open design decisions one at a time on a durable map, then hands settled decisions to `/map-plan`.
+- **Too foggy to plan?** `/map-wayfind` resolves open design decisions on a durable map. Evidence-first research is on by default: factual lookups stay light; uncertain decisions get independent investigations and targeted checks, with four attempts before asking to extend the budget. Research handoffs are checked before `/map-plan`; historical decisions retain explicit legacy provenance.
 - **Want one entry point?** `/map-auto` routes and drives the chain autonomously; hard-stops only on `dangerous_action`/`safety_guardrail` holds.
 
 > Codex CLI ships the same 23 MAP skill entry points and invokes them with `$`:
@@ -201,7 +201,7 @@ The DevOpsConf 2026 case study applies this process to a production Kubernetes P
 | `/map-debug` | Bug fixes and debugging |
 | `/map-task` | Execute a single subtask from an existing plan |
 | `/map-tdd` | Test-first implementation workflow |
-| `/map-release` | Package release workflow |
+| `/map-release` | Package release workflow; Codex `$map-release` shares the same commit-bound CI gates |
 | `/map-resume` | Resume interrupted workflows |
 
 [Detailed usage and options →](docs/USAGE.md)

{mapify_cli-3.31.4 → mapify_cli-3.32.0}/README.md

@@ -89,7 +89,7 @@ That's the whole golden path.
 - **Starting from a PRD?** Run `/map-prd-review` directly, or accept `/map-plan`'s optional readiness preflight. A non-ready result shows the gaps and asks whether to revise or continue planning anyway.
 - **Already scoped?** Go straight to `/map-efficient`.
 - **Tiny edit?** `/map-plan` off-ramps you to a direct edit or `/map-fast` instead of forcing full planning.
-- **Too foggy to plan?** `/map-wayfind` resolves open design decisions one at a time on a durable map, then hands settled decisions to `/map-plan`.
+- **Too foggy to plan?** `/map-wayfind` resolves open design decisions on a durable map. Evidence-first research is on by default: factual lookups stay light; uncertain decisions get independent investigations and targeted checks, with four attempts before asking to extend the budget. Research handoffs are checked before `/map-plan`; historical decisions retain explicit legacy provenance.
 - **Want one entry point?** `/map-auto` routes and drives the chain autonomously; hard-stops only on `dangerous_action`/`safety_guardrail` holds.
 
 > Codex CLI ships the same 23 MAP skill entry points and invokes them with `$`:
@@ -156,7 +156,7 @@ The DevOpsConf 2026 case study applies this process to a production Kubernetes P
 | `/map-debug` | Bug fixes and debugging |
 | `/map-task` | Execute a single subtask from an existing plan |
 | `/map-tdd` | Test-first implementation workflow |
-| `/map-release` | Package release workflow |
+| `/map-release` | Package release workflow; Codex `$map-release` shares the same commit-bound CI gates |
 | `/map-resume` | Resume interrupted workflows |
 
 [Detailed usage and options →](docs/USAGE.md)

{mapify_cli-3.31.4 → mapify_cli-3.32.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "mapify-cli"
-version = "3.31.4"
+version = "3.32.0"
 description = "MAP Framework installer - Modular Agentic Planner for Claude Code"
 authors = [{ name = "MAP Framework Contributors" }]
 readme = "README.md"

{mapify_cli-3.31.4 → mapify_cli-3.32.0}/src/mapify_cli/__init__.py

@@ -23,7 +23,7 @@ Or install globally:
     mapify check
 """
 
-__version__ = "3.31.4"
+__version__ = "3.32.0"
 
 # MUST stay the first import: it turns "this interpreter is older than 3.11" into
 # a message that says so, instead of the ImportError raised by `from datetime

{mapify_cli-3.31.4 → mapify_cli-3.32.0}/src/mapify_cli/templates/codex/hooks/context-meter.py

@@ -36,13 +36,13 @@ import sys
 # evaluated annotations) fails with a message that never mentions the version.
 # Name the real cause instead. Kept in sync with
 # mapify_cli/python_runtime.MINIMUM_PYTHON.
-# UP036 is suppressed on purpose: the project targets 3.11, but the interpreter
-# executing this shipped file is the user's `python3`, not the project's.
+# Compare the runtime tuple: the executing interpreter is the user's `python3`,
+# not necessarily the Python version targeted by the project's static checker.
 #
 # FAIL-OPEN mode. Exit 1 is a non-blocking hook error for Claude Code (only
 # exit 2, or a JSON deny, blocks a tool call), so the reason reaches the user
 # and the session continues -- a broken interpreter is not a policy decision.
-if sys.version_info < (3, 11):  # noqa: UP036
+if tuple(sys.version_info) < (3, 11):
     _MAP_PYTHON_PROBLEM = (
         f"MAP requires Python 3.11 or newer, but {sys.executable} is "
         f"Python {sys.version_info[0]}.{sys.version_info[1]}.\n"

{mapify_cli-3.31.4 → mapify_cli-3.32.0}/src/mapify_cli/templates/codex/hooks/detect-clarification-triggers.py

@@ -37,13 +37,13 @@ import sys
 # evaluated annotations) fails with a message that never mentions the version.
 # Name the real cause instead. Kept in sync with
 # mapify_cli/python_runtime.MINIMUM_PYTHON.
-# UP036 is suppressed on purpose: the project targets 3.11, but the interpreter
-# executing this shipped file is the user's `python3`, not the project's.
+# Compare the runtime tuple: the executing interpreter is the user's `python3`,
+# not necessarily the Python version targeted by the project's static checker.
 #
 # FAIL-OPEN mode. Exit 1 is a non-blocking hook error for Claude Code (only
 # exit 2, or a JSON deny, blocks a tool call), so the reason reaches the user
 # and the session continues -- a broken interpreter is not a policy decision.
-if sys.version_info < (3, 11):  # noqa: UP036
+if tuple(sys.version_info) < (3, 11):
     _MAP_PYTHON_PROBLEM = (
         f"MAP requires Python 3.11 or newer, but {sys.executable} is "
         f"Python {sys.version_info[0]}.{sys.version_info[1]}.\n"

{mapify_cli-3.31.4 → mapify_cli-3.32.0}/src/mapify_cli/templates/codex/hooks/map-memory-capture.py

@@ -10,13 +10,13 @@ import sys
 # evaluated annotations) fails with a message that never mentions the version.
 # Name the real cause instead. Kept in sync with
 # mapify_cli/python_runtime.MINIMUM_PYTHON.
-# UP036 is suppressed on purpose: the project targets 3.11, but the interpreter
-# executing this shipped file is the user's `python3`, not the project's.
+# Compare the runtime tuple: the executing interpreter is the user's `python3`,
+# not necessarily the Python version targeted by the project's static checker.
 #
 # FAIL-OPEN mode. Exit 1 is a non-blocking hook error for Claude Code (only
 # exit 2, or a JSON deny, blocks a tool call), so the reason reaches the user
 # and the session continues -- a broken interpreter is not a policy decision.
-if sys.version_info < (3, 11):  # noqa: UP036
+if tuple(sys.version_info) < (3, 11):
     _MAP_PYTHON_PROBLEM = (
         f"MAP requires Python 3.11 or newer, but {sys.executable} is "
         f"Python {sys.version_info[0]}.{sys.version_info[1]}.\n"

{mapify_cli-3.31.4 → mapify_cli-3.32.0}/src/mapify_cli/templates/codex/hooks/map-memory-endmark.py

@@ -10,13 +10,13 @@ import sys
 # evaluated annotations) fails with a message that never mentions the version.
 # Name the real cause instead. Kept in sync with
 # mapify_cli/python_runtime.MINIMUM_PYTHON.
-# UP036 is suppressed on purpose: the project targets 3.11, but the interpreter
-# executing this shipped file is the user's `python3`, not the project's.
+# Compare the runtime tuple: the executing interpreter is the user's `python3`,
+# not necessarily the Python version targeted by the project's static checker.
 #
 # FAIL-OPEN mode. Exit 1 is a non-blocking hook error for Claude Code (only
 # exit 2, or a JSON deny, blocks a tool call), so the reason reaches the user
 # and the session continues -- a broken interpreter is not a policy decision.
-if sys.version_info < (3, 11):  # noqa: UP036
+if tuple(sys.version_info) < (3, 11):
     _MAP_PYTHON_PROBLEM = (
         f"MAP requires Python 3.11 or newer, but {sys.executable} is "
         f"Python {sys.version_info[0]}.{sys.version_info[1]}.\n"

{mapify_cli-3.31.4 → mapify_cli-3.32.0}/src/mapify_cli/templates/codex/hooks/map-memory-recall.py

@@ -10,13 +10,13 @@ import sys
 # evaluated annotations) fails with a message that never mentions the version.
 # Name the real cause instead. Kept in sync with
 # mapify_cli/python_runtime.MINIMUM_PYTHON.
-# UP036 is suppressed on purpose: the project targets 3.11, but the interpreter
-# executing this shipped file is the user's `python3`, not the project's.
+# Compare the runtime tuple: the executing interpreter is the user's `python3`,
+# not necessarily the Python version targeted by the project's static checker.
 #
 # FAIL-OPEN mode. Exit 1 is a non-blocking hook error for Claude Code (only
 # exit 2, or a JSON deny, blocks a tool call), so the reason reaches the user
 # and the session continues -- a broken interpreter is not a policy decision.
-if sys.version_info < (3, 11):  # noqa: UP036
+if tuple(sys.version_info) < (3, 11):
     _MAP_PYTHON_PROBLEM = (
         f"MAP requires Python 3.11 or newer, but {sys.executable} is "
         f"Python {sys.version_info[0]}.{sys.version_info[1]}.\n"

{mapify_cli-3.31.4 → mapify_cli-3.32.0}/src/mapify_cli/templates/codex/hooks/map-memory-session.py

@@ -10,13 +10,13 @@ import sys
 # evaluated annotations) fails with a message that never mentions the version.
 # Name the real cause instead. Kept in sync with
 # mapify_cli/python_runtime.MINIMUM_PYTHON.
-# UP036 is suppressed on purpose: the project targets 3.11, but the interpreter
-# executing this shipped file is the user's `python3`, not the project's.
+# Compare the runtime tuple: the executing interpreter is the user's `python3`,
+# not necessarily the Python version targeted by the project's static checker.
 #
 # FAIL-OPEN mode. Exit 1 is a non-blocking hook error for Claude Code (only
 # exit 2, or a JSON deny, blocks a tool call), so the reason reaches the user
 # and the session continues -- a broken interpreter is not a policy decision.
-if sys.version_info < (3, 11):  # noqa: UP036
+if tuple(sys.version_info) < (3, 11):
     _MAP_PYTHON_PROBLEM = (
         f"MAP requires Python 3.11 or newer, but {sys.executable} is "
         f"Python {sys.version_info[0]}.{sys.version_info[1]}.\n"

{mapify_cli-3.31.4 → mapify_cli-3.32.0}/src/mapify_cli/templates/codex/hooks/map-stop.py

@@ -10,13 +10,13 @@ import sys
 # evaluated annotations) fails with a message that never mentions the version.
 # Name the real cause instead. Kept in sync with
 # mapify_cli/python_runtime.MINIMUM_PYTHON.
-# UP036 is suppressed on purpose: the project targets 3.11, but the interpreter
-# executing this shipped file is the user's `python3`, not the project's.
+# Compare the runtime tuple: the executing interpreter is the user's `python3`,
+# not necessarily the Python version targeted by the project's static checker.
 #
 # FAIL-OPEN mode. Exit 1 is a non-blocking hook error for Claude Code (only
 # exit 2, or a JSON deny, blocks a tool call), so the reason reaches the user
 # and the session continues -- a broken interpreter is not a policy decision.
-if sys.version_info < (3, 11):  # noqa: UP036
+if tuple(sys.version_info) < (3, 11):
     _MAP_PYTHON_PROBLEM = (
         f"MAP requires Python 3.11 or newer, but {sys.executable} is "
         f"Python {sys.version_info[0]}.{sys.version_info[1]}.\n"

{mapify_cli-3.31.4 → mapify_cli-3.32.0}/src/mapify_cli/templates/codex/hooks/map-token-meter.py

@@ -41,13 +41,13 @@ import sys
 # evaluated annotations) fails with a message that never mentions the version.
 # Name the real cause instead. Kept in sync with
 # mapify_cli/python_runtime.MINIMUM_PYTHON.
-# UP036 is suppressed on purpose: the project targets 3.11, but the interpreter
-# executing this shipped file is the user's `python3`, not the project's.
+# Compare the runtime tuple: the executing interpreter is the user's `python3`,
+# not necessarily the Python version targeted by the project's static checker.
 #
 # FAIL-OPEN mode. Exit 1 is a non-blocking hook error for Claude Code (only
 # exit 2, or a JSON deny, blocks a tool call), so the reason reaches the user
 # and the session continues -- a broken interpreter is not a policy decision.
-if sys.version_info < (3, 11):  # noqa: UP036
+if tuple(sys.version_info) < (3, 11):
     _MAP_PYTHON_PROBLEM = (
         f"MAP requires Python 3.11 or newer, but {sys.executable} is "
         f"Python {sys.version_info[0]}.{sys.version_info[1]}.\n"

{mapify_cli-3.31.4/src/mapify_cli/templates → mapify_cli-3.32.0/src/mapify_cli/templates/codex}/hooks/post-compact-context.py

@@ -20,13 +20,13 @@ import sys
 # evaluated annotations) fails with a message that never mentions the version.
 # Name the real cause instead. Kept in sync with
 # mapify_cli/python_runtime.MINIMUM_PYTHON.
-# UP036 is suppressed on purpose: the project targets 3.11, but the interpreter
-# executing this shipped file is the user's `python3`, not the project's.
+# Compare the runtime tuple: the executing interpreter is the user's `python3`,
+# not necessarily the Python version targeted by the project's static checker.
 #
 # FAIL-OPEN mode. Exit 1 is a non-blocking hook error for Claude Code (only
 # exit 2, or a JSON deny, blocks a tool call), so the reason reaches the user
 # and the session continues -- a broken interpreter is not a policy decision.
-if sys.version_info < (3, 11):  # noqa: UP036
+if tuple(sys.version_info) < (3, 11):
     _MAP_PYTHON_PROBLEM = (
         f"MAP requires Python 3.11 or newer, but {sys.executable} is "
         f"Python {sys.version_info[0]}.{sys.version_info[1]}.\n"
@@ -325,3 +325,4 @@ def main() -> None:
 
 if __name__ == "__main__":
     main()
+

{mapify_cli-3.31.4 → mapify_cli-3.32.0}/src/mapify_cli/templates/codex/hooks/pre-compact-save-transcript.py

@@ -20,13 +20,13 @@ import sys
 # evaluated annotations) fails with a message that never mentions the version.
 # Name the real cause instead. Kept in sync with
 # mapify_cli/python_runtime.MINIMUM_PYTHON.
-# UP036 is suppressed on purpose: the project targets 3.11, but the interpreter
-# executing this shipped file is the user's `python3`, not the project's.
+# Compare the runtime tuple: the executing interpreter is the user's `python3`,
+# not necessarily the Python version targeted by the project's static checker.
 #
 # FAIL-OPEN mode. Exit 1 is a non-blocking hook error for Claude Code (only
 # exit 2, or a JSON deny, blocks a tool call), so the reason reaches the user
 # and the session continues -- a broken interpreter is not a policy decision.
-if sys.version_info < (3, 11):  # noqa: UP036
+if tuple(sys.version_info) < (3, 11):
     _MAP_PYTHON_PROBLEM = (
         f"MAP requires Python 3.11 or newer, but {sys.executable} is "
         f"Python {sys.version_info[0]}.{sys.version_info[1]}.\n"

{mapify_cli-3.31.4 → mapify_cli-3.32.0}/src/mapify_cli/templates/codex/hooks/ralph-context-pruner.py

@@ -25,13 +25,13 @@ import sys
 # evaluated annotations) fails with a message that never mentions the version.
 # Name the real cause instead. Kept in sync with
 # mapify_cli/python_runtime.MINIMUM_PYTHON.
-# UP036 is suppressed on purpose: the project targets 3.11, but the interpreter
-# executing this shipped file is the user's `python3`, not the project's.
+# Compare the runtime tuple: the executing interpreter is the user's `python3`,
+# not necessarily the Python version targeted by the project's static checker.
 #
 # FAIL-OPEN mode. Exit 1 is a non-blocking hook error for Claude Code (only
 # exit 2, or a JSON deny, blocks a tool call), so the reason reaches the user
 # and the session continues -- a broken interpreter is not a policy decision.
-if sys.version_info < (3, 11):  # noqa: UP036
+if tuple(sys.version_info) < (3, 11):
     _MAP_PYTHON_PROBLEM = (
         f"MAP requires Python 3.11 or newer, but {sys.executable} is "
         f"Python {sys.version_info[0]}.{sys.version_info[1]}.\n"

{mapify_cli-3.31.4 → mapify_cli-3.32.0}/src/mapify_cli/templates/codex/hooks/ralph-iteration-logger.py

@@ -19,13 +19,13 @@ import sys
 # evaluated annotations) fails with a message that never mentions the version.
 # Name the real cause instead. Kept in sync with
 # mapify_cli/python_runtime.MINIMUM_PYTHON.
-# UP036 is suppressed on purpose: the project targets 3.11, but the interpreter
-# executing this shipped file is the user's `python3`, not the project's.
+# Compare the runtime tuple: the executing interpreter is the user's `python3`,
+# not necessarily the Python version targeted by the project's static checker.
 #
 # FAIL-OPEN mode. Exit 1 is a non-blocking hook error for Claude Code (only
 # exit 2, or a JSON deny, blocks a tool call), so the reason reaches the user
 # and the session continues -- a broken interpreter is not a policy decision.
-if sys.version_info < (3, 11):  # noqa: UP036
+if tuple(sys.version_info) < (3, 11):
     _MAP_PYTHON_PROBLEM = (
         f"MAP requires Python 3.11 or newer, but {sys.executable} is "
         f"Python {sys.version_info[0]}.{sys.version_info[1]}.\n"

{mapify_cli-3.31.4/src/mapify_cli/templates → mapify_cli-3.32.0/src/mapify_cli/templates/codex}/hooks/safety-guardrails.py

@@ -24,8 +24,8 @@ import sys
 # evaluated annotations) fails with a message that never mentions the version.
 # Name the real cause instead. Kept in sync with
 # mapify_cli/python_runtime.MINIMUM_PYTHON.
-# UP036 is suppressed on purpose: the project targets 3.11, but the interpreter
-# executing this shipped file is the user's `python3`, not the project's.
+# Compare the runtime tuple: the executing interpreter is the user's `python3`,
+# not necessarily the Python version targeted by the project's static checker.
 #
 # FAIL-CLOSED mode. This file is a blocking PreToolUse gate whose only job is to
 # refuse unsafe tool calls, so an interpreter it cannot run on must not degrade
@@ -34,7 +34,7 @@ import sys
 # how a PreToolUse hook blocks), so the call stops and the reason -- version,
 # interpreter, fix -- reaches the operator. Fix python3 in another terminal;
 # tool calls stay blocked until `python3 --version` reports 3.11+.
-if sys.version_info < (3, 11):  # noqa: UP036
+if tuple(sys.version_info) < (3, 11):
     _MAP_PYTHON_PROBLEM = (
         f"MAP requires Python 3.11 or newer, but {sys.executable} is "
         f"Python {sys.version_info[0]}.{sys.version_info[1]}.\n"
@@ -521,3 +521,4 @@ def main() -> None:
 
 if __name__ == "__main__":
     main()
+

{mapify_cli-3.31.4 → mapify_cli-3.32.0}/src/mapify_cli/templates/codex/hooks/scrub-internal-ids.py

@@ -43,13 +43,13 @@ import sys
 # evaluated annotations) fails with a message that never mentions the version.
 # Name the real cause instead. Kept in sync with
 # mapify_cli/python_runtime.MINIMUM_PYTHON.
-# UP036 is suppressed on purpose: the project targets 3.11, but the interpreter
-# executing this shipped file is the user's `python3`, not the project's.
+# Compare the runtime tuple: the executing interpreter is the user's `python3`,
+# not necessarily the Python version targeted by the project's static checker.
 #
 # FAIL-OPEN mode. Exit 1 is a non-blocking hook error for Claude Code (only
 # exit 2, or a JSON deny, blocks a tool call), so the reason reaches the user
 # and the session continues -- a broken interpreter is not a policy decision.
-if sys.version_info < (3, 11):  # noqa: UP036
+if tuple(sys.version_info) < (3, 11):
     _MAP_PYTHON_PROBLEM = (
         f"MAP requires Python 3.11 or newer, but {sys.executable} is "
         f"Python {sys.version_info[0]}.{sys.version_info[1]}.\n"

{mapify_cli-3.31.4/src/mapify_cli/templates → mapify_cli-3.32.0/src/mapify_cli/templates/codex}/hooks/workflow-context-injector.py

@@ -25,13 +25,13 @@ import sys
 # evaluated annotations) fails with a message that never mentions the version.
 # Name the real cause instead. Kept in sync with
 # mapify_cli/python_runtime.MINIMUM_PYTHON.
-# UP036 is suppressed on purpose: the project targets 3.11, but the interpreter
-# executing this shipped file is the user's `python3`, not the project's.
+# Compare the runtime tuple: the executing interpreter is the user's `python3`,
+# not necessarily the Python version targeted by the project's static checker.
 #
 # FAIL-OPEN mode. Exit 1 is a non-blocking hook error for Claude Code (only
 # exit 2, or a JSON deny, blocks a tool call), so the reason reaches the user
 # and the session continues -- a broken interpreter is not a policy decision.
-if sys.version_info < (3, 11):  # noqa: UP036
+if tuple(sys.version_info) < (3, 11):
     _MAP_PYTHON_PROBLEM = (
         f"MAP requires Python 3.11 or newer, but {sys.executable} is "
         f"Python {sys.version_info[0]}.{sys.version_info[1]}.\n"
@@ -1116,3 +1116,4 @@ def main() -> None:
 
 if __name__ == "__main__":
     main()
+

{mapify_cli-3.31.4 → mapify_cli-3.32.0}/src/mapify_cli/templates/codex/hooks/workflow-gate.py

@@ -45,8 +45,8 @@ import sys
 # evaluated annotations) fails with a message that never mentions the version.
 # Name the real cause instead. Kept in sync with
 # mapify_cli/python_runtime.MINIMUM_PYTHON.
-# UP036 is suppressed on purpose: the project targets 3.11, but the interpreter
-# executing this shipped file is the user's `python3`, not the project's.
+# Compare the runtime tuple: the executing interpreter is the user's `python3`,
+# not necessarily the Python version targeted by the project's static checker.
 #
 # FAIL-CLOSED mode. This file is a blocking PreToolUse gate whose only job is to
 # refuse unsafe tool calls, so an interpreter it cannot run on must not degrade
@@ -55,7 +55,7 @@ import sys
 # how a PreToolUse hook blocks), so the call stops and the reason -- version,
 # interpreter, fix -- reaches the operator. Fix python3 in another terminal;
 # tool calls stay blocked until `python3 --version` reports 3.11+.
-if sys.version_info < (3, 11):  # noqa: UP036
+if tuple(sys.version_info) < (3, 11):
     _MAP_PYTHON_PROBLEM = (
         f"MAP requires Python 3.11 or newer, but {sys.executable} is "
         f"Python {sys.version_info[0]}.{sys.version_info[1]}.\n"

{mapify_cli-3.31.4 → mapify_cli-3.32.0}/src/mapify_cli/templates/codex/skills/map-plan/SKILL.md

@@ -130,6 +130,18 @@ that the PRD became ready.
 
 ---
 
+## Pre-flight: Wayfinding Handoff (optional)
+
+A handoff seeds a fresh plan ONLY after Resume Detection returns `no_plan` (or after operator-confirmed archival resolves `goal_mismatch`). On `resume`, existing spec/task-plan wins and the handoff is NOT re-consumed; never overwrite an in-progress plan by re-seeding.
+
+- For explicit `--wayfind <slug>`, select `.map/wayfind/<slug>/handoff.json` (repo-level).
+- Otherwise run `python3 .map/scripts/wayfind_runner.py list_handoffs`; exactly one completed handoff may be offered, but consume only on an explicit user yes. Never guess a match; zero/multiple handoffs means skip.
+- For BOTH explicit and user-accepted offered handoffs, run `python3 .map/scripts/wayfind_runner.py validate_wayfind_handoff <slug>` immediately before seeding. Non-success → STOP: stale, tampered, missing or actively corrected managed evidence is not settled input. Success with `evidence_status: legacy_unrecorded` → surface the provenance warning, never call it verified. Validation is read-only and proves integrity, not truth; do not repair or migrate the map on read.
+
+When a handoff is used, pre-seed the spec: `decisions[]` → **Decisions Made** (settled; do not re-ask), `out_of_scope[]` → **Out of Scope**, `remaining_risks[]` → **Open Questions**. Unresolved research and corrections in risks are not decisions. Continue for anything the handoff did not settle; never modify the wayfinding map.
+
+---
+
 ## Pre-flight: Workflow-Fit Gate
 
 Assess whether MAP planning is warranted. Evaluate these signals:

{mapify_cli-3.31.4 → mapify_cli-3.32.0}/src/mapify_cli/templates/codex/skills/map-release/SKILL.md

@@ -73,7 +73,7 @@ Execute all 12 gates. Read the full gate scripts in [release-reference.md § Pha
 - **Gates 5–6:** Build + twine check
 - **Gate 7:** Security audit (`pip-audit`)
 - **Gates 8–10:** Git state — main branch, clean working directory, up-to-date with origin
-- **Gate 11:** Latest CI run on main must have `conclusion: "success"`
+- **Gate 11:** CI run for `git merge-base HEAD origin/main` must have `conclusion: "success"`; unpushed commits may touch only release metadata
 - **Gate 12:** CHANGELOG.md completeness (Unreleased section exists and has content; commit/entry gap check)
 
 **If any gate fails:** ABORT. Fix issues, re-run Phase 1.
@@ -81,27 +81,21 @@ Execute all 12 gates. Read the full gate scripts in [release-reference.md § Pha
 ## Phase 2: Version Determination
 
 Read CHANGELOG.md `[Unreleased]` section to determine bump type (MAJOR/MINOR/PATCH/EXPLICIT).
-Get current version from `pyproject.toml`. Ask the user directly for the bump type.
+Get current version from `pyproject.toml`.
 
-See [release-reference.md § Phase 2](release-reference.md#phase-2-version-determination) for the full question/option block.
-
-## Phase 3: Execute Version Bump Script
+Ask the user directly for PATCH / MINOR / MAJOR / EXPLICIT, and wait for their answer.
 
-Run `./scripts/bump-version.sh --yes "$BUMP_TYPE"`, then verify:
+For EXPLICIT, ask separately for the exact version. Carry only the user's approved
+`BUMP_TYPE` and exact `NEW_VERSION` into Phase 3; each command runs in a fresh shell.
 
-```bash
-# Verify tag points to HEAD
-TAG_COMMIT=$(git rev-list -n 1 "$LAST_TAG")
-HEAD_COMMIT=$(git rev-parse HEAD)
-[[ "$TAG_COMMIT" != "$HEAD_COMMIT" ]] && echo "❌ Tag mismatch" && exit 1
+See [release-reference.md § Phase 2](release-reference.md#phase-2-version-determination) for the full question/option block.
 
-# 🚨 CRITICAL: Verify __version__ in __init__.py (bump-version.sh known bug)
-INIT_VERSION=$(grep -m1 -E '^__version__ = ' src/mapify_cli/__init__.py | sed -E 's/__version__ = "(.*)"/\1/')
-TAG_VERSION="${LAST_TAG#v}"
-[[ "$INIT_VERSION" != "$TAG_VERSION" ]] && echo "❌ __version__ mismatch — fix manually, see reference" && exit 1
+## Phase 3: Execute Version Bump Script
 
-echo "✅ Version bump successful: all version fields match"
-```
+Show the exact approved version and bump type, then execute the Phase 3 reference
+blocks with those values explicitly supplied in each invocation. Never rely on
+variables left by a previous shell. Verify the version-derived `vX.Y.Z` tag points
+to HEAD and both version fields match it using the Phase 3.3 reference block.
 
 If `__version__` mismatches, follow the fix procedure in [release-reference.md § Phase 3 workaround](release-reference.md#phase-3-execute-version-bump-script).
 
@@ -109,25 +103,24 @@ If `__version__` mismatches, follow the fix procedure in [release-reference.md
 
 **⚠️ CRITICAL PHASE:** Once the tag is pushed the release workflow triggers and publishes to PyPI.
 
-Re-verify: on main branch, CI passed, tag does not already exist on remote. Then ask the user directly for **explicit confirmation** (YES / NO / REVIEW options). See [release-reference.md § Phase 4](release-reference.md#phase-4-push-commit-and-tag-irreversible) for the full confirmation block.
+Re-verify: on main branch, exact merge-base CI completed successfully with matching
+`headSha`, only the three allowed metadata files changed, version-derived tag
+points to HEAD and does not already exist on remote. Then request **explicit user
+confirmation** (YES / NO / REVIEW options).
 
-```bash
-git push origin main
-git push origin "$LAST_TAG"
-```
+Ask the user directly and wait; only an unambiguous YES authorizes pushing.
+
+Read [release-reference.md § Phase 4](release-reference.md#phase-4-push-commit-and-tag-irreversible)
+for the confirmation and push blocks. Recompute the tag in the push invocation;
+consent for an earlier version or commit does not authorize a changed release.
 
 If user aborts: stop workflow, exit gracefully. Tag remains local only.
 
 ## Phase 5: CI/CD Monitoring
 
-Wait for the release workflow to start, then watch it to completion:
-
-```bash
-gh run list --workflow=release.yml --limit 1 --json databaseId,status,conclusion,createdAt
-gh run watch "$RUN_ID"
-FINAL_STATUS=$(gh run view "$RUN_ID" --json conclusion --jq '.conclusion')
-[[ "$FINAL_STATUS" != "success" ]] && echo "❌ Release workflow failed — see reference for rollback" && exit 1
-```
+Use the Phase 5 reference block: recompute the version-derived tag and release
+commit, select `release.yml` for that exact commit (not latest-main), derive
+`RUN_ID` in the same shell, then watch and validate the final status and `headSha`.
 
 The GitHub Release is created automatically by the workflow (no manual step).