Align BMAD paths with new knowledge structure and automate project registry sync

80_bmad/base/_bmad/bmm/workflows/4-implementation/code-review/instructions.xml

@@ -13,9 +13,12 @@
   <critical>Tasks marked complete but not done = CRITICAL finding</critical>
   <critical>Acceptance Criteria not implemented = HIGH severity finding</critical>
   <critical>Do not review files that are not part of the application's source code. Always exclude the _bmad/ and _bmad-output/ folders from the review. Always exclude IDE and CLI configuration folders like .cursor/ and .windsurf/ and .claude/</critical>
+  <critical>Before starting review, synchronize Lead_tech project registry via: `bash $LEADTECH/scripts/sync-projects-conf.sh --project-root {project-root} --sync-existing`.</critical>
 
 
   <step n="1" goal="Load story and discover changes">
+    <action>Run: `bash $LEADTECH/scripts/sync-projects-conf.sh --project-root {project-root} --sync-existing`</action>
+    <action if="sync command fails">Output warning and continue review if repository state is still analyzable.</action>
     <action>Use provided {{story_path}} or ask user which story file to review</action>
     <action>Read COMPLETE story file</action>
     <action>Set {{story_key}} = extracted key from filename (e.g., "1-2-user-authentication.md" → "1-2-user-authentication") or story
@@ -229,7 +232,7 @@
 
       Review all findings for: anti-patterns found, recurring issues, architecture decisions confirmed or invalidated during this review.
     </output>
-    <action>For EACH candidate (aim for 1-3): write a proposal to ~/AI_RULES/_Assistant_Lead_Tech/95_a_capitaliser.md ONLY — NEVER inside the project repo. FORMAT = "DATE — base / FILE_UPDATE_PROPOSAL / Fichier cible: &lt;target&gt; / Pourquoi: &lt;reason&gt; / Proposition: &lt;content&gt;"</action>
+    <action>For EACH candidate (aim for 1-3): write a proposal to $LEADTECH/95_a_capitaliser.md ONLY (Mac: ~/AI_RULES/_Assistant_Lead_Tech/95_a_capitaliser.md ; NUC: /srv/helpers/_Assistant_Lead_Tech/95_a_capitaliser.md) — NEVER inside the project repo. FORMAT = "DATE — base / FILE_UPDATE_PROPOSAL / Fichier cible: &lt;knowledge/backend/patterns/&lt;theme&gt;.md | knowledge/backend/risques/&lt;theme&gt;.md | knowledge/frontend/patterns/&lt;theme&gt;.md | knowledge/frontend/risques/&lt;theme&gt;.md | knowledge/ux/patterns/&lt;theme&gt;.md | knowledge/ux/risques/&lt;theme&gt;.md | knowledge/n8n/patterns/general.md | knowledge/n8n/risques/general.md | knowledge/product/patterns/general.md | knowledge/product/risques/&lt;theme&gt;.md | knowledge/workflow/risques/story-tracking.md | 10_conventions_redaction.md | 40_decisions_et_archi.md | 90_debug_et_postmortem.md&gt; / Pourquoi: &lt;reason&gt; / Proposition: &lt;content&gt;"</action>
     <action if="nothing worth capitalizing">Output explicitly: "Rien à capitaliser pour cette review." — do NOT skip silently</action>
   </step>
 

80_bmad/base/_bmad/bmm/workflows/4-implementation/dev-story/instructions.xml

@@ -11,8 +11,11 @@
     other instruction.</critical>
   <critical>Do NOT schedule a "next session" or request review pauses unless a HALT condition applies. Only Step 6 decides completion.</critical>
   <critical>User skill level ({user_skill_level}) affects conversation style ONLY, not code updates.</critical>
+  <critical>Before any implementation work, synchronize Lead_tech project registry via: `bash $LEADTECH/scripts/sync-projects-conf.sh --project-root {project-root} --sync-existing`.</critical>
 
   <step n="1" goal="Find next ready story and load it" tag="sprint-status">
+    <action>Run: `bash $LEADTECH/scripts/sync-projects-conf.sh --project-root {project-root} --sync-existing`</action>
+    <action if="sync command fails">Output warning and continue only if story work can proceed safely.</action>
     <check if="{{story_path}} is provided">
       <action>Use {{story_path}} directly</action>
       <action>Read COMPLETE story file</action>

80_bmad/base/_bmad/bmm/workflows/qa-generate-e2e-tests/instructions.md

@@ -6,6 +6,16 @@
 
 ## Instructions
 
+### Step -1: Sync Lead_tech project registry
+
+Before any test generation work, run:
+
+```bash
+bash $LEADTECH/scripts/sync-projects-conf.sh --project-root {project-root} --sync-existing
+```
+
+If the command fails, report the warning and continue only if test generation can proceed safely.
+
 ### Step 0: Detect Test Framework
 
 Check project for existing test framework: