mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-10 04:36:40 +00:00
kevinveenbirkenbachandClaude Opus 4.8
cb52a72f2e
The drill entry gate treated 'deploys no swarm service' as 'has nothing to restore', but the backup chain operates on NFS volumes and deployed backup units, not on scheduler objects; bigbluebutton's seven NFS-backed volumes went entirely unproven. Gate the drill solely on the NFS-flagged volume and make only the full-disaster step workload-aware: stack roles keep docker stack rm, node-local roles get their compose project (label com.docker.compose.project=<entity>, the compose handler's --project convention) stopped on every node so no writer races the export wipe and restore. Declare workload: node-local on bigbluebutton so the phantom-service converge/chaos gates skip while play, e2e and now the drill keep running; svc-runner stays skipped via its missing NFS volume. Document the nine drill steps host-by-host in the README. Co-Authored-By: Claude Opus 4.8 <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. ✅