cli: drift status, shadow drift detail, per-query staleness + prime block (spec steps 1–3)

[jschatz1]

Steps 1–3 of the graph staleness / git drift spec. Companion to kaicontext/kai-engine#23, which this depends on.

kai status (step 1)

Graph:      2 commits behind git HEAD (graph 956aa12d11ce · git 2c6ddf3511cb · oldest unprocessed 2h ago)
            Run 'kai capture' (or 'kai import' for many commits) to catch up.

One line per relationship with an action hint; --json gains the drift block. Merge-base/rev-list only on the status path.

kai shadow drift (step 2)

No-flag default is the drift detail view: per-commit files touched, import-target annotations ([adds imports into pkg/foo]), the superseded leg on divergence, manifest state. Explicit --snap/--git-ref keep the legacy snapshot comparison. Pin sites (bridge import, kai import) sync the manifest so catch-up shrinks it.

Per-query staleness (step 3)

kai query callers|dependents|impact, kai test affected, kai blame:

• Answer neighborhood (every file in the answer + the target) classified before printing.
• stale-refused (orphaned graph, or ≥ staleness.refuse_after_intersecting intersecting commits) suppresses the answer and errors with the reason. Default: never refuse.
• Otherwise the answer prints, then one stderr line (--quiet to suppress):

  staleness: stale-suspect — 1 unprocessed commit intersects this query (bf5e3fd6ee20); run 'kai capture' to catch up
  

  fresh stays silent.
• --strict (or staleness.strict) makes stale-suspect exit 75 (the CI tripwire convention). Default exit stays 0 so existing scripts don't break.
• kai blame --json embeds the full staleness block (existing shapes preserved).
• kai prime appends a ## Staleness section to injected context — outside the char budget so truncation can't drop it — listing intersecting commits and steering agents to prefer current file contents.

New config slice: staleness.strict, staleness.refuse_after_intersecting (zero values = annotate, never block).

Verified end-to-end

Scratch repo: synced query silent → drift commit touching pkg/foo → same query annotates stale-suspect with the commit, unrelated query stale-valid; --strict exits 75; threshold config refuses before printing; --quiet suppresses; prime carries the block; blame JSON embeds it. All suites green (engine drift/status, cmd/kai, internal/config, vet, gofmt).

Note for CI

Builds against local engine via go.work; proxy-resolved CI needs an engine tag containing kaicontext/kai-engine#23.

🤖 Generated with Claude Code

[kaicontext]

🔍 Kai review

Warning

Needs a look — intent partially matches, 2 flags.

• 🟡 Intent partially matches — semantic match unconfirmed
• ✅ No coverage gaps
• ⚠️ [correctness] cmd/kai/status_drift.go:115 — `annotateStaleness` calls `os.Exit(exitStaleSuspect)` which terminates immediately without running any `defer`red cleanup in the callin…
• ⚠️ [correctness] cmd/kai/main.go:12950 — `runStatus` is changed to call `status.WriteOutputFull` (adding a `driftReport` arg) but this function does not appear to be defined anywhere…

_{+617 −14 · 4 files · reaches 15}

View finding → · Awaiting your verdict — Kai never approves its own finding.