Make the wp-form-deploy-qa skill well written enough to reliably prove site lead forms work, and register it as a slash command.
Skills/wp-form-deploy-qa/SKILL.md (v1.1.0). Confirmed via diff before editing, so no duplicate skill was created.set -a; source .credentials/vault.env; set +a + LITIFY_ORG connectivity check).PROJECTS_ROOT env + find fallback so a moved tree does not make the run quit.commands/wp-form-deploy-qa.md following the established pattern (routes_to canonical, aliases, how-to-invoke). Aliases: /wp-form-deploy-qa, /wordpress-form-deploy-qa, /form-qa, /check-forms.Skills/SKILL-INDEX.md (alphabetical, before wp-site-health).Load With skills exist (litify-live-defaults, litify-operator-core, salesforce-litify-offline-conv, wp-site-health).admin/scripts/rendered-form-contract-qa.py exists and that the endpoint/classes/probe-table referenced in the skill match the script source.bash -n.Completed. Scope was authoring/QA only; no live WordPress, Litify, or DNS writes were made.
/wp-form-deploy-qa) to capture a current PASS/FAIL baseline for the contact + homepage forms.Skills/wp-form-deploy-qa/SKILL.md, commands/wp-form-deploy-qa.md, Skills/SKILL-INDEX.md to sail-projects-root.The skill is procedure-complete and self-contained. If forms need actual verification, invoke /wp-form-deploy-qa; it loads creds, flushes cache, runs the rendered contract audit, and reads back the latest Litify lead. Treat the live site and LITIFY_ORG as authoritative over any value written in the skill. Rollback: prior version was v1.1.0 (130 lines, identical to the uploaded file); revert the single SKILL.md and delete the two new files (commands pointer + index entry) to undo.