Repository navigation
chore(rendered-views): retire rung, default ladder, tier for precedence and surface for a config file #13184
Description
Parent
Refs: #12750. Epic: #12646. Source: PLAN Phase 10, topic planning-chain-consolidation.
Depends on
Outcome
The rendered-views vocabulary names each thing once: the view form choice (text, diagram, page, video) is a form, not a rung; the medium order is the fallback chain, not a default ladder or its rungs; precedence between settings is by scope, not tier; a settings file is named as that file or setting, not a surface. View tiers, the interview surface and the other allowlisted senses keep their names.
Demo: check-vocabulary --sense rung --sense default-ladder --sense tier-precedence --sense surface-config docs/contracts/rendered-views docs/conventions/rendered-views plugins/visualization exits 0.
The Brief (Problem, Goal, Constraints) is in the epic body.
Decisions
- Q5-Q12: rung (form vs medium) retired: form, or medium / fallback chain step; default ladder now fallback chain; tier for precedence now scope (ADR 0075); surface for a config file retired. The epic's Problem names the clashes: contract rung :328 vs :806, tier :37 vs :822, surface :802 (line numbers as of the epic).
- D8: allowlisted senses stay (the checker slice's data file).
Done when
- AC3 for these senses: the Demo command exits 0.
- Each section heading renamed in
docs/contracts/rendered-views/README.md(for example "Choosing the rung", "Default ladder and its reconciliation") has every in-repo link and anchor to it updated:git grep -nfor the old anchor slug prints only CHANGELOG lines. - Evals whose case names or graders use the retired word (for example visualization's
viz-comparison-tablenames-rungsample) are renamed or reworded with the skill text they grade; the plugin's evals validate with no FAIL; no model evals are run. - The contract's CHANGELOG and each touched plugin's release record follow AGENTS.md.
Out of scope
lib/rendered-view.mdand its synced copies (the AC4 slice of chore(vocabulary): retire rung, default ladder, overlay and the other clashing senses with a checker #12750)- overlay, contract-for-the-Brief (sibling slices)
- Renaming View tiers, the interview surface, the education explanation rung or any other allowlisted sense
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: #13178
Understood: a vocabulary cleanup across the rendered-views contract, conventions and visualization plugin. "Rung" becomes form or fallback-chain step. "Default ladder" becomes fallback chain. "Tier" used for precedence becomes scope. "Surface" used for a config file is retired. The work includes updating anchors, evals and release records. The outcome and done-when are exact, and the decisions are recorded in the issue, so nothing is missing. It depends on #13178. No duplicates found.
Automated triage, applied by the lanes App.
melodic-automation-lanes commentedon Nov 4, 2026
Not admitted to the issue lane yet: blocker #13178 is not closed by a listed human or a merge.
github-actions commentedon Nov 4, 2026
melodic-automation-lanes commentedon Nov 4, 2026
The work-resolve-issue lane stopped on this issue (
outcome-unread): the run wrote no readable outcome file: it crashed or was cut off, which says nothing about the issue.It keeps
agent-ready, and work-unblock starts it again (retry 1 of 2).In the run's words:
Partial work is on the branch
work-resolve-issue/issue-13184-41848351261-1. The next run continues from it while it is not behind the default branch, and otherwise starts fresh.Run: https://github.com/melodic-software/claude-code-plugins/actions/runs/41848351261
github-actions commentedon Nov 4, 2026
github-actions commentedon Nov 4, 2026
melodic-automation-lanes commentedon Nov 4, 2026
This run started fresh from the default branch instead of resuming
work-resolve-issue/issue-13184-41848351261-1, which is behind it. That branch keeps the earlier run's commits until the next run on this issue deletes it, when no pull request uses it.