docs-alignment-lock

Privacy placeholders protect sensitive data by enforcing standard messaging across candidate skills. They replace actual values in policy docs, ensuring privacy-safe language is maintained before PRs are merged.

Checking release hygiene involves running scripted validation checks on policy docs to verify references and enforce privacy gates. This ensures consistent wording and placeholder usage across files like AGENTS.md and README.md before merging.

Yes, frontmatter-based discovery via SKILL.md supports skill candidate documentation workflows. It enables consistent wording, placeholder usage, and release hygiene checks for policy docs during validation.

Validating privacy gates and references in PR templates is done through scripted checks as part of a validation workflow. This verifies references and enforces privacy-safe language before pull requests are submitted.

Release documentation fails privacy checks when policy docs contain inconsistent wording or missing privacy placeholders. Running alignment and hygiene checks before merging identifies these issues and prevents sensitive data leakage.