Skip to content

Follow linked stories and restore node focus from wrapper URLs #44

Closed

Description

@jdylanmc

Reconciled status (2026-09-27)

Inspected baseline: main@c8e22ec. Maintained intent: docs/product-spec.md.

Disposition: completed; closing this bounded delivery.

Completed: shared-source story links, wrapper-owned focus/from/fromFocus URLs, direct-open/reload restoration, and return navigation are implemented and retained in the current shell. The same-origin viewer receives restored focus without modifying the vendored renderer.

Remove the obsolete blocking relationship to #43: its prerequisite implementation is on main, and its remaining follow-up scope is not a prerequisite for this completed delivery.

Merged delivery evidence: #51, #65, #71. These merge commits are ancestors of the inspected main revision.

Current source and regression evidence:

Existing exact-main CI is successful. This reconciliation inspected current code, committed regression coverage and merged history; it does not claim a new test run, manual walkthrough, visual acceptance, cross-machine experiment, or approval of paused work.

Historical issue scope (preserved; current disposition and readiness are above)

Parent

#40 - Specification: Storybook-for-architecture whiteboard MVP.

Source revision: 2026-09-19T12:09:45Z; complete specification body SHA-256 1965e96d069d64a85cb7850abde9d91249874a7cf1bd2e0b38197262a86827de.

Requirements: CON-08, S-3, FR-03 inter-document index.

What to build

Let a reviewer select a node linked to another story, drill into that explanation, and return to the surrounding context using durable wrapper navigation. The wrapper URL must represent the selected focus and restore it when opened again. Use topo's document index and the same-origin wrapper/viewer boundary; keep the renderer copy untouched.

Acceptance criteria

  • AC-19: Selecting a node mapped to another document updates the wrapper URL, and loading that URL restores the same focus without modifying the vendored renderer.

  • Demonstrate overview-to-detail and return navigation across multiple actual rendered stories while retaining their code evidence.

  • Do not attempt the rejected components[].href schema extension or make an upstream navigation PR a prerequisite. Upstream overlap is an observation, not a replacement for the agreed wrapper-side contract.

Verification and readiness

  • Use Playwright against the actual same-origin wrapper and pinned rendered artifacts.

  • Assert the parent URL, cross-document destination, focus after reload/direct-link opening, and return to the surrounding story context rather than only inspecting an iframe URL.

  • Keep the vendored integrity gate passing.

Readiness: Fully specified; needs the story catalogue/index. No new navigation product decision is open.

Open product decisions: None for this scoped slice. Return newly discovered material scope decisions to the human.

Blocked by

A closed prerequisite alone is insufficient: its implementation must be available on this delivery's agreed base.

Boundaries

  • Scope is Specification: Storybook-for-architecture whiteboard MVP #40, not the broader historical Roadmap: deferred architecture and engineering-health capabilities #1 roadmap. Preserve existing scanner, explorer, curated views, and enrichment behavior.

  • No hosting, authentication, deployment, public npm publication, human sketch canvas, or mandatory model service.

  • No heuristic staleness or explanation-coverage gate. Structural/source validation does not prove semantic truth.

  • Use the existing unit/script/browser verification seams and keep the repository regression gates. No documentation gate is added.

  • The source snapshot for this breakdown has AC-14 already delivered by PR chore(lint): add correctness baseline #39. Begin implementation from a base containing that merged change.

  • Keep the preserved prototype unchanged. Do not silently edit the vendored renderer or substitute an unapproved upstream version.

  • The implementation owner chooses local code structure within the agreed contracts; return newly discovered material product choices to the human.

Delivery grouping

Intentionally separate coherent deliveries, one eventual PR per child; not one parent-wide implementation PR. No delivery is launched by publication.

No assignee or exclusive ownership is claimed. Publication does not authorize worker dispatch, implementation, merge, or parent closure.

Assembled acceptance

The complete parent acceptance remains all AC-01 through AC-19 over the assembled state. Independent child completion is not a claim that the full MVP is shipped. The final delivery owner verifies the complete local authoring, composition, linked navigation, and static bundle journey once all prerequisite changes are on the agreed base. Parent closure and merges remain human-owned.

Activity

  1. added a commit that references this issue on Sep 20, 2026
  2. jdylanmc commented on Sep 27, 2026

    @jdylanmc
    OwnerAuthor

    Backlog reconciliation (2026-09-27)

    Inspected baseline: main@c8e22ec. Maintained intent: docs/product-spec.md.

    Disposition: completed; closing this bounded delivery.

    Completed: shared-source story links, wrapper-owned focus/from/fromFocus URLs, direct-open/reload restoration, and return navigation are implemented and retained in the current shell. The same-origin viewer receives restored focus without modifying the vendored renderer.

    Remove the obsolete blocking relationship to #43: its prerequisite implementation is on main, and its remaining follow-up scope is not a prerequisite for this completed delivery.

    Merged delivery evidence: #51, #65, #71. These merge commits are ancestors of the inspected main revision.

    Current source and regression evidence:

    Existing exact-main CI is successful. This reconciliation inspected current code, committed regression coverage and merged history; it does not claim a new test run, manual walkthrough, visual acceptance, cross-machine experiment, or approval of paused work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions