What problem does it solve? Publishing the awid.ai static site requires pushing the exact reviewed main commit to a dedicated deploy branch without introducing unreviewed changes, dirty working trees, or non-fast-forward history. This Skill encodes that guarded deployment procedure so the release happens only from a verified state. ## Core Features & Use Cases - Guarded deployment: Runs make deploy-site, which refuses a dirty checkout, requires the commit to match fetched origin/main, enforces a fast-forward from the current deploy-awid-landing tip, and reads the remote ref back after pushing. - Documentation freshness gate: Ensures the site's committed mirrors of docs/identity-guide.md and docs/trust-model.md are current and reviewed before deployment, with make sync-awid-site-docs as the remediation path. - Use Case: After a docs update to the aweb identity guide is reviewed and merged to main, use this Skill to push that exact commit to the deploy-awid-landing branch so Render rebuilds awid.ai, then verify the live site serves the updated content. ## Quick Start Deploy the current reviewed main commit to awid.ai by running the deploy-site make target and then verify the Render deployment and live site content.