drift-sweeplisted

# /foundry:drift-sweep An operator/agent **ADVISORY** sweep that names the **whole batch** of frozen atoms a schema/module migration just invalidated, instead of letting each one be rediscovered one at a time, weeks apart, at its own build. It is the **batch-level, schema-coherence analogue** of `/foundry:coherence-check` (which covers citations): same advisory posture, same tri-state fail-closed exit, same fresh-walk-every-run discipline — the missing dimension is schema identifiers instead of citations. > **DORMANT:** the engine below (`scripts/foundry_drift_sweep.py`) does **not** ship — the > command is design intent for a re-implementation, not a runnable verb today. ```bash python3 "${CLAUDE_PLUGIN_ROOT}/scripts/foundry_drift_sweep.py" \ --base /path/to/base-snapshot.json \ --head /path/to/head-snapshot.json \ --corpus-root "$CLAUDE_PROJECT_DIR" # default: $CLAUDE_PROJECT_DIR or cwd ``` ## Input — a base->head snapshot PAIR (host-side, HOW obtained is a wiring concern) The sweep takes **two already-built** snapshots from the system-state snapshot tool (`foundry_system_snapshot.build_system_snapshot()` results — `{schema_version, schema_grounded, module_grounded, grounding_configured, entities, modules, signature}`) as JSON files. It opens **no grounding source itself** and does **no git plumbing** — how the caller obtains the base (pre-migration) and head (post-migration) snapshots (e.g. re-resolving the same `grounding` block at two different migratio