fix(bmm): correct VCS config path in Architect/PM/Dev agents

ISSUE: Path Inconsistency
BMM agents were looking for VCS config at wrong path:
- Old: bmad-core/vcs-config.yaml (incorrect)
- New: .bmad/vcs-config.yaml (correct per BMVCS spec)

IMPACT:
VCS integration failed without manual workaround

FIX:
Updated 3 agent files to use correct path:
- src/modules/bmm/agents/architect.md (line 17)
- src/modules/bmm/agents/pm.md (line 17)
- src/modules/bmm/agents/dev.md (line 22)

TESTING:
Discovered during BMVCS Alpha Phase 2 testing
- Workaround documented, now properly fixed in source
- Test results: ~/test-bmvcs-install/testing/

AFFECTED AGENTS:
✅ Architect - VCS-aware documentation generation
✅ PM - VCS-aware requirements planning
✅ Dev - VCS-aware implementation guidance

This fix enables seamless VCS integration without manual intervention.

Related: #661
Testing: Alpha Phase 2 complete (2025-10-01)

src/modules/bmm/agents/architect.md

@@ -14,7 +14,7 @@
     <i>Load into memory {project-root}/bmad/bmm/config.yaml and set variable project_name, output_folder, user_name, communication_language</i>
     <i>Remember the users name is {user_name}</i>
     <i>ALWAYS communicate in {communication_language}</i>
-    <i>Check if VCS configuration exists in {project-root}/bmad-core/vcs-config.yaml - if present, adapt architecture documentation format and terminology to the configured workflow (GitHub Flow: lightweight docs, GitFlow: version-oriented, Trunk-Based: flag-gated, No VCS: comprehensive monolithic). If missing, architecture decisions remain VCS-neutral.</i>
+    <i>Check if VCS configuration exists in {project-root}/.bmad/vcs-config.yaml - if present, adapt architecture documentation format and terminology to the configured workflow (GitHub Flow: lightweight docs, GitFlow: version-oriented, Trunk-Based: flag-gated, No VCS: comprehensive monolithic). If missing, architecture decisions remain VCS-neutral.</i>
   </critical-actions>
   <!-- IDE-INJECT-POINT: architect-agent-instructions -->
   <cmds>

src/modules/bmm/agents/dev.md

@@ -19,7 +19,7 @@
     <i critical="MANDATORY">Pin the loaded Story Context into active memory for the whole session; treat it as AUTHORITATIVE over any model priors</i>
     <i critical="MANDATORY">For *develop (Dev Story workflow), execute continuously without pausing for review or "milestones". Only halt for explicit blocker conditions (e.g., required approvals) or when the story is truly complete (all ACs satisfied and all tasks checked).</i>
     <i>ALWAYS communicate in {communication_language}</i>
-    <i>Check if VCS configuration exists in {project-root}/bmad-core/vcs-config.yaml - if present, adapt code delivery and commit suggestions to the configured workflow (GitHub Flow: atomic commits with conventional style, GitFlow: descriptive commits with branch prefixes, Trunk-Based: feature-flag wrapped changes, No VCS: complete packaged code, SVN/other: appropriate VCS terminology). If missing, remain VCS-neutral.</i>
+    <i>Check if VCS configuration exists in {project-root}/.bmad/vcs-config.yaml - if present, adapt code delivery and commit suggestions to the configured workflow (GitHub Flow: atomic commits with conventional style, GitFlow: descriptive commits with branch prefixes, Trunk-Based: feature-flag wrapped changes, No VCS: complete packaged code, SVN/other: appropriate VCS terminology). If missing, remain VCS-neutral.</i>
   </critical-actions>
 
   <cmds>

src/modules/bmm/agents/pm.md

@@ -14,7 +14,7 @@
     <i>Load into memory {project-root}/bmad/bmm/config.yaml and set variable project_name, output_folder, user_name, communication_language</i>
     <i>Remember the users name is {user_name}</i>
     <i>ALWAYS communicate in {communication_language}</i>
-    <i>Check if VCS configuration exists in {project-root}/bmad-core/vcs-config.yaml - if present, adapt PRD scope and release planning to the configured workflow (GitHub Flow: feature-scoped PRDs, GitFlow: release-scoped with versions, Trunk-Based: flag-gated increments, No VCS: comprehensive upfront requirements). If missing, requirements remain workflow-neutral.</i>
+    <i>Check if VCS configuration exists in {project-root}/.bmad/vcs-config.yaml - if present, adapt PRD scope and release planning to the configured workflow (GitHub Flow: feature-scoped PRDs, GitFlow: release-scoped with versions, Trunk-Based: flag-gated increments, No VCS: comprehensive upfront requirements). If missing, requirements remain workflow-neutral.</i>
   </critical-actions>
   <cmds>
     <c cmd="*help">Show numbered cmd list</c>