fix(skills): pass --project-root to the customization resolver (#37)

Core's resolve_customization.py inferred the project root when the flag
was absent, and for a skill installed under the user's home that
inference walked up to ~ — where a user-level install's ~/_bmad made
home look like the project. Team overrides in the real project were
silently ignored: no error, no warning, just shipped defaults.

The resolver itself is fixed in BMAD-METHOD#2802, which is what actually
repairs existing installs since this module ships no copy of the script.
This is the hardening half: passing the root explicitly leaves nothing to
infer, and matches resolve_config.py, which has always required it.

No behaviour change where the inference already landed correctly. The
flag has always existed, so new skill text works against an old resolver
and old text against the new one.

Refs bmad-code-org/BMAD-METHOD#2796


Claude-Session: https://claude.ai/code/session_01L8Hyqmp2giAVgEAnB49zEQ

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: bmadcode

src/agents/gds-agent-game-architect/SKILL.md

@@ -20,7 +20,7 @@ You are Cloud Dragonborn, the Game Architect. You design scalable game architect
 
 ### Step 1: Resolve the Agent Block
 
-Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key agent`
+Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --project-root {project-root} --key agent`
 
 **If the script fails**, resolve the `agent` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
 

src/agents/gds-agent-game-designer/SKILL.md

@@ -20,7 +20,7 @@ You are Samus Shepard, the Game Designer. You drive creative vision, game design
 
 ### Step 1: Resolve the Agent Block
 
-Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key agent`
+Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --project-root {project-root} --key agent`
 
 **If the script fails**, resolve the `agent` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
 

src/agents/gds-agent-game-dev/SKILL.md

@@ -22,7 +22,7 @@ You are Link Freeman, the Game Developer. You implement features, execute dev st
 
 ### Step 1: Resolve the Agent Block
 
-Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key agent`
+Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --project-root {project-root} --key agent`
 
 **If the script fails**, resolve the `agent` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
 

src/agents/gds-agent-game-solo-dev/SKILL.md

@@ -20,7 +20,7 @@ You are Indie, the Game Solo Dev. You ship complete games from concept to launch
 
 ### Step 1: Resolve the Agent Block
 
-Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key agent`
+Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --project-root {project-root} --key agent`
 
 **If the script fails**, resolve the `agent` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
 

src/agents/gds-agent-tech-writer/SKILL.md

@@ -20,7 +20,7 @@ You are Paige, the Technical Writer. You transform complex game development conc
 
 ### Step 1: Resolve the Agent Block
 
-Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key agent`
+Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --project-root {project-root} --key agent`
 
 **If the script fails**, resolve the `agent` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
 

src/workflows/1-preproduction/gds-brainstorm-game/SKILL.md

@@ -22,7 +22,7 @@ description: 'Facilitate game brainstorming sessions with game-specific techniqu
 
 ### Step 1: Resolve the Workflow Block
 
-Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`
+Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --project-root {project-root} --key workflow`
 
 **If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
 

src/workflows/1-preproduction/gds-brainstorm-game/steps/step-04-complete.md

@@ -277,6 +277,6 @@ This step-file architecture ensures consistent, creative brainstorming with user
 
 ## On Complete
 
-Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow.on_complete`
+Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --project-root {project-root} --key workflow.on_complete`
 
 If the resolved `workflow.on_complete` is non-empty, follow it as the final terminal instruction before exiting.

src/workflows/1-preproduction/gds-create-game-brief/SKILL.md

@@ -15,7 +15,7 @@ At the opening greeting, let the user know they can invoke `bmad-party-mode` for
 
 ## On Activation
 
-1. Resolve customization: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`. On failure, read `{skill-root}/customize.toml` directly and use defaults.
+1. Resolve customization: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --project-root {project-root} --key workflow`. On failure, read `{skill-root}/customize.toml` directly and use defaults.
 2. Execute each entry in `{workflow.activation_steps_prepend}` in order.
 3. Treat every entry in `{workflow.persistent_facts}` as foundational context for the rest of the run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.
 4. `{workflow.external_sources}` is an org-configured registry of internal tools (knowledge bases, MCP tools); consult them alongside generic web research on the same triggers in `## Discovery`, org tools preferred when their directive matches. If a named tool is unavailable at runtime, fall back to standard behavior and note the gap when relevant.

src/workflows/1-preproduction/research/gds-domain-research/SKILL.md

@@ -20,7 +20,7 @@ description: 'Conduct game domain and industry research. Use when the user says
 
 ### Step 1: Resolve the Workflow Block
 
-Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`
+Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --project-root {project-root} --key workflow`
 
 **If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
 

src/workflows/1-preproduction/research/gds-domain-research/domain-steps/step-06-research-synthesis.md

@@ -446,6 +446,6 @@ Congratulations on completing comprehensive game domain research!
 
 ## On Complete
 
-Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow.on_complete`
+Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --project-root {project-root} --key workflow.on_complete`
 
 If the resolved `workflow.on_complete` is non-empty, follow it as the final terminal instruction before exiting.