Jump to current time in the Schedule timeline (scroll-to-now + shareable time links)

[chiptus]

This was generated by AI during triage.

Context

Captured from stale PR #23 ("Jump to current day in schedule view") so the feature intent isn't lost. That PR can't be merged as-is (see below).

Goal

Let a viewer jump the Schedule timeline to the current festival time, and share links to a specific time view. Desired behavior (from PR #23):

• A "Jump to Now" control that scrolls the timeline to the current time.
• A jumpToTime URL param (e.g. YYYY-MM-DDTHH:mm) for deep-linking / sharing a specific time; the timeline smooth-scrolls to it on load.
• The quick-nav buttons (Morning / Afternoon / Evening) drive the same URL-based time jump.

Why PR #23 can't just be merged

PR #23 (Nov 2025, 1 commit, never updated) was written against the pre-rework timeline. Since then the timeline moved to festival timezone (#75 / #76) and gained schedule reveal levels (#46), and #47 further reworks the Schedule tab. So "current time" and the morning/afternoon/evening buckets must now compute in festival time, and this feature only makes sense at the full reveal level (times are hidden below it). The scroll + URL logic needs rebuilding on the current timeline, not rebasing.

Open questions (triage / grill before agent-ready)

• Reveal levels: hide the "Jump to Now" control below full (where times don't exist)?
• Confirm "now" and the time-of-day buckets compute in festival time (per Festival timezone: schema, admin config, and Schedule list view in festival time #75).
• How does jumpToTime coexist with the existing day / time / view timeline search params (see Fix schedule route search-schema mismatch dropping timeline params #81)?

References

• Stale PR: Jump to current day in schedule view #23
• Related current work: Multi-mode Schedule tab UX for days/stages reveal levels #47 (schedule rework), Festival timezone: schema, admin config, and Schedule list view in festival time #75 / Horizontal timeline Schedule view in festival time #76 (festival timezone), Fix schedule route search-schema mismatch dropping timeline params #81 (schedule search params)

[chiptus]

This was generated by AI during triage.

Triage: enhancement + ready-for-human

Grilled during triage. The ephemeral scroll behavior is fully settled, but the sharing / URL-capture behavior — which is the core value of this ticket — needs a human to prototype a few options and judge. That keeps it out of AFK-agent scope.

Settled decisions (locked)

• "Jump to Now" scrolls the timeline to the current festival-local time (reuses the existing getFestivalHour / festival.timezone path). It is an ephemeral action.
• Edge case: when "now" is before the festival starts or after it ends, scroll to the first/last slot (or disable the control with a tooltip).
• Filters stay orthogonal to scroll. A jump never changes day / time / stages, so it can't land on a slot the active filter has hidden. The Morning / Afternoon / Evening controls remain filter buckets, not scroll navigation (this supersedes PR Jump to current day in schedule view #23's idea of repurposing them).
• Reveal levels: the control lives inside the timeline, which already renders the not-revealed placeholder below the full reveal level — so "Jump to Now" is automatically absent below full. No extra gating needed.
• MVP is consume-only for any deep-link param: support scrolling to it on load; do not build a separate "generate link" UI unless the prototype (below) calls for it.

Open — for the implementer to prototype and decide

How does sharing / URL capture work? The tension: if "Jump to Now" is purely ephemeral, copying the current URL reproduces filters but not the scroll position, so a recipient sees a different view. But if the button writes jumpToTime=<time> into the URL, a shared/bookmarked link freezes to a stale timestamp and re-scrolls there on every load. Neither is clearly right. Candidate approaches to prototype:

1. Ephemeral button, no URL capture (loses shared scroll).
2. Button writes jumpToTime=<festival-local time> (shareable but frozen).
3. Scroll-spy — jumpToTime continuously reflects whatever time is currently in view, so copying the URL always captures the current scroll position and "Jump to Now" is just a scroll the URL naturally picks up.
4. A separate "copy link to this moment" affordance, distinct from the ephemeral jump.

Pick after prototyping. If a jumpToTime param lands, format YYYY-MM-DDTHH:mm in festival-local time, slotted into timelineSearchSchema via useTimelineUrlState.

Sequencing

Build on the reworked timeline — after #47 (schedule rework) lands and #81 (schedule route search-schema mismatch) is fixed. The scroll + URL logic should be rebuilt on the current timeline, not rebased from the stale PR #23.

Why ready-for-human, not ready-for-agent

The ticket's headline feature (shareable time links, per PR #23) depends on a UX judgment — prototyping and choosing among the four approaches above — that an AFK agent can't make against a fixed brief. The ephemeral-scroll half alone is agent-shaped, but it isn't the point of the ticket on its own.

---

Generated by Claude Code