mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-08 11:46:35 +00:00
kevinveenbirkenbachandClaude Opus 4.7
5b8cb71884
Inner-loop iteration on a deployed stack often needs a one-off sidecar container against the same docker daemon the stack lives on — typical cases are rerunning a Playwright project with a patched .env, retrying an arbitrary CLI image against an app container, or smoke-checking a release image without going through Ansible. Without a wrapper the caller has to spell out `docker exec <host-container> docker run --rm <flags...> <image> <cmd>` by hand, which is verbose enough that agents tend to fall back to redeploying instead of validating in-place. Add `make run IMAGE=<ref> [CMD=...] [RUN_FLAGS=...]` plus the underlying `scripts/tests/deploy/local/exec/run.sh`. The script reuses `scripts/meta/env/all.sh` to resolve the host container name (same SPOT as `make exec`), forwards RUN_FLAGS verbatim, and only wraps CMD in `sh -lc` so default-entrypoint images and shell one-liners both work. Wire both iteration loops to mention the wrapper next to `make exec`: the Role Loop's Inspect block gets a bullet pointing at it, and the Playwright Spec Loop gains a short "Debugging in the nested docker daemon" section that also reminds the agent to mirror any successful hand-patch back into the role's playwright.env.j2. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Test Utilities 🧪
This directory holds the operational side of testing in Infinito.Nexus.
These assets are meant to support confidence, not ceremony. They help the project validate real-world behavior across local development, CI environments, and deployment-oriented smoke tests. The emphasis is on practical feedback: when something breaks, the surrounding test tooling should make the failure easier to understand, easier to reproduce, and easier to clean up. 🚀
Good changes in this area usually make the test experience more:
- repeatable
- diagnosable
- environment-aware
- safe to rerun
The ideal outcome is boring reliability: contributors should be able to trust that a test run says something meaningful about the system, not just about the machine that happened to execute it. ✅