Severity: Low
`src-tauri/src/screenplay/document.rs` (~line 209) documents `SceneCard.scene_index` as "Matches scene position in the script (0-based index)". In a series project this is ambiguous: is it absolute across the whole series, or relative to the owning episode?
Currently each episode carries its own `scene_cards: Vec` and indices appear to be per-episode — but the PDF renderer's cross-lookups (see #4 in this batch) already collide with the absolute convention, which suggests frontend and backend may not agree.
Fix direction: pin down a single invariant, document it in the struct comment, and name accordingly (`episode_scene_index` or `absolute_scene_index`).
Why it matters: Hidden source of future bugs as features touch this field; explicit naming prevents a class of series regressions.
Severity: Low
`src-tauri/src/screenplay/document.rs` (~line 209) documents `SceneCard.scene_index` as "Matches scene position in the script (0-based index)". In a series project this is ambiguous: is it absolute across the whole series, or relative to the owning episode?
Currently each episode carries its own `scene_cards: Vec` and indices appear to be per-episode — but the PDF renderer's cross-lookups (see #4 in this batch) already collide with the absolute convention, which suggests frontend and backend may not agree.
Fix direction: pin down a single invariant, document it in the struct comment, and name accordingly (`episode_scene_index` or `absolute_scene_index`).
Why it matters: Hidden source of future bugs as features touch this field; explicit naming prevents a class of series regressions.