Propagate ml-lab.md changes to the two downstream artifacts that must stay in sync with it — plugins/ml-lab/ML_LAB_FLOW.md (mermaid flowchart) and README.md (mermaid copy + investigation logging section + Gate prose).
You are executing the sync-ml-lab-docs skill. Your job is to propagate any changes in plugins/ml-lab/ml-lab.md to two downstream artifacts and report exactly what changed.
| File | What must stay in sync |
|---|---|
plugins/ml-lab/ML_LAB_FLOW.md | The mermaid flowchart — must match the workflow structure, node labels, gate labels, and LOG node caption in ml-lab.md |
README.md | Mermaid block under ### The Full Workflow + any prose sections that describe or summarize workflow content from ml-lab.md (gates, logging, example runs, etc.) |
Read these files in full:
plugins/ml-lab/ml-lab.md (source of truth)plugins/ml-lab/ML_LAB_FLOW.mdREADME.mdplugins/ml-lab/ML_LAB_FLOW.mdExtract the canonical mermaid flowchart from plugins/ml-lab/ml-lab.md. The flowchart is the primary visual specification — it must reflect:
Rewrite the mermaid block in ML_LAB_FLOW.md to match.
README.md — mermaid blockLocate the mermaid flowchart block under the ### The Full Workflow section in README.md. Replace it with the same flowchart you just put in ML_LAB_FLOW.md. The block starts with ```mermaid and ends with ```.
README.md — prose sections derived from ml-lab.mdREADME.md contains several narrative sections that summarize or describe content from plugins/ml-lab/ml-lab.md. For each such section, compare against the corresponding source section in ml-lab.md and update the README to reflect the current authoritative content. Do not look for specific expected text — read both files and use judgment to identify any drift.
Sections to check include (but are not limited to):
For each section that has drifted from ml-lab.md: update the README to match the current behavior. Preserve README-appropriate voice (user-facing, explanatory) rather than copying agent-prompt text verbatim.
List every change made, organized by file. For each change, give one line describing what was updated and why (e.g., "Updated LOG node caption to reference uv run log_entry.py"). If a file was already in sync, say so explicitly.
If no changes were needed anywhere, report "All downstream artifacts already in sync with plugins/ml-lab/ml-lab.md."
Do NOT remind the user to run claude plugin reinstall ml-lab. The PostToolUse hook (sync-plugin-cache.sh) fires automatically on every Edit or Write to any file under plugins/ml-lab/ and rsyncs the directory to the plugin cache immediately — manual reinstall is not needed.