chore(cockpit): retire the c-debug "no aimock e2e" cross-references

Two files pointed at the c-debug README as the marker for a cap that
deliberately ships without an aimock suite. That is no longer true.

`scripts/rerecord-all-aimock.sh` is the load-bearing one: it discovers caps
by walking `*/e2e/fixtures/*.json`, so c-debug is picked up automatically
now that it has a fixture, and an unlisted cap defaults to the prompt
"Hello". Re-recording would have quietly replaced the fixture with one whose
user message no cap spec sends. Register c-debug's actual prompt.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Author: blove

cockpit/render/README.md

@@ -17,4 +17,4 @@ Existing coverage:
 
 If a render-specific e2e harness is desired in the future (visual diffs, interactive scrubbing), it would be a separate cycle. The aimock pattern from cockpit-chat / cockpit-langgraph caps does not fit.
 
-This file is the deliberate "no e2e" marker matching the c-debug README (`cockpit/chat/debug/angular/e2e/README.md`).
+This file is the deliberate "no e2e" marker for the render caps. It is the only one left: `c-debug` carried the same marker until it gained a real aimock suite at `cockpit/chat/debug/angular/e2e/`.

scripts/rerecord-all-aimock.sh

@@ -42,11 +42,12 @@ declare -A CAP_PROMPTS=(
   ["c-subagents"]="Plan a trip from LAX to JFK"
   ["c-generative-ui"]="Show me a dashboard of airline operations.|Filter to only the cancelled flights."
   ["c-a2ui"]="I want to fly LAX to JFK|I want to fly SFO to SEA"
+  ["c-debug"]="What is a jet bridge?"
   ["streaming"]="Tell me one quick fact about Angular signals in two sentences."
 )
 
 # Discover aimock-eligible caps by walking fixture files. Excludes
-# documented-N/A caps (render, ag-ui, c-debug) which have no fixtures.
+# documented-N/A caps (render, ag-ui) which have no fixtures.
 CAPS=()
 while IFS= read -r f; do
   cap_id=$(basename "$f" .json)