context-checksolid

# context-check An optional, on-demand drift audit for bypass cases: a merge or an external edit drifted a tracked source file you are not about to commit, so commit-gate's Phase 5.5 auto-heal did not fire. This skill reports stale docs and lets you act on each one individually. This skill is NOT in the daily loop. Commit-gate auto-heal (Phase 5.5, `heal_worklist`) owns the routine maintenance path. Invoke this only when drift was introduced outside a commit (e.g. a direct push, a merge you did not author, a manual file edit). <!-- catalog-compatibility-notice:start --> > Compatibility route. Prefer `$ca-status drift` for new explicit usage. The retained entry > and natural-language intent use this owner under > [includes/command-compatibility.md](../../includes/command-compatibility.md). <!-- catalog-compatibility-notice:end --> ## Entry boundaries Use this owner for a requested provenance drift audit, `$ca-status drift`, or the explicit `$ca-context-check` compatibility entry. Explanation-only questions and ordinary status snapshots remain read-only answers, not repair requests. Report first. Write only after the user selects re-scout or re-baseline for that document; never change an unselected derived document. This owner neither stages nor commits. Routine commit-gate auto-heal is unchanged. ## Pre-flight Read these before computing drift: 1. `.codearbiter/.provenance/` — the per-doc provenance records. Load all records via `load_provenance_dir` from [hooks/