reference-drift-probelisted

# Reference-drift probe Is the template still the best version of itself? ```bash python scripts/reference_drift_probe.py --target <skill-repo> --repos-root ~/src python scripts/reference_drift_probe.py --target <skill-repo> --repos-root ~/src --format json python scripts/reference_drift_probe.py --target <skill-repo> \ --repo-path malkreide/swiss-efv-mcp=/srv/swiss-efv-mcp python scripts/reference_drift_probe.py --target <skill-repo> --repos-root ~/src --no-unanimity ``` Exit `0` agree, `2` **findings**, `3` nothing readable (NOT MEASURED), `4` the checkout moved during the run, `127` the harness could not run. ## Why `reference/` in a skill repository ships code that gets copied into servers. After the copy, the two halves drift apart in both directions and neither side looks wrong: in the server only the copied fragment is visible, and in the skill repository there is no server. Nobody is ever looking at both. The dangerous direction is the template being behind. A server that missed a fix is one repository with one defect; a stale template hands the same defect to every server built next, at the moment somebody is least likely to read the code they are copying. ## The mapping is declared, never guessed `reference/adoption.toml` names which template, which repositories, which file and symbol, and since when. There is no name-similarity fallback. A guessed mapping produces a finding nobody can retrace, and a finding nobody can retrace is how a gate gets switched