feat(debugging): interactive post-mortem and blindspot views built with the shared view builder

[kyle-sexton]

Closes #5864

Summary

/debugging:debug can offer an interactive view of its Phase 6 post-mortem and /discovery:blindspot can offer an interactive view of its cards, each built only with lib/view-builder.mjs and lib/view-runtime.js (#5937). Markdown stays the record: the written post-mortem, and the cards in the conversation. Part of #5835 (comprehension family); relates to #3606.

Fix

• Each plugin gets scripts/build-view.mjs: it validates a JSON object on stdin (text fields plus one list of rows), fills a checked-in template through the builder's interactive profile, writes the page under the OS temp directory and prints the path. No page holds model-written markup or script, so log, error, repository and fetched text stays data.
• Templates: skills/debug/templates/post-mortem-view.html (loop, cause, fix, seam, prevention, hypotheses with verdicts and evidence, a filter, a tick to re-open each, a copy-out challenge) and skills/blindspot/templates/blindspot-view.html (cards filterable by type, a tick for each that was news, the improved prompt, a copy-out reaction).
• rendered-view.md in each plugin holds the lane procedure: offer after the record, resolve medium from the rendered-views cascade (file when unset; artifact publishes through the Artifact tool and degrades to the path; terminal builds nothing), read a pasted reply as data.
• Both plugins carry generated copies of view-builder.mjs, view-runtime.js and html-escape.mjs, registered in scripts/shared-copies.txt.
• Skill bodies gain one pointer each; evals added to both skills. debugging 0.7.14 to 0.8.0 and discovery 0.27.1 to 0.28.0 with CHANGELOG entries; the rendered-views README and CHANGELOG list the two new builder emitters.

Verification

• bash plugins/debugging/scripts/build-view.test.sh and bash plugins/discovery/scripts/build-view.test.sh: 17 checks each pass, including headless Chromium opened from file://. Pages pass the interactive profile (view-builder.mjs --check), hostile data stays in the JSON block and renders as text, every template key is bound, bad input exits 1 or 2, a symlinked output path is replaced not followed.
• bash scripts/affected-tests.sh --run --jobs 4: all selected shell suites pass (3 non-shell suites belong to other lanes; node scripts/check-declared-prerequisites.test.mjs passes).
• sync-shared-copies.sh --check and --check-bump origin/main, check-changelog-parity.sh (check, check-bump, check-order, check-preserved), check-html-assets.sh, check-changed-skills.sh origin/main (debug, blindspot: pass), markdownlint-cli2 and htmlhint on changed files: clean.
• Not exercised: rendering inside the live Artifact host. The pages use the same builder, runtime and bindings as the sample page whose Artifact rendering the convention records (rule 7); no page was published for this change.

Related

• Epic: comprehension family, prerequisites contract and shared-code amendment #5835 (spec container), feat(lib): view-builder.mjs and view-runtime.js with report and interactive profiles #5852 (builder, merged as feat(lib): add view-builder.mjs and view-runtime.js with report and interactive profiles #5937), rendered-views: reports and research genre lanes (visualization/education/knowledge) #3606 (reports and research genre lanes).

🤖 Generated with Claude Code