This folder keeps the July 2026 privacy and operator-experience review in a form that can be worked through without losing its source evidence.
checklist.md- canonical, deduplicated remediation checklist.evidence.md- finding IDs, anchors, reproduction steps, observed results, and corrections from runtime verification.privacy-audit.md- source privacy and compliance-readiness audit snapshot.operator-experience-audit.md- source webmaster and operator-experience audit snapshot.
- Work through
checklist.mdin P0, P1, P2, then P3 order unless a dependency requires a different sequence. - Treat the two source audits as snapshots. Record remediation progress only
in
checklist.mdso status does not diverge across files. - Before checking an item, add or update automated tests, run the relevant
repository checks, and confirm the behavior against
evidence.md. - Record the implementing commit and tests beneath the completed item.
- Keep collector/backend work and operator/legal decisions separate from plugin engineering. Automated tests do not constitute legal approval.
- If new evidence overturns a finding, update
evidence.mdfirst and note the correction in the checklist rather than silently deleting the task.