Plan recurring custom events, task by task

Browse Source

Eleven tasks from the design, each with its own test cycle and commit.
Ordered so the schema field lands before anything derives from it and the
store migration is proved before a single row is expanded.

Three things the plan had to settle that the spec left to the implementer.
The overlap check is one exported predicate, because a form that restates
its schema's rule drifts from it and starts refusing saves that would
succeed. The timeline's expansion needs App to pass the same four scope
filters the lists use, so the predicate is extracted rather than copied.
And custom-ui.test.tsx renders statically with no testing-library in the
project at all, so anything needing a click is stated as a pure function
and tested directly rather than through a harness that does not exist.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>

...

This commit is contained in:

Lucas Winther

2026-08-27 02:10:05 +02:00

co-authored by Claude Opus 5

parent 98cd950e8e

commit c07e37a4a7

1 changed files with 2359 additions and 0 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

docs/superpowers/plans/2026-08-27-recurring-custom-events.md

+2359

File diff suppressed because it is too large Load Diff