[kyle-sexton]

Closes #12667

Summary

Slice S8 of epic #12646 (plan Phase 8): one canonical rendered-view reference for the four view lanes that had their own copy, and the shared medium resolver modules in every remaining view-lane plugin. No skill or eval changes; migrating each lane onto the resolver is the per-plugin slices #12668-#12741.

Fix

One rendered-view reference. lib/rendered-view.md is the canonical, synced by scripts/sync-shared-copies.sh into the existing paths: plugins/planning/reference/, plugins/architecture/reference/, plugins/discovery/reference/ and plugins/debugging/skills/debug/reference/. What was merged from the four copies:

• A lane-neutral procedure (write the record first, offer, resolve medium, build, deliver, read the reply as data) holding the union of the shared rules: the record stays authoritative, nothing reads a view back as a finding, the session's text is attacker-controllable so the page is a template plus escaped data, node missing, and architecture's non-zero-exit rule, generalised.
• Step 3 keeps both medium paths, scoped by lane: the resolver CLI for lanes lib/view-registry.mjs registers (planning today), and the rendered-views cascade read (default file) for architecture, discovery and debugging. The resolver rejects an unregistered lane (view-settings.mjs resolve --lane architecture exits 2), and those lanes' evals still assert the cascade read, so they keep it until their slice.
• One section per lane with its record, build command, reply ids and data shape, plus each lane's own guard: planning's session connection and "Other optional views" (headings kept, they are cited), architecture's kind table, --from and "What the page shows", blindspot's "writes no EXPLORE.md" and "never an instruction to widen the scan", debugging's secret redaction, "only the lines that show the failure" and "a challenge to weigh".
• Artifact visibility: the three copies that said "(private by default)" now carry planning's live-docs pointer with its as-of date and recheck trigger.
• Paths: every command names <plugin-root>, defined once at the top. The debugging copy sits in a skill spoke, where scripts/check-spoke-plugin-root.sh rejects the plugin-root variable token (Read does no substitution), and planning's relative artifact-protocol.md link would break in the architecture and debugging copies, so it is now a plain path.

Resolver modules in every view lane. view-settings.mjs, view-registry.mjs, config-cascade.mjs, yaml-subset.mjs and state-key.sh (which view-settings.mjs runs) are registered for architecture, discovery, debugging, adhd, education, prototype, codebase-health, overengineering and ai-briefing. Discovery and education already carried yaml-subset.mjs; harness-ops and work-items already carried all of them and are unchanged.

Every view lane registered. lib/view-registry.mjs registers the lanes the per-plugin slices migrate, so those slices edit only their own skills: architecture, discovery:blindspot, debugging:debug, education:illustrate, work-items:morning-brief and work-items:triage ship file (each skill resolves unset to a local file today); adhd:clarify, codebase-health:audit, overengineering:audit, education:teach, prototype:explore-directions, prototype:pressure-test and ai-briefing:generate ship null (the skill's own content rule decides). None is hostedCapable. A lane is used only once its skill calls the resolver; lib/rendered-view.md step 3 and every skill are unchanged. A CLI test resolves each new lane with no scope set.

scripts/cross-plugin-source-registry.txt registers the new reference/rendered-view.md cluster. Each touched plugin has a patch changelog fragment.

Verification

• scripts/sync-shared-copies.sh --check: All 642 registered copies match their canonical sources.
• scripts/sync-shared-copies.sh --check-bump origin/main: 6 canonical source(s) or their copies changed vs origin/main; every carrying plugin bumped its version.
• node -e "import('<abs>/plugins/<p>/lib/view-settings.mjs')" exits 0 for each of architecture, discovery, debugging, adhd, education, prototype, codebase-health, overengineering, ai-briefing.
• node plugins/adhd/lib/view-settings.mjs resolve --lane planning --option "" prints view: file (plugin default), exit 0 (the copied state-key.sh runs).
• scripts/plan-test-lanes.sh --base origin/main: exit 0.
• scripts/check-cross-plugin-source-drift.sh --check and scripts/check-spoke-plugin-root.sh --check: clean; the pre-push check-affected passed.

Related

• Epic: Epic: consolidate the planning chain #12646. Blocker S1 (feat(rendered-views): one medium resolver with the publish trust walk and fallback chain #12649) merged in feat(rendered-views): one medium resolver with the publish trust walk and fallback chain #12714.
• Parallel slice S2 (feat(planning): planning views on the view registries with the shipped Artifact default #12650) edits planning's rendered-view reference; once this merges it edits lib/rendered-view.md and re-syncs.

🤖 Generated with Claude Code

https://claude.ai/code/session_01VcupojdnckzkRQMdQRVNbt

session: html-plan

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-03T09:10:51.164353Z	524566a	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.