Weekly chores like 2,100 activity points are a number, not a count of
days, and monthly ones need a month. The status shape now carries its
measure and period start, so tasks can reuse it whole.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Task status reuses the goal status shape, so one chip, one count and one
tally serve chores, events and tasks alike.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Review found three ordinary actions that deleted a goal this build could
not read: "It repeats daily", pressing an already-pressed Off, and "not
daily" without saying so. Only "not daily" clears a goal now, and its
warning keys off what is stored, not what parses.
The count field was bound straight to the goal, so emptying it snapped
the old number back and typing appended to it. It now keeps a draft.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The product, storage and design records now say what a goal is, why it
never marks an event done, and why an unreadable goal is kept rather than
stripped. That last rule is the one a future cleanup would most likely
undo by mistake.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The goal sits under the checklist, where its count shows. With a goal
set, the caption counts against it instead of calling unticked days
missed. Reaching an event-wide goal offers Mark event done but never
takes it. Saying "not daily" says up front that it removes the goal.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
An event wanting five days of seven stays in the strip all week with its
count on the chip. Once the week is met it reads as done this week, and
it counts toward the header without a tick being invented. The burst
now watches today's ticks, so meeting a week by backfilling stays quiet.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Goals ride the existing record, so export and the later-edit-wins import
merge carry them with no new key. Setting one clears a contradicting
"not daily"; saying "not daily" clears the goal, so no conflict hides
in storage.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Some events want five days out of seven, not every day. The goal is the
reader's input, recomputed from the day log on every read, so backfills
and week rollovers need no bookkeeping. An unreadable stored goal reads
as none instead of being stripped, so a newer shape survives an older
bundle.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Check-in goals and weekly tasks both need a period longer than a day.
Working in game-day keys rather than instants means a week rolls exactly
where the game's own day does, per region, with no second clock.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The goal control lives on the checklist only: "It repeats daily" already
reaches it from a non-daily event, so a second entry point added nothing.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The goals draft stopped at three open questions; the owner answered them,
and widened the scope to weekly and monthly chores with numeric targets.
Both share one period engine, so they are specified together and built
goals-first.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Every server's reset hour and offset was checked against it, so it is
credited beside the schedules' sources.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Rewrites the reset table for every corrected game, records the rule that a
game's offset must make its day key name the source's calendar day, and
names Game-Time-Master as the evidence for server clocks a source does not
state (transcribed, never vendored: it is GPL-3.0).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Game-Time-Master gives the reset as 05:00 JST (20:00 UTC). The previous
04:00 was read off a single mission ending at 3:59AM JST.
Re-labels the game-day of some already-logged ticks.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Reverse: 1999 has an Asia server on UTC+8 alongside Global on UTC-5, both
resetting at 05:00. Asia readers were on Global's 10:00 UTC; theirs rolls
at 21:00 UTC. Source: Game-Time-Master.
Re-labels the game-day of some already-logged ticks for Asia readers.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Haoplay Asia resets at 05:00 UTC+8 and Haoplay Global at 21:00 UTC-8; the
app used the regional default at 04:00. Asia readers take the Asia server,
America and Europe take Global. Source: Game-Time-Master.
Re-labels the game-day of some already-logged ticks.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
NTE resets at 05:00 server time, not 04:00, and its America server runs
UTC-4. Asia and Europe rolled an hour early; America lands on the same
09:00 UTC instant and day key as before. Source: Game-Time-Master.
Re-labels the game-day of some already-logged ticks in Asia and Europe.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
One worldwide server on a fixed UTC-7 resetting at 13:00 (20:00 UTC); the
app used the regional default. Source: Game-Time-Master, which lists the
zone as fixed rather than Pacific.
Re-labels the game-day of some already-logged ticks.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The Global server resets at 05:00 UTC; the app used the regional default.
Source: Game-Time-Master.
Re-labels the game-day of some already-logged ticks.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The English/Japanese server resets once worldwide at 20:00 UTC; the app
used the regional default. Source: Game-Time-Master.
Re-labels the game-day of some already-logged ticks.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
One worldwide server resetting at 18:00 UTC; the app used the regional
default. Source: Game-Time-Master, corroborated by GameWith.
Re-labels the game-day of some already-logged ticks.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Umamusume Global resets once worldwide at 15:00 UTC (midnight JST); the app
used the regional default. Kept on the UTC calendar because the source's
dates are headed Availability (UTC). Source: Game-Time-Master.
Re-labels the game-day of some already-logged ticks.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Blue Archive Global is one worldwide server resetting at 19:00 UTC, but the
app used the regional default (20:00 / 09:00 / 03:00 UTC). Source:
Game-Time-Master, corroborated by two guides.
Re-labels the game-day of some already-logged ticks.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Infinity Nikki resets at 04:00 on America UTC-7 and Europe UTC+2, not the
regional default, so the app rolled the day 2h early for American readers
and 1h late for European ones. Source: Game-Time-Master.
Re-labels the game-day of some already-logged ticks for those readers.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A game's servers need not agree on the reset hour any more than on the
offset. Reverse: 1999 and Nikke spell their 05:00 out for all three
regions, so no reader's day key moves.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
