mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-08 03:38:23 +00:00
kevinveenbirkenbachandClaude Opus 5
aa09a3707b
The local exec helpers covered the development container and a throwaway sidecar next to it, but nothing reached into an application the stack had already deployed. Swarm had swarm-app-exec for that; compose had no counterpart, so the only remaining route was a nested docker exec, which the contributor rules forbid. The helper goes through container.sh's positional form rather than its cmd environment variable. container.sh runs that variable through `sh -lc`, so an already-composed command would be split a second time; passing argv through untouched leaves exactly one shell level, inside the target container. Co-Authored-By: Claude Opus 5 (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. ✅