docs: record built-in weekly tasks

Co-Authored-By: Claude Opus 5.5 <[email protected]>

docs/DATA-MODEL.md

@@ -473,7 +473,7 @@ ID spaces, and the reason is the one this document keeps making:
 mygame:<slug>        a game the reader defined      "mygame:limbus-company"
 myevent:<random>     an event the reader entered    "myevent:k3f9qa2m"
 mytask:<random>      a weekly or monthly task       "mytask:p0q8n3x2ab"
-routine:<game>:<slug>  a built-in task (held for phase 2b; nothing writes it yet)
+routine:<game>:<slug>  a built-in weekly task      "routine:zzz:ridu-weekly"
 ```
 
 **A reader's event is never minted as `${game}:${slug}:${date}`.** That space is derived from source
@@ -513,6 +513,14 @@ one a newer version wrote, and opening an older tab must not erase it. `amounts`
 pruned. An event's points goal stores its numbers the same way, under the event id. Deleting a task
 removes the task record only.
 
+**Built-in tasks** (`src/shared/routines.ts`) are not stored: they ship in the bundle, each with a
+`source` URL and the `asOf` date that page gives, and their ticks and numbers are stored under their
+`routine:` id exactly as a reader's task's are. Two prefs govern them: `routineGames` (games whose
+built-ins are on) and `routinesAsked` (games already asked), both **absent meaning none** so they
+are opt-in for every install. *Make it mine* adds a `mytask:` with `from: <routine id>` and copies
+the routine's day log and amounts to it — additively, so deleting the copy shows the original
+with its own numbers again.
+
 Reader-authored events reuse `progress`, `daily` and `ignored` unchanged, keyed by their `myevent:`
 id — everything the reader can say about a scraped event they can say about their own, with no
 second set of stores to keep in sync.

docs/DESIGN.md

@@ -415,6 +415,9 @@ selected tab fills with `raised` and turns ink; unselected tabs are faint and go
   label, a small numeric field on `ground`, `/ 2,100 points`, and a near-pill Save. Weekly and
   monthly counts sit on their own faint line under the strip's heading, so the reset countdown
   never wraps.
+- **Built-in question** (top of the dailies strip, once per game): one line of muted text —
+  `Track Zenless Zone Zero's built-in weekly tasks?` — with a near-coloured **Yes** and a faint **No
+  thanks** as plain text buttons. Never a card, never a modal; the strip renders for it alone.
 - **Check-in goal control** (detail sheet, under the daily checklist): the status pills' style —
   Off / Each week / Across the event — then a small number field and, for weeks, a weekday select,
   both on `ground` with a hairline border like the notes field. Once a goal is set, a smaller

docs/PRD.md

@@ -557,8 +557,12 @@ default) or **reach a number** (a target such as 2,100, with an optional unit).
 - **Theirs, kept and exported.** Deleting a task removes the task only; its ticks and numbers stay.
   Both travel in the export, and import never rolls a newer week back.
 
-Built-in tasks per game, offered when a game is switched on, are specified as the next phase
-(`docs/superpowers/specs/2026-10-13-periodic-tasks-design.md` § Phase 2b) and are not built yet.
+**Some games' weekly tasks are built in** — ZZZ's Ridu Weekly (1,300 points) and Endfield's Weekly
+Routine (10 points) so far, each from a cited page and shown with the date that page gives, so a
+figure from an old guide is visibly old. They are **off until the reader says yes**: the strip asks
+once, in one line, about a game on screen that has them, and a switch per game in *What you see*
+governs them after. Built-ins are not edited in place; **Make it mine** copies one into the reader's
+own tasks with its ticks and numbers, and hides the original while the copy exists.
 
 ## Out of scope for v1
 

docs/superpowers/specs/2026-10-13-periodic-tasks-design.md

@@ -2,7 +2,9 @@
 
 **Date:** 2026-10-13
 
-**Status:** phase 2a implemented 2026-10-13; phase 2b not started. Spec 2 of 2. Builds on `2026-10-03-check-in-goals-design.md` (the
+**Status:** implemented 2026-10-13 (2a and 2b). Spec 2 of 2. The per-game switch lives in *What
+you see* beside the daily-chores switch rather than on each game row, and *Make it mine* is in
+settings only. Builds on `2026-10-03-check-in-goals-design.md` (the
 period engine and goals) and ships after it, in two phases.
 
 ## Request and intended outcome