Centralize timing constants

[natashaannn]

Centralize timing constants

Objective

Create one shared constants module for duplicated Remotion timing values.

---

Why this matters

Timing constants currently exist in multiple files.

Even small drift can create subtle render bugs.

---

Parallelization metadata

Track

remotion

Depends on

• none

Safe to run in parallel with

• pipeline issues
• caption extraction

Merge risk

• low/medium

---

Files in scope

Primary:

• remotion/lib/constants.ts

Likely touch:

• timing-related overlay files
• hook-related files

---

Required implementation

1. Move duplicated constants

Examples:

• hook tail pad constants
• bridge constants
• declick frames
• fps constants if duplicated

2. Replace local declarations

Consumers should import from shared constants.

---

Constraints

• preserve numeric values exactly

---

Handoff contract

Future Remotion refactors should treat this as canonical timing constants.

---

Acceptance criteria

Functional

• no render behavior changes

Regression checks

• duplicate timing constant declarations removed

---

Verification commands

grep -r "HOOK_TAIL_PAD" remotion/

Expected result:

• only shared constants module defines it

---

Explicitly out of scope

• hook timing logic changes

---

Suggested branch

refactor/s6-remotion-constants

Suggested commit slug

phase-5-step-3-remotion-constants