Skip to content

Guard episode-runtime-shaping fix-routing with a regression test [#961]#1356

Open
minion1227 wants to merge 1 commit into
e35dev:mainfrom
minion1227:minion_961
Open

Guard episode-runtime-shaping fix-routing with a regression test [#961]#1356
minion1227 wants to merge 1 commit into
e35dev:mainfrom
minion1227:minion_961

Conversation

@minion1227

Copy link
Copy Markdown
Contributor

Closes #961.

What & why

prototype/episode-runtime-shaping.html already does the right thing: it treats
the runtime target as guidance, not a hard cap, and every tightening
opportunity it surfaces hands the edit off to the screen that owns that edit
rather than trying to make the cut in place. But none of that routing was
guarded by a test, so a future change could silently drop a hand-off link,
point an opportunity at the wrong screen, or turn the advisory target into an
export blocker — with nothing to catch it.

This adds a focused regression test for that behaviour. It is a test-only
change; no production code is modified.

What the test guards

prototype/episode-runtime-shaping-fix-routing.test.js asserts:

  1. Every opportunity is a navigable hand-off — each tightening opportunity
    renders a fix-link whose href is the opportunity's route, labelled
    Open <owner> →.
  2. No dead links — every route in the OPPORTUNITIES data resolves to a
    real prototype screen on disk.
  3. The four documented routes stay wired to their owning screens:
    Opportunity Routes to
    Long pauses in guest discussion pause-crosstalk-cleanup.html
    Segment runs longer than usual show-segment-system.html
    Intro could be shorter intro-outro-builder.html
    Repeated point near 34:00 transcript-search-navigation.html
  4. Runtime shaping stays advisory — the screen still states the episode can
    export at any length and the target does not block export.

Verification

The verification commands pass:

…dev#961]

episode-runtime-shaping already hands every tightening opportunity off to the
screen that owns that edit (long pauses -> pause & cross-talk cleanup, an
over-long segment -> show segment system, a long intro -> intro & outro builder,
a repeated point -> transcript search) instead of cutting in place, and the
target stays advisory so it never blocks export. None of that was guarded by a
test. Add a focused regression test that asserts each opportunity renders an
"Open <owner> →" link to a real fix screen, that the four documented routes stay
wired to their owning screens, and that runtime shaping never gates export.

Test-only change; no production code is modified.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Guard episode-runtime-shaping fix-routing with a regression test

1 participant