Validate standalone deployment playbooks in CI
Expanded the playbook validation matrix and aligned contributor guidance with the active include graph and Docker-before-firewall task order.
Deployment-safety improvement
CI now validates both supported Ansible entry points instead of leaving the standalone deployment playbook outside lint and syntax checks.
Problem
CI linted only the primary playbook and a Docker-group test, so syntax or policy regressions in the standalone deployment playbook could merge undetected. Contributor guidance also referenced stale task files and contradicted the implemented security ordering.
Approach
Runs YAML and Ansible lint across all supported playbooks, syntax-checks both installation entry points, and documents the current nested task flow without changing deployment runtime behavior.
Impact and scope
- Closes a validation gap for users who deploy through the standalone playbook rather than the primary entry point.
- Keeps contributor instructions consistent with the repository's active task graph and privilege-migration sequence.
- Changes CI and documentation only; it does not alter roles, variables, or deployed hosts.
Validation
- YAML lint, production-profile Ansible lint, and syntax checks passed for the supported playbook set.
- Maintainer validation exercised the playbook on an AWS host with pinned dependencies and covered Docker-group privilege migration.
- All six hosted checks passed, the linked issue is closed, and the verified merge commit credits Goutam Adwant.