# Lead_tech override — workflow code-review (porte aussi l'ex-rôle QA, advisory strict=false).
[workflow]
activation_steps_prepend = [
  "Before starting review, synchronize Lead_tech project registry: `bash $LEADTECH/scripts/sync-projects-conf.sh --project-root {project-root} --sync-existing`. If it fails, warn and continue if the repository state is still analyzable.",
]
activation_steps_append = [
  "Ex-QA duty: during review, call Leadtech MCP `emit_checklist(agent_role='reviewer', domain, story_text)` and `validate_patch(domain, diff_text, changed_files, strict=false)` before accepting 'done'. QA stays advisory (strict=false) on purpose — strict blocks were already taken on the dev side (Phase 2 partielle). A blocking_issues surfacing here means a dev override was not properly traced: refuse 'done' until the override and its rationale are explicit in `Leadtech MCP Gates`.",
]
persistent_facts = [
  "file:{project-root}/_bmad/custom/leadtech-capitalisation.md",
  "Capitalisation review: for EACH candidate (aim 1-3) write a FILE_UPDATE_PROPOSAL to 95_a_capitaliser.md ONLY — never inside the project repo. If nothing: output explicitly 'Rien à capitaliser pour cette review.' — do NOT skip silently. Cibles QA: frontend tests patterns+risques, knowledge/workflow/risques/story-tracking.md, 90_debug_et_postmortem.md.",
]
