Track router prompt and update release workflow contract test

Author: goodguy1963

.github/prompts/cockpit-scheduler-router.prompt.md

@@ -0,0 +1,36 @@
+---
+description: "Dispatcher prompt for routing Cockpit Todo cards with the compact routing MCP tool."
+---
+
+[AGENT]
+Task Source:
+- Cockpit Todo ID: [COCKPIT_TODO_ID]
+- Title: [COCKPIT_TITLE]
+- Description: [SYNTHESIZED_FINAL_PLAN]
+
+Execution Goal:
+- Inspect Cockpit cards, not external tracker tasks.
+- Use `cockpit_list_routing_cards` first, then `cockpit_get_todo` only for matching cards.
+- Use `needs_review_mode=plan-only`.
+- Apply mutations deterministically.
+- Prefer the latest actionable user comment for intent and cron overrides.
+- Use flags for single review-state handoff and labels for multi-value topic or routing tags.
+- When the card references a scheduled task, verify task lifecycle with scheduler MCP tools instead of inferring it from comments alone.
+- Prefer `cockpit_closeout_todo` for final execution handoff so comment, review-state update, section fallback, and stale task-link cleanup stay atomic.
+
+Required Output:
+- What was changed
+- Files touched
+- Validation performed
+- Remaining risks or follow-ups
+
+Completion Update:
+- Add a Cockpit comment summarizing the result.
+- Update flags, labels, linked `taskId`, and section to match the final outcome.
+- If the linked scheduler task was removed or no longer exists, clear the stale `taskId`.
+
+Notes:
+- Treat canonical workflow flags as the routing state. Use labels for categorization and treat comment labels as context only.
+- Ignore `Scheduled as ...`, `Done`, label-maintenance notes, dispatcher status comments, and scheduler status comments.
+- Prefer existing review-state flags such as `needs-user-review` or `FINAL-USER-CHECK` over inventing new label-only review markers.
+- Return only the compact execution summary requested by the dispatcher.

.gitignore

@@ -40,3 +40,6 @@ FULL_SPECIFICATION.md
 .vscode/cockpit-prompt-backups/
 .vscode/scheduler-history
 analysis_tools/
+
+!.github/prompts/
+!.github/prompts/**

.vscodeignore

@@ -25,6 +25,8 @@ AGENTS.md
 !.github/
 !.github/agents/
 !.github/agents/**
+!.github/prompts/
+!.github/prompts/**
 !.github/skills/
 !.github/skills/**
 

src/test/suite/releaseUtils.test.ts

@@ -177,7 +177,8 @@ suite("Release Pipeline Contract Tests", () => {
     assert.ok(workflow.includes("uses: actions/cache@v4"));
     assert.ok(workflow.includes("path: .vscode-test"));
     assert.ok(workflow.includes("run: npm run pretest"));
-    assert.ok(workflow.includes("run: npm test"));
+    assert.ok(workflow.includes("Ensure Xvfb is available"));
+    assert.ok(workflow.includes('run: xvfb-run -a --server-args="-screen 0 1280x1024x24" npm test'));
     assert.ok(workflow.includes("RELEASE_TAG=edge"));
     assert.ok(workflow.includes("node ./scripts/release-notes.js CHANGELOG.md release-notes.md"));
     assert.ok(workflow.includes('gh release view "${RELEASE_TAG}" >/dev/null 2>&1'));