recalibratelisted

The ecosystem-learning loop. `/reflect` learns from what happened in sessions; this skill learns from what changed in the world. The scaffold's encoded practices are claims about tools and methods that keep evolving — claims rot. Founding example: this repo's worktree skill shipped with a manual script two weeks after `claude --worktree` made it the fallback rather than the path. ## Hold in mind 1. The gate is method, not publisher: any source can be primary, and the test is a verbatim quote you read yourself. A fetch summary is never evidence — not from an aggregator, and not from a subagent. 2. Propose, never edit: your only outputs are `Status: candidate` ledger entries and the run stamp — `/evolve` keeps promotion authority, and the evidence discipline survives. 3. Verify drift in both directions: absence of confirmation is not deprecation — flag a convention only when a primary source contradicts or supersedes it — and presence in the scaffold is not currency — an encoded practice is a claim about a moving target, so re-verify it against primary sources before relying on it or "fixing" it. 4. Aim at what would cost the most to lose: the conventions this repo is proudest of are the ones a comfortable audit skips. Name them first. 5. Ledger rules apply: one concept per entry, dedupe by Evidence-bump, entries below the marker, source URL in the Trigger line. Durable discipline goes in the Rule; the dated vendor fact stays in the Trigger. ## Steps 1. Enumerate the conven