airgap-vettinglisted

# airgap-vetting Rapidly vet a candidate OSS product for air-gap readiness before adoption. Answers eight questions and assigns one of four grades. The organizing insight from the research behind this skill: **"documents an offline flag" ≠ "works offline"** — several tools fall back to downloading even with their own offline flag set, and the decisive distinction (*air-gap-native* vs *proxy-in-disguise*) is only provable by denying egress **after** activation and watching whether the product keeps working. **Arguments** (parse from `$ARGUMENTS`): - target (first positional, required): a product name (`meilisearch`), a local source checkout, a git URL, or a container image ref. Resolve whatever else is needed in Phase 0. - `--dynamic`: run the Phase-2 dynamic harness. Without it the vet is static-only and the verdict says so. - `--repo PATH` / `--image REF`: explicit source checkout / image when the positional target is ambiguous. - `--stakes low|high` (default `low`): `high` mandates the dynamic pass for any candidate that survives static; `low` allows a static-only provisional grade. Enforcement lives in the gate section. **The eight questions:** | # | Question | Reference | |---|----------|-----------| | 1 | Sends telemetry to the internet? | `references/telemetry.md` | | 2 | Can telemetry be turned off — and does off mean off? | `references/telemetry.md` | | 3 | Actually a proxy over a hosted API? | `references/downloads-and-proxy.md` | | 4 | Requires inter