Skip to content

chore(shared-copies): ship the medium resolver and one rendered-view reference to every view lane #12667

Closed

Description

@kyle-sexton

Parent

Source: PLAN Phase 8, topic planning-chain-consolidation. Epic: #12646.

Depends on

Outcome

Every view-lane plugin carries the resolver, registry, cascade and yaml-subset copies, and planning, architecture, discovery and debugging share one synced rendered-view reference.

Demo: The shared-copies check passes and each new copy imports.

The Brief (Problem, Goal, Constraints) is in the epic body.

Decisions

  • Q52: AC15 covers every view lane, planning chain first.

Key interfaces

Module layout

Module Owns Public contract Consumers
View settings medium resolution, publish trust filter, retired-file notices C1 resolveMedium every view lane
Medium registry medium entries, fallback chain order, reachability probes, publish gate call C2 MediumEntry view settings, renderer
View renderer view kinds (plan, brainstorm, design), templates, redraw binding, shared chrome C2 render, C5 every view lane
Surface registry interview surfaces (terminal, page, shared session) C2 SurfaceEntry, resolveSurface planning:interview
Page input lock and comment events, missed-input sweep C4 review pages, interview pages

Dependency direction: skills -> view settings and renderer -> registries -> external providers (Artifact service, hosted publisher, tunnel), each contained in one registry entry. Registries never call skills. Each shared module has one canonical copy synced into each plugin (ADR 0019).

Conventions followed

  • docs/adr/0075 (config cascade) via lib/config-cascade.mjs; docs/adr/0019 (shared copies, scripts/shared-copies.txt, sync-shared-copies.sh); docs/contracts/rendered-views/README.md:813-816 (publish trust); lib/view-runtime.js (hash-pinned runtime, copy binding); lib/session-bridge (loopback page events); docs/standards/design-for-change.md:26 (add a variant by addition); plugins/visualization/reference/html-chrome.html (chrome tokens, accessibility floor).
  • Net new: the three registries and the lane registration (no existing pattern holds a variant set for views); the redraw binding (none exists in lib/view-runtime.js); the PageInput shape outside the shared session; a design view kind in the builder.
  • Challenges a pattern: per-skill medium lists in ~20 skills and four unsynced rendered-view.md copies (single source of truth); lib/publish-gate.mjs trustedMedium and review's digest-policy.mjs resolveMedium as two resolvers with different rules; the 1:1 interview page's own settings chain (.claude/interview-surface.json) outside ADR 0075; docs/contracts/config-cascade/README.md:659 marking rendered-views "conforms".

Done when

  • AC4 / AC15 (enabling): the shared-copies script passes --check and --check-bump; for each new carrier the view-settings copy imports.

Out of scope

  • Changing any skill's behaviour (per-plugin slices)

Activity

  1. added
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Nov 3, 2026
  2. added theissue type on Nov 3, 2026
  3. melodic-automation-lanes commented on Nov 3, 2026

    @melodic-automation-lanes
    Contributor

    This records a re-fire of an earlier refusal, not a new refusal. The lanes kill switch stopped run 41576258964, the work-resolve-issue run that agent-ready started, before it did any work; that run ended at 2026-11-03T04:37:16Z. work-unblock has now removed and added agent-ready back to start a fresh run. A kill-switch refusal is no fault in this issue or the lanes, so it never counts against later re-fires; after limits.limit-stops-per-issue of them since a person last added agent-ready or a run last reported, work-unblock waits longer before each one, up to 24 hours.

  4. added
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    and removed
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Nov 3, 2026
  5. self-assigned this
    on Nov 3, 2026
  6. github-actions commented on Nov 3, 2026

    @github-actions
    Contributor
    No description provided.
  7. melodic-automation-lanes commented on Nov 3, 2026

    @melodic-automation-lanes
    Contributor

    This records a re-fire of an earlier refusal, not a new refusal. The lanes kill switch stopped run 41581255310, the work-resolve-issue run that agent-ready started, before it did any work; that run ended at 2026-11-03T05:40:38Z. work-unblock has now removed and added agent-ready back to start a fresh run. A kill-switch refusal is no fault in this issue or the lanes, so it never counts against later re-fires; after limits.limit-stops-per-issue of them since a person last added agent-ready or a run last reported, work-unblock waits longer before each one, up to 24 hours.

  8. added
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    and removed
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Nov 3, 2026
  9. github-actions commented on Nov 3, 2026

    @github-actions
    Contributor
    No description provided.
  10. 21 remaining items

  11. kyle-sexton commented on Nov 3, 2026

    @kyle-sexton
    MemberAuthor

    Closing: delivered across three PRs, each linked with Refs: #12667 (split so each review pass could read its diff whole; see #12965 for why pr-verify could not pass the last part).

    Done-when, "AC4 / AC15 (enabling): the shared-copies script passes --check and --check-bump; for each new carrier the view-settings copy imports":

    Part PR Carriers given the resolver copies
    lib changes, every lane registered, existing carriers re-synced, and a test that runs every registered view-settings.mjs copy #12917 adhd, ai-briefing
    every rendered-view.md copy synced from lib/rendered-view.md #12937 architecture, debugging
    the rest #12792 codebase-health, discovery, education, overengineering, prototype

    The per-plugin migrations this unblocks are #12668-#12741.

  12. added 2 commits that reference this issue on Nov 3, 2026
    b46db19
    25f2ba1
  13. removed
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Nov 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Fields

No fields configured for Task.

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions