Skip to content

Carry layout-first placements into source media health [#1131] - #1337

Open
bohdansolovie wants to merge 1 commit into
e35dev:mainfrom
bohdansolovie:feat/source-media-health-layout-handoff
Open

Carry layout-first placements into source media health [#1131]#1337
bohdansolovie wants to merge 1 commit into
e35dev:mainfrom
bohdansolovie:feat/source-media-health-layout-handoff

Conversation

@bohdansolovie

@bohdansolovie bohdansolovie commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

Summary

Completes the #1131 placement workflow for the episode-flow entry screen (source-media-health.html), aligned with the connected preview shell (#581) and connected preview screens (#583):

  • speakersFromState in layout-handoff.js maps placed layout slots into source-media-health speaker rows (with carried recording sig for duplicate detection).
  • Source media health loads the shared handoff, seeds speakers from placements, shows a layout-start summary, flags duplicate recordings, and resets to the carried state instead of generic samples.
  • Layout-first episode detour: when opened with from=episode, Continue targets source media health (not the generic production workspace).
  • Preview app routing preserves layout-first handoff on source media health and the role-mapping ↔ source-media-health round trip.

Test plan

  • npm test — 106 smoke test files pass
  • prototype/source-media-health-layout-handoff.test.js — handoff seeding, duplicate recording gate, summary render
  • preview/layout-first-episode-continue.test.js — episode-origin Continue targets source media health
  • preview/layout-handoff.test.jsspeakersFromState unit coverage
  • preview/app-route-context.test.js — handoff preserved on source media health navigation

Refs #1131, #581, #583

Source media health is the episode-flow entry for layout-first placement; seed its speaker rows from carried videos, surface duplicate-recording conflicts, preserve handoff in preview routing, and return episode-origin layout-first Continue to this screen.
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.

1 participant