Add per-deployment adaptive optimization + VEIL npm metaharness (ADR-289)

Two additions on top of the hyper-optimized VEIL shield.

1) Adaptive optimization (v2/crates/wifi-densepose-privshield/src/optimize.rs):
   - optimal_bits_across_snr / model_optimal_bits_for_snr: the throughput-
     optimal feedback resolution shifts with SNR (unconstrained optimum 4 bits
     at 5-10 dB, 3 bits at 20-40 dB); within the spec {5,7,9} set it stays 5,
     which is why the shipped shield is SNR-stable.
   - adaptive_shield / min_passes_for_n: derive a shield for a specific
     deployment. Finding: the collapse budget is N-independent in this model
     (48 passes collapses N in {8,64} alike) — it is set by the fine-subspace
     dimension, not the candidate count. Defaults unchanged, so the proof
     witness is untouched. 38 tests + doctest pass; clippy -D warnings clean.

2) npm metaharness harness/wifi-densepose-privshield/ (ADR-289), mirroring
   wifi-densepose-sar-harness (ADR-286) with two improvements:
   - @metaharness/* imported dynamically inside the commands that need them, so
     `guidance` and `--help` run with ZERO dependencies installed (offline / pre
     `npm install`).
   - a dependency-free VEIL `guidance` command: a source-cited, evidence-
     labelled, read-only capability map (topics: overview, threat,
     countermeasure, compliance, optimization, experiment).
   Standard router + flywheel (SYNTHETIC) + Darwin wiring, tailored to VEIL
   task axes and policy levers. Tests: smoke + router + flywheel (need install)
   and guidance (offline). .harness manifest generated with real per-file
   hashes. Validated offline: cli syntax, --help, guidance topics, exit codes,
   graceful degradation when deps are absent.

Docs: research bundle 08 gains a per-deployment adaptivity section; 07 and the
crate README point at the harness; ADR-289 added and indexed.

Co-Authored-By: claude-flow <ruv@ruv.net>
Claude-Session: https://claude.ai/code/session_01WEXNqzs7UsfNFBcP5yW21p

docs/research/privacy-shield/07-implementation-and-roadmap.md

@@ -13,6 +13,12 @@
 - **This research bundle** (`docs/research/privacy-shield/`).
 - **[ADR-288](../../adr/ADR-288-veil-privacy-shield-compliant-waveform.md)** — the
   formal decision record.
+- **npm metaharness** `harness/wifi-densepose-privshield/`
+  ([ADR-289](../../adr/ADR-289-wifi-densepose-privshield-harness-via-metaharness.md))
+  — a per-crate contributor harness (architect/implementer/reviewer/test-writer,
+  router, flywheel) with a dependency-free `guidance` surface that serves this
+  bundle's capability map. `npx wifi-densepose-privshield-harness guidance
+  --topic optimization`.
 
 The crate is intentionally a **leaf with no internal RuView dependencies**
 (mirrors `wifi-densepose-aether`), so it can be reasoned about, fuzzed, and

docs/research/privacy-shield/08-optimization.md

@@ -110,7 +110,29 @@ expected to open up — a hardware study (roadmap P5) will re-measure it.
 
 ---
 
-## 6. Robustness caveats (unchanged from the threat model)
+## 6. Per-deployment adaptivity
+
+The optimum is not one number — `optimize` derives it per deployment:
+
+- **SNR → feedback resolution.** `optimal_bits_across_snr` shows the
+  *unconstrained* throughput-optimal resolution shifting with SNR: **4 bits at
+  5–10 dB, 3 bits at 20–40 dB** (low SNR values fine resolution more because
+  the Shannon capacity is near-linear there, so the residual costs more). Within
+  the spec-allowed {5,7,9} set the choice is 5 bits across this whole range —
+  the residual is already negligible at 5 bits — which is why the shipped shield
+  is SNR-stable.
+- **Identity count → mixing.** `adaptive_shield(base, n)` derives the config for
+  a room with `n` expected occupants. A notable finding: in this model the
+  collapse budget is **N-independent** (min 48 passes collapses N∈{8,64}
+  alike), because a well-mixed Haar-like rotation destroys per-identity
+  structure regardless of how many identities there are — the budget is set by
+  the fine-subspace dimension, not the candidate count. So `adaptive_shield`
+  returns the same 96/5 across that range: the default is robust, not a point
+  tuning.
+
+Both are surfaced through the harness `guidance --topic optimization`.
+
+## 7. Robustness caveats (unchanged from the threat model)
 
 - The collapse is verified against two classifiers and two N; a learned
   attacker on real captures must still be checked (P2/P5).