docs: mark sub-projects 2 and 3 shipped; record the reviews' deferred items

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-10-16 06:45:30 +02:00
parent c2cc685f65
commit 256ea71cc0
4 changed files with 28 additions and 1 deletions
@@ -58,6 +58,24 @@
 - [ ] Track Infinity Nikki's *Pinnacle Contest*, which resets on the 1st and 16th of each month
  (infinity-nikki.fandom.com/wiki/Mira_Crown, 2025-12-08) — a half-month period, which `period.ts`
  cannot express yet. *Merit Arena* has no page stating its cycle; leave it until one does.
+- [ ] Small things the whole-branch reviews of sub-projects 2 and 3 found and left (2026-10-16),
+  none a bug a reader meets today:
+  - At phone width, with weekly, monthly and cycle tasks all present, the strip header's period
+    counts wrap ("Cycles 0/8" on its own line). `Dailies.tsx`, the `periodCounts` line.
+  - Copy still says "weekly and monthly" where cycles now count too: `YourOwn.tsx` (the tasks and
+    built-ins headings), `Controls.tsx` ("Show built-in weekly and monthly tasks"), and the
+    strip's one-time question "Track X's built-in weekly and monthly tasks?" — a yes also turns on
+    that game's cycle built-ins. Fold into the settings rework below.
+  - The header label "Cycles" against "Weekly"/"Monthly".
+  - `TaskForm.tsx`'s `isDayKey` checks the pattern only; the schema also refuses impossible dates.
+    A date input cannot produce one, so the two agree in practice.
+  - Editing a cycle task's length or start files its old numbers under the old start keys (kept,
+    and restored by undoing the edit) — the same as editing a week's start day, but with no
+    notice; `CustomForms.tsx`'s `strandedNotice` could be reused.
+  - `fandomtable` and `fandomversion` are kept apart per table, not per page: a page holding both
+    kinds of table would match both parsers (none does). `PassSource.title(rowName)` and the
+    `"event"` name heading were for Miliastra and are unused; `cells`, `wholeDate` and `pageUrl`
+    are copied between `fandomTable.ts` and `versionTable.ts`.
 - [ ] **Rework the settings, with mockups first** (owner, 2026-10-16: "we will have to do a
  settings rework of some kinds with some mockups"). *What you see* keeps gaining switches —
  dailies, built-ins globally and per game, standard-banner pulls, weekly / monthly tasks, and
@@ -2,7 +2,8 @@

 Date: 2026-10-14. Status: **shipped 2026-10-16** (`612e0a2..23924db`, merged to `main`), every
 entry verified in game by the owner except the two open in TODO.md. Sub-project 1 of 3 — see
-§ Scope; sub-projects 2 and 3 are next, with their starting points in TODO.md.
+§ Scope; sub-projects 2 and 3 shipped the same day — the [cycle routines spec](2026-10-16-cycle-routines-design.md)
+and the [pass windows spec](2026-10-16-pass-windows-design.md).

 ## Problem

@@ -1,5 +1,9 @@
 # Built-ins on longer cycles — design

+Date: 2026-10-16. Status: **shipped 2026-10-16** (`a80f581..f19ef32`, plus review fixes `4427f6c`,
+`5080397`; merged to `main` at `9488053`). The owner's four in-game checks of § Entries were
+deferred by the owner to TODO.md. Sub-project 2 of 3.
+
 Sub-project 2 of the owner's "usual repeatable events" request. Sub-project 1 (weekly and monthly
 built-ins, per-item tracking) is in the [built-in routines spec](2026-10-14-built-in-routines-design.md),
 whose § Scope item 2 holds the in-game readings this design starts from.
@@ -1,5 +1,9 @@
 # Battle pass windows as feed events — design

+Date: 2026-10-16. Status: **shipped 2026-10-16** for Star Rail, ZZZ and Infinity Nikki
+(`40d0dbe..c2cc685`, merged to `main`); see § Outcome for what changed from the plan, and TODO.md
+for Endfield, Wuthering Waves and NTE. Sub-project 3 of 3.
+
 Sub-project 3 of the owner's "usual repeatable events" request (sub-project 1: the
 [built-in routines spec](2026-10-14-built-in-routines-design.md), whose § Scope item 3 holds the
 owner's in-game readings; sub-project 2: the [cycle routines spec](2026-10-16-cycle-routines-design.md)).