mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-09 04:06:42 +00:00
kevinveenbirkenbachandClaude Opus 5.5
00340c6795
The comment rule allows parameter docs and nocheck directives only, so the five Exception comments this branch added go. What they explained: - cli/administration/roles/marker.py: O_NONBLOCK keeps a FIFO planted under the marker name from blocking the open; the fstat refuses it. - cli/administration/roles/source.py: a git hook exports GIT_DIR, GIT_INDEX_FILE and friends, which would point the scratch repository at the core checkout; the askpass helpers and the detached session keep a fetch that needs credentials from prompting. - roles/web-app-bluesky/files/login-broker/server.js: the account map lives in the broker's own volume, never in a Keycloak user attribute; a bluesky_* attribute write under LDAP federation in WRITABLE mode triggers a schema-violating sync push that breaks later OIDC logins. - roles/web-app-yourls/files/php/upgrade_database.php: YOURLS reports bootstrap and upgrade errors with die(), which exits 0; only the shutdown handler turns them into a failure. - scripts/tests/deploy/act/workflow.sh: act copies the checkout through .gitignore, which drops the pulled custom roles, so the job binds the checkout to keep them. Co-Authored-By: Claude Opus 5.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. ✅