makiolaj
1c323d5b4c
Review fixes for the silence-after setting. Changing the alarm's silence-after now re-measures a ring in progress at once, through AlarmEngine.onSilenceAfterChanged: past the new window it closes as missed, inside it the backstop moves. onAutoSilence also re-arms instead of closing a ring that is still inside the current window, so a backstop armed for a shorter window cannot end a ring early. A cycle the resolver closes as missed (a ring past its window, or a snooze that never fired) now disables a one-shot alarm, as the engine's own close does. A short window made that path much easier to reach, and the alarm was being armed for the same time the next day. A late snooze is kept for the window or ten minutes, whichever is longer, so a short window never makes a promised snooze easier to lose than in v1. A timer that has gone quiet stays quiet when the setting is raised: the lapsed anchor moves back past the hard stop. The timer's heads-up is now keyed to the session anchor rather than the window's end, so editing the setting mid-ring no longer counts as a new session and alerts again. A negative stored value now reads as the default instead of Never. The picker offers a stored value that matches no choice, and the wake-lock timeout is one shared constant. Refs #17
Clockula — documentation
Clockula is a Material 3 Expressive clock app for Android: alarms, timers,
stopwatch and world clock. Third floret of the bloom, after
Calendula (calendar) and
Agendula (tasks). See the top-level
../README.md for the pitch.
Unlike its siblings, Clockula owns its storage, because there is no open provider behind
a clock. What that costs and how the open-standards commitment is honoured anyway
is the first section of PLAN.md.
Index
| Doc | What it covers |
|---|---|
PLAN.md |
The spec. Thesis, locked decisions, the alarm engine, data model, system interop, identity, pipeline, and how ClockMaster is used. The "why". |
ROADMAP.md |
Status and the work queue: milestones M0–M11 and post-v1. What the build loop works through. |
ARCHITECTURE.md |
How Clockula is built today: layers, the data seam, the alarm engine, DI, build/tooling, manifest. Written from M2 onward. |
RELEASING.md |
How to cut a release. Written at M0 alongside the pipeline. |
PROVENANCE.md |
Third-party code and assets carried in-tree, and under what licence (PLAN.md §11). |
Also: ../CHANGELOG.md (Keep a Changelog format; tag sections
feed the release notes).
How the docs relate
- PLAN is the design decisions (stable; the "why").
- ARCHITECTURE is the current shape of the code (kept in sync as it grows).
- ROADMAP is the moving status layer (updated as milestones land).
- RELEASING is the operational runbook.