drift-risk-audit-artifact-updateslisted

# Drift Risk Audit Artifact Updates Skill Use this skill when a Drift change requires explicit updates to the audit stack under `audit_results/`. ## When To Use - A file under `src/drift/signals/` changes materially - A file under `src/drift/ingestion/` changes materially - A file under `src/drift/output/` changes materially - An input path, output path, or trust boundary changes - Precision or recall changes by more than 5 percentage points - A push would otherwise fail the risk-audit gate ## Core Rules 1. **Run the Drift Policy Gate first.** Audit updates do not rescue inadmissible work. 2. **Treat audit artifacts as contracts, not optional docs.** POLICY §18 makes them mandatory. 3. **Update the right artifact for the change type.** Any audit file is not enough. 4. **Never delete the four protected audit artifacts.** The gate checks existence. 5. **Use bypasses only with explicit maintainer approval and a documented emergency reason.** ## Step 0: Run The Drift Policy Gate Before touching the audit stack, use the gate format from `.github/instructions/drift-policy.instructions.md`. ## Step 1: Classify The Change Sort the implementation into one of these categories: ### A. Signal changed Examples: - new signal - materially changed heuristic - changed finding criteria - changed scoring-readiness behavior Treat a change as material when it changes detection scope, improves or worsens precision/recall in a meaningful way, alters actionable output, or changes what r