An optional, on-demand drift audit for bypass cases: a merge or an external\nedit drifted a tracked source file you are not about to commit, so commit-gate's\nPhase 5.5 auto-heal did not fire. This skill reports stale docs and lets you\nact on each one individually.
\nThis skill is NOT in the daily loop. Commit-gate auto-heal (Phase 5.5,\nheal_worklist) owns the routine maintenance path. Invoke this only when drift\nwas introduced outside a commit (e.g. a direct push, a merge you did not\nauthor, a manual file edit).
Read these before computing drift:
\n.codearbiter/.provenance/ — the per-doc provenance records. Load all\nrecords via load_provenance_dir from\n${CLAUDE_PLUGIN_ROOT}/hooks/_provenancelib.py..codearbiter/code-map.md — coarse concern map; read to orient on which\nmodules the stale docs govern.Use _provenancelib helpers in this order:
load_provenance_dir(root + \"/.codearbiter/.provenance/\") — returns the\nprovenance map {doc: record}.drift_trigger: true paths across all records.batch_hash(paths, runner) — hash every existing path in one git call.compute_drift(provenance_map, current_hashes) — returns a drift report\n{doc: [{path, kind}]} for docs that have stale sources.Alternatively reuse the same logic as startup_drift_line by calling it for\na human-readable summary, then inspecting compute_drift directly for detail.
If the drift report is empty: report \"no stale docs — provenance is fresh\"\nand exit. No further action required.
\nFor each doc in the drift report, call changed_scope(doc_provenance, drift)\nto list its drifted paths. Present a concise report before offering actions:
Stale docs (N):\n <doc>: <path1>, <path2> (changed | missing)\n ...\nFor each stale doc, present three choices and wait for the user to select one:
\nre-scout — dispatch an incremental re-scout of the drifted paths for this\ndoc, scoped to those paths only (like commit-gate Phase 5.5 heal but manually\ninvoked). The scout re-reads the changed paths and reports whether claims still\nhold. If claims still hold: silently re-baseline the hashes via rebaseline.\nIf claims changed: surface the proposed doc edits for the user to accept before\nre-baselining.
re-baseline — acknowledge the drift without re-scouting: call\nrebaseline(provenance, current_hashes) to update the stored hashes silently.\nUse this when the source change is cosmetic (formatting, comments, whitespace)\nand the derived doc claims are still accurate.
defer — do nothing for this doc now. The drift line will reappear at the\nnext SessionStart. Use when the change is in-progress and the doc update should\nwait for a later commit.
\nAfter processing all stale docs, summarize which docs were re-scouted,\nre-baselined, or deferred.
\nThis skill MUST NOT commit. If re-scout or re-baseline produces updated\n.codearbiter/.provenance/ records, those file changes ride the next\nuser-initiated commit through commit-gate normally. No staging, no commits here.