mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-09 12:17:13 +00:00
kevinveenbirkenbachandClaude Opus 4.7
1042523a45
Three iteration-rule sharpenings, all surfaced by repeated foot-guns in the web-app-zammad role-build loop: - Promote "validate the fix in-container before redeploying" from SHOULD to MUST. Adds an explicit reproducible-there carve-out (container crashes at startup, misconfigured env var, image-side bug, in-container script failure) so the rule is unambiguous on when it applies; the only exception is failures that genuinely depend on multi-container or post-deploy Ansible state. - Playwright-specific addendum: when the failing unit is a Playwright spec, "in-container validation" means running `make compose-playwright role=<role>` against the live stack — not just `curl` against the underlying API. The spec runs in a browser context with env loading, locator strategies, and cookie state that `curl` does not exercise. - New "Full-matrix iteration flow" subsection under "Matrix variants" documenting the variant-pinned `mode=update` → per-remaining-variant `mode=reinstall full_cycle=true` → final unpinned full-matrix `mode=reinstall full_cycle=true` recipe. Closes the gap where the existing "Matrix variants" rules only described focused single-variant debug and full-matrix initiation, but not the cycle that keeps full cross-variant coverage as the iteration target. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>