feat(media): expose and rehydrate speed state from MediaEditor

[jlocala1]

Stacked on #342 — the first four commits are that PR; this adds five on top. Rebase/merge after #342 lands and the diff shrinks to it.

Speed markers and the default playback speed live only in MediaEditor component state today: hosts can't persist them, so they vanish on reload — and pulseclip's new server-side export render can't bake speed ramps it never receives (the one documented gap in mieweb/pulseclip#30).

• useTranscriptEdits: initialSpeedMarkers / initialDefaultSpeed options seed the state
• MediaEditor: same two props passed through, plus onSpeedStateChange(speedMarkers, defaultSpeed) — fires once on mount with the initial values and on every change, mirroring onEditedWordsRender
• Purely additive; existing callers unaffected

Consumer: pulseclip persists these in edits.json alongside the edit list and applies them in the export render (setpts/atempo).

Gates: lint ✅ typecheck ✅ format ✅ 400/400 tests ✅

[Copilot]

Pull request overview

Adds a persistence-friendly “speed state” surface area to MediaEditor/useTranscriptEdits so hosts can save/restore speed markers and default playback speed (and downstream consumers can bake speed ramps into export renders). This PR is stacked on #342, so it also contains the drag-selection improvements and their regression tests.

Changes:

• useTranscriptEdits: accepts initialSpeedMarkers / initialDefaultSpeed to seed speed state.
• MediaEditor: exposes the same initial props and emits onSpeedStateChange(speedMarkers, defaultSpeed) on mount and whenever speed state changes.
• Tests: adds coverage for speed-state rehydration and drag-selection behavior beyond pane bounds.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
src/hooks/useTranscriptEdits.ts	Adds options to initialize speed markers/default speed in the headless edit hook.
src/components/MediaEditor/MediaEditor.tsx	Plumbs initial speed props through and adds onSpeedStateChange; also includes stacked drag-selection changes.
src/components/MediaEditor/MediaEditor.test.tsx	Adds regression tests for speed rehydration callback and drag-selection tracking outside the pane.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (1)

src/hooks/useTranscriptEdits.ts:933

• setSpeedForRange always adds a marker at startIndex, even when the requested speed is already the effective speed at the start of the range (e.g. applying 1x when the default is 1). This creates redundant {wordIndex, speed: 1} markers that will be persisted/exported even though they don’t change playback.

      const kept = speedMarkers.filter(
        (m) => m.wordIndex < startIndex || m.wordIndex > endIndex
      );
      const next = [...kept, { wordIndex: startIndex, speed }];
      if (

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (1)

src/hooks/useTranscriptEdits.ts:917

• setSpeedForRange always calls pushUndo() and sets hasEdits=true even when applying a speed that is already effectively in place for the whole range and there are no markers to clear (e.g. applying 1x to a fresh transcript). In that no-op case the final speedMarkers stays the same, but you still create an undo step and mark the editor dirty, which can trigger unnecessary persistence/export updates.

    (startIndex: number, endIndex: number, speed: PlaybackSpeed) => {
      if (startIndex > endIndex) return;
      pushUndo();
      const afterIndex = endIndex + 1;
      const speedAfter = getSpeedAtIndex(

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.

Suppressed comments (1)

src/hooks/useTranscriptEdits.ts:939

• setSpeedForRange pushes an undo snapshot and sets hasEdits=true even when the operation is a true no-op (e.g., applying 1x to a region when the effective speed is already 1x and there are no markers to clear / no restore marker to add). This creates an extra undo step and incorrectly marks the editor as edited.

      pushUndo();
      const afterIndex = endIndex + 1;
      const speedAfter = getSpeedAtIndex(
        afterIndex,
        speedMarkers,

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.

Suppressed comments (1)

src/hooks/useTranscriptEdits.ts:479

• Speed rehydration now sets hasEdits=true (needed), but it also means onChange can fire on the first render when only speed state was rehydrated (e.g. initialSpeedMarkers provided but initialEditedWords undefined). That can cause hosts to persist a baseline editedWords/undoStack payload on mount even though there was no in-session mutation. Consider treating any provided initial saved state (words/undo/speed) as “initialized from saved” and skipping the first onChange notification in that case (not just when initialEditedWords is present).

    // Speed markers index into the old transcript's word list; keeping them
    // would apply stale rates to arbitrary words of the new transcript
    setSpeedMarkers([]);
    setDefaultSpeed(1);
    setSpeedUndoStack([]);
    initializedFromSaved.current = false;

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.

Suppressed comments (1)

src/components/MediaEditor/MediaEditor.tsx:218

• New Tailwind utility classes were added for the sped-region underline (decoration-warning, decoration-dotted, decoration-2, underline-offset-4). For Tailwind CSS 3 consumers that don’t scan node_modules, these need to be added to miewebUISafelist (see src/tailwind-preset.ts’s safelist contract) or the underline styling won’t be emitted in consumer builds.

  // A dotted warning underline spans every word of a re-timed region, so the
  // affected range reads at a glance (the badge only sits on the first word)
  if (s.isSped) {
    parts.push(
      'underline decoration-warning decoration-dotted decoration-2 underline-offset-4'
    );

[garrity-miepub]

Reviewed the hook and editor changes closely. The speed undo stack riding alongside the word undo stack is a clean design, and re-anchoring markers through silence-threshold rebuilds was a great catch. All Copilot findings addressed with regression tests.

Verified locally against latest main: typecheck, lint, format, and 415/415 tests green. Also tested the range-speed flow hands-on in Storybook — drag select, apply 2x, auto-restore marker after the range, single-step undo all work as described.

Approving! 🚀