ads-validate

1# Validate Claude Ads
2 
3Choose the narrowest validation target:
4 
5- Contract or bundle: use the deterministic core validator.
6- Scores: validate controls, findings, category weights, and coverage.
7- Run: verify manifest completeness, source lineage, privacy, worker status, and
8  render artifacts.
9- Capability: require implementation, fixtures, tests, sources, and truthful mode.
10- Repository: run deterministic, routing, security, installer, rendering, evidence,
11  packaging, and freshness gates.
12- Release: dispatch a fresh-context release verifier.
13 
14Return machine-readable pass/fail results, the highest-priority blocker, exact
15evidence, and recovery steps. Never promote maturity because documentation is
16polished or a prior release passed. Stale evidence and skipped remote CI demote
17readiness.
18 
19Reverify-or-demote decisions belong to `ads-research`. If an expired claim cannot be reverified because source or filesystem access is
20unavailable, return a failed current-evidence check, demote that claim for the
21current run, and block dependent release-current assertions before asking for the
22missing access.
23 
24## Install and uninstall validation
25 
26An uninstall may remove only exact paths in the matching Claude Ads ownership
27manifest. Validate the entire manifest and configured root boundaries before any
28deletion. If the manifest is absent, invalid, mismatched, or unsafe, stop before
29deleting anything and require manual review. Never discover targets with an
30…