fix(cockpit-e2e-wiring): accept matrix python entry as uv-sync evidence

The wiring spec previously required a literal `working-directory:
cockpit/<cap>/python` step in ci.yml. After the matrix migration in
this PR, that path moves into the matrix entry (`python: cockpit/...`)
and the working-directory is templated as `${{ matrix.cap.python }}`.

Spec now accepts either form, so matrix-templated jobs and any
remaining literal-step jobs both pass the cross-check.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: blove

apps/cockpit/cockpit-e2e-wiring.spec.ts

@@ -184,7 +184,13 @@ describe('cockpit e2e wiring', () => {
         if (!workflow.includes(wiring.project)) {
           errors.push(`${wiring.project}: ${workflowPath} does not run the e2e target`);
         }
-        if (!workflow.includes(`working-directory: ${wiring.langgraphCwd}`)) {
+        // Matrix-migrated jobs (cockpit-e2e) template the working-directory via
+        // `${{ matrix.cap.python }}`; the python path appears in the matrix
+        // entry (e.g. `python: cockpit/chat/foo/python`) instead. Accept either
+        // form so matrix and non-matrix jobs both pass.
+        const literalUvSync = workflow.includes(`working-directory: ${wiring.langgraphCwd}`);
+        const matrixEntry = workflow.includes(`python: ${wiring.langgraphCwd}`);
+        if (!literalUvSync && !matrixEntry) {
           errors.push(`${wiring.project}: ${workflowPath} does not pre-sync ${wiring.langgraphCwd}`);
         }
       }