Agenda timeline and time marker

Purpose and usage

Translate time into a shared spatial layout while keeping the current day and overlapping commitments readable.

Use for daily planning and schedule visualization, not a generic sortable list.

Anatomy

Variants and configuration

State coverage

Interaction and responsive behavior

• Reuse the exported timeline constants so pointer math matches the display.
• Start/end are fractional hours in UI models; server action data uses minutes.
• The placement algorithm checks interval segments and rejects more than two overlapping blocks.
• Do not infer project task persistence from visual completion within a local block.

Accessibility contract

• Time must remain available as text, not only position.
• A pointer-driven block manipulation needs an equivalent nonpointer path.
• The source has polite announcements for changes, but a complete keyboard move/resize model is not established.

Known gaps and readiness

Error/loading/retry patterns are not fully standardized. End-to-end backend scheduling validation and nonpointer parity are outside the isolated capture verification.

Composition example

const top = (start - DEFAULT_AGENDA_START_HOUR)
  * DEFAULT_AGENDA_HOUR_HEIGHT;
const height = (end - start)
  * DEFAULT_AGENDA_HOUR_HEIGHT;

Source references