coordination-conformancelisted

# Coordination Conformance Test harness capabilities through local, privacy-safe evidence. Read [references/evidence-policy.md](references/evidence-policy.md) before collecting authenticated product observations. ## Prepare the Run 1. Define one falsifiable capability question and exact harmless input. 2. Use a disposable fixture with no credentials, personal data, remotes, connectors, or unrelated transcripts. 3. Create a run directory outside the installed skill. Keep raw captures outside the repository. 4. Record unsupported, unobserved, and untested behavior distinctly. ## Redact and Record Run `scripts/redact.py` before admitting screenshots, transcripts, or logs. Image evidence requires an opaque rectangle and a `.redacted` derivative. Image redaction requires Python 3.9 or newer and the dependency in `requirements.txt`; text redaction, recording, validation, and summarization use only the Python standard library. Build an observation body as JSON, then use `scripts/record.py` to append it. The recorder hashes evidence, rejects raw screenshots, scans text for common identifiers and secret patterns, and keeps timestamps append-only. Pass `--privacy-checked` only after manually inspecting every derivative; the recorder does not infer that review. Use `--evidence-source synthetic` for harmless generated fixture artifacts; redacted evidence is always recorded as a `redacted-derivative`. ## Validate and Summarize Run: ```sh scripts/validate.py <observations.js