Description
The matrix deploy scripts rely on the mutable current kubeconfig context. A stale current context blocks the run, and parallel cluster creation can silently route calls to a different permutation.
Acceptance Criteria
- #1 Every matrix kubectl and Helm call targets the cluster owned by that permutation explicitly.
- #2 Static lab checks and a bounded real matrix run preserve failed, empty and partial outcomes and retain residency evidence.
Definition of Done
- #1 just check (fmt-check, lint, gen-check, env-check, docs-check, test, race, hygiene, ui-check, compose-check, helm-test, lab-check, signal-fidelity)
- #2 just gen (only if a blueprint field, construct/workload config struct, or a skill under plugins/synthkit/skills/ changed)
- #3 just dump — inventory diffed against signals/
Final Summary
Integrated in 4dbe491. Matrix commands carry explicit owned-cluster contexts; readonly child environments, nested-module invocation and relative output paths were corrected. Five permutations captured successfully after the failed first attempt. Both nodes per permutation passed image residency after first import on execution base7cbafe0 plus harness patch cda6bda011c23aa52c9dbab132894cac3c46dd01e5d8b6ccb6f62e745be12ecb. Ten clusters created/deleted across attempts, zero retained. Static checks, matrix package checks, second CodeRabbit batch with zero findings and full integrated gate passed.