feat(app): reviews know how a card was studied; progress can start afresh
Each review records its mode (ADR 0004, rule 3): front to back, back to front with a schedule of its own, or crammed outside the schedule. A card's schedule replays only the reviews of one mode. Resetting progress appends a 'reset' entry per card, no migration (the column is text): schedules replay what follows it, and the history stays for the streak and the heatmap. Reviews are inserted in batches. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Tizian 「ティツィアーン」 <raisondetredev@pm.me>
This commit is contained in:
parent
8cf7749ed6
commit
baace1b6e9
1 changed files with 214 additions and 69 deletions
|
|
@ -56,7 +56,9 @@ revision's payload, and the per-side merge of ADR 0003 becomes per field.
|
|||
back), `reverse` (back to front, with a schedule of its own, as Anki's reverse cards
|
||||
have) or `cram` (outside the schedule: it counts for streaks and the activity
|
||||
heatmap, and never moves a schedule). A card's schedule replays only the reviews of
|
||||
one mode. Existing reviews are `review`.
|
||||
one mode. Existing reviews are `review`. Resetting a card's progress (added
|
||||
2026-10-01) appends a `reset` entry rather than deleting reviews: schedules replay
|
||||
only what follows it, and the streak and the heatmap keep the history.
|
||||
4. **A person's settings are one synced row.** `person_settings` holds settings in a
|
||||
versioned payload: study goals now, other preferences later. Two devices creating it
|
||||
while offline make two rows; the app keeps the one with the smallest id and folds the
|
||||
|
|
|
|||
Loading…
Reference in a new issue