Repository navigation
Description
Parent
Refs: #12750. Epic: #12646. Source: PLAN Phase 10, topic planning-chain-consolidation.
Depends on
None.
Outcome
No view-lane instruction tells a skill to read a retired rendered-views file as a settings layer. lib/rendered-view.md's "Other lanes" step (and its synced plugins/*/reference/rendered-view.md copies) points at the shared medium resolver instead of listing ~/.claude/rendered-views.md, .claude/rendered-views.md and .claude/rendered-views.local.md as a "cascade surface" to read. What stays are the lines that name a retired file only as a test fixture or to test or describe AC14's retired-file notice.
Demo: git grep -nE "rendered-views(\.local)?\.md" -- lib plugins outside the exclusions below prints nothing.
The Brief (Problem, Goal, Constraints) is in the epic body.
Decisions
- Q14 / AC4: medium resolves through ADR 0075 precedence; no retired rendered-views file is read as a settings layer.
- AC14 (owner, amended 2026-11-03): a view lane that finds a retired file reads it only to name its value and where to move it; its terminal or file value still keeps the view local. Tests and evals of that notice must name the retired file, so they stay.
- Q5-Q12: "surface" for a config file is a retired sense; the rewritten step names the resolver, not a surface.
Done when
- AC4 (carried from feat(rendered-views): one medium resolver with the publish trust walk and fallback chain #12649 via chore(vocabulary): retire rung, default ladder, overlay and the other clashing senses with a checker #12750):
git grep -nE "rendered-views(\.local)?\.md" -- lib pluginsprints only lines in: CHANGELOG files;lib/view-settings.mjs, its test and its synced copies; and files whose matching lines write a retired file as a fixture to prove it is not read as a layer, or test or describe the AC14 retired-file notice (today the view-lane evals in adhd, ai-briefing, architecture, codebase-health, overengineering and work-items,plugins/codebase-health/README.md, and the AC5 fixture inplugins/planning/tests/surface-registry.test.mjs). Each kept file's matching lines are read and confirmed to be one of those cases. -
lib/rendered-view.mdand every synced copy match (the repository's sync check passes), and each plugin whose copy changed carries its release record per AGENTS.md.
Out of scope
- The vocabulary checker and the other retired senses (sibling slices of chore(vocabulary): retire rung, default ladder, overlay and the other clashing senses with a checker #12750)
- Changing the resolver's behaviour or the AC14 notice text
Activity
github-actions commentedon Nov 4, 2026
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Medium
Complexity: Low
Uncertainty: Known
Flags: none
Blocked by: none
Understood: rewrite the "Other lanes" step in
lib/rendered-view.md(and its synced plugin copies) to point at the shared medium resolver instead of listing retired rendered-views files as a settings layer. Keep only fixture/AC14-notice mentions. Release records are needed for the changed plugins. The done-when is exact and no open questions remain. No duplicates found among open issues.Automated triage, applied by the lanes App.
github-actions commentedon Nov 4, 2026
github-actions commentedon Nov 4, 2026