sales-demos-verify-eelisted

# sales-demos-verify-ee Runs a playbook **inside** `sales-demos-ee`, the image AAP runs job templates on, rather than beside it on the laptop. ## Why this exists `ansible-playbook` on your laptop resolves `~/.ansible/collections` and the system python. An AAP job template resolves whatever the EE baked in. **Those are two dependency sets and only one of them is what production uses.** Nothing else here can tell them apart. `README.md` says it outright: *"A green CI run does not mean a playbook works — the lint gate cannot execute anything."* So a local run is this repo's only pre-merge verification, and by default it verifies the wrong one. Three times now that gap has held a real defect: | | What it was | What saw it | |---|---|---| | #122 | `python3-devel` repointed `/usr/bin/python3` from 3.12 to 3.9, whose site-packages has no `kubernetes` — every `kubernetes.core` task would fail at runtime on an image that built and pushed clean | nothing, until someone ran it in the image | | #173 | `validate.yml` passes on the laptop, fails in the EE — `check mode and async cannot be used on same task`. Underneath it, `validate.yml` had never once exercised `infra.aap_configuration`'s check-mode paths, on either machine | this skill, first serious use | | #120 | the gap itself | — | ## What is different, and it is not the collections Every collection pin matches exactly, laptop and EE. `build-ee.sh` checks that and is green. **The divergence is underneath them:** **Check this