[ReinaldoAssis]

Why

The Time module only had one-off blocks. This adds a default week that keeps the planner filled: paint the routine once and the app creates the concrete blocks for the next 8 weeks, updating them when the routine changes.

Model

• RoutineState = { revision, blocks[] } in the snapshot; a block is { weekday, startMinutes, durationMinutes, categoryId, title } (no dates).
• Stored as a shared_settings singleton (routine), so it syncs LWW with lifeForce, finance and dailyGoal.
• Generated blocks carry routineId + routineRevision and use deterministic ids (routine-<id>-<date>), so two devices do not duplicate them.

Rules

• Horizon: 8 weeks, refilled on boot and after sync.
• Today only gets slots that have not started yet; past/in-progress blocks are untouched.
• Manual blocks win: the routine skips any date/time already occupied.
• Editing or deleting a generated block is a one-off exception; the routine only changes through the editor.
• Saving a new routine bumps the revision, removes future generated blocks (cancelled exceptions stay as tombstones) and recreates the horizon. Historical blocks stay.
• Free for everyone on mobile (decision of 22/10/2026).

UI

• Rotina button in the Time module (top actions on desktop, category row on mobile) opens a mini-planner.
• Paint 30-minute cells for the default week, pick category or eraser; Clear affects only the visible hour window.
• Blocks outside the configured hour window are preserved on save.
• docs/ROUTINE.md documents the model and rules.

Verification

• npm run check
• npm test (40 files / 284 tests)
• npm run build
• npm run csp:check (23/23)

Pending manual check on device: paint/save a routine, confirm future blocks appear, manual conflicts are skipped, and editing/deleting a generated block stays one-off after reopening the app.