Something can happen because time passed, and land somewhere worth reading

Nothing in LLeMbas ever happened on its own. Every reply was downstream of
somebody pressing Send, and the one exception -- jobs.wake, waking a chat when a
background job finishes -- was downstream of a command they had run. PLAN.md
never listed scheduling as unbuilt because services/chat.py:618 had recorded it
as a decision: "a scheduler is a whole new concern for a single-worker
application". This is that concern, taken on deliberately, plus the two places
its output goes.

Reports first, because it is useful with no scheduling at all. A report is not a
Chat with one Message in it: it has no turns and no reply, it is read top to
bottom, and it must be writable with no chat behind it -- being the fallback for
a run whose own chat has gone. As a Chat it would need a sidebar row per daily
report, a title that regenerates itself, a composer to suppress and a bubble with
a rewind button around something that is not a turn. The section's character is
enforced by absence: nothing under reports/ includes the composer or renders
chat/_message.html, so there is no sse-connect anywhere and nothing on those
pages *can* start a generation. The test reads that off the OpenAPI schema, not
by walking app.routes -- this FastAPI keeps an included router wrapped rather
than flattening it, so the walk finds nothing and the assertion passes for the
wrong reason.

rule.py is pure, total, and was finished before anything called it. No session,
no wall clock, nothing that raises: validate clamps what it recognises, drops
what it does not, and answers {} for prose -- at which point the caller shows the
manual form. It had to be that way because the compile step's output is model
output that becomes a *timer*, which is the sharpest case of hard rule 6 here.
The invariant, pinned: anything validate accepts has a computable next
occurrence. A schedule that can never fire looks exactly like a working one on
every screen it appears on.

Wall-clock and elapsed time are kept apart because they mean different things.
at.times are wall-clock in the owner's zone, so 15:00 stays 15:00 across a
daylight-saving change -- that is what "every Monday at 3PM" means. every is
elapsed real time, so six hours stays six hours across a 23- or 25-hour day --
that is what a timer means. Conflating them gets one of the two wrong twice a
year. A time inside the spring-forward gap fires at the first minute that exists;
left to zoneinfo's own resolution it lands an hour away wearing a wall-clock time
that did not happen, and a daily 02:30 report vanishing once a year on a machine
nobody watches is the failure this file is arranged around.

The ticker claims and commits *before* it fires. The other order is a hot loop: a
firing that raises is retried every tick for ever against whatever it was that
failed, and the only symptom is load. Its blanket except is copied from the
terminal reaper for a sharper reason -- a ticker that dies on one bad row stops
every schedule on the instance and says nothing at all. No request fails, no
reply errors, no dot appears. The reports simply stop.

Three rules that look like bugs from outside: a firing arriving while the chat is
still answering queues rather than starting a second reply, and past max_queued
is skipped with the reason on the row; Run now does not advance next_fire_at, or
testing a schedule silently consumes the run it was testing; resuming recomputes
from now, or a schedule paused for a month fires the instant it comes back, once
per occurrence it missed. Catching up lives in the sweep and not in a startup
hook, because a suspended host and a long stall reproduce "its time passed while
nothing was running" with no restart to hang one on.

services/wake.py is the lock discipline extracted rather than copied. A finished
job and a due schedule are the same problem, and both depend on there being no
await between the running_for check and the writes; two lock dictionaries for one
invariant is how one of them drifts. jobs.wake is now a caller that supplies
wording, and _completion_text stayed exactly where it was because tool.background
quotes its opening sentence.

A scheduled run has no reader, so ask_user is withdrawn from resolve_tools rather
than merely discouraged in core.unattended -- a rule living only in a system
message is one a page the model just read can argue with, and a parked question
holds the reply for the whole approval_timeout with nobody to answer it. For the
same reason a task chat may not be an agent chat in v1: Manual, Edit and Plan all
stop to ask on RISK_EXECUTE, so the only two outcomes would be unattended
execution and a reply that stalls. That deserves its own pass.

Messages is bounded in the request and unbounded on disk. Only the latest chunk
is sent; everything else stays exactly where it was written. Nothing is folded
into text and nothing is deleted -- the visible conversation is identical either
way, so destroying the older rows would buy only disk, against being irreversible
and losing every attachment and tool call in the range, and it would contradict
the rule compaction already holds. should_compact refuses this kind for the
matching reason: two mechanisms narrowing one transcript is how a summary ends up
summarising a summary. The history route is the mirror of thread_tail and keeps
its four properties; the fifth is its own, that prepending moves the scroll
position, so app.js records scrollHeight before the swap and adds the difference
back after.

An empty Chat.kind meant "both sides of the switch" and had been read as "no
filter" since there were only two of them. The sidebar passes "" precisely when
agent chats are switched off -- so the moment a third kind existed, every task
chat and every Messages conversation appeared in somebody's ordinary chat list,
on exactly the instances whose owners would never think to look. KINDS stays the
two-sided fork, because set_sidebar_kind validates against it and a third entry
there makes the tree filterable to a side with no button to leave it; ALL_KINDS
is what a row may be. Both narrowings are pinned, because they are two
implementations of one rule and only one of them is SQL.

Per-user timezone had to exist for any of this: harness.py:179 was telling every
reader the *server's* idea of the date, which is survivable while the answer is
prose and stops being survivable the moment somebody says "every Monday at 3" and
something has to work out when that is.

Three things were caught by a test being wrong rather than by the code being
wrong. The task-chat "no composer" assertions were passing against a page
rendering its no-models-configured branch. A permission test asserted the same
thing twice because the administrator bypasses every permission. And every
Messages test passed with default_model never called, because none of them
configured a model -- so the pair it returns was being assigned straight to
model_id, and SQLite refuses a tuple in a String column. The fixtures now say why
they exist.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

PLAN.md

@@ -8,7 +8,8 @@ that would be expensive to revisit. Kept current as work lands; the detail of
 with web search, custom HTTP tools and MCP servers, agent chats that work on a
 machine over SSH, a knowledge library, notes, memory and skills, speech in and
 out, image generation over ComfyUI, users and groups, model administration,
-installable as an app. 1676 tests, `ruff` clean.
+installable as an app, reports, messages, and scheduled work that runs on its
+own. 1805 tests, `ruff` clean.
 
 ---
 
@@ -239,6 +240,55 @@ be a different project, not a refactor.
       contents come along, with the path and the machine, so the model knows
       exactly which file it was handed
 
+### Scheduling
+- [x] **Schedules** — work that runs because time passed rather than because
+      somebody asked just now. Fire once or repeat; a fixed number of runs or
+      until stopped; a timer ("every ten minutes") or a calendar ("every Monday
+      at 3PM"), and the two compose into "every other Monday"
+- [x] **Wall-clock and elapsed time are kept apart**, because they mean
+      different things: a calendar time stays 15:00 across a daylight-saving
+      change, while a six-hourly timer stays six hours. A time that does not
+      exist on a spring-forward day fires at the first minute that does
+- [x] **Per-user timezone**, so "every Monday" means the reader's Monday. The
+      harness tells them their own time now, not the server's
+- [x] **Scheduled** — one chat per task, replied into each time it comes round.
+      No composer: run it now, pause it, edit it, remove it
+- [x] A missed run **catches up once** and then resumes. A week of downtime owes
+      one report, not a hundred and sixty-eight
+- [x] Claim before firing, so a run that fails moves the schedule on rather than
+      retrying every tick for ever; and "Run now" deliberately does *not* consume
+      the run it was testing
+- [x] **Say it in your own words** — a model turns "every Monday morning, check
+      the build" into a recurrence and an instruction that reads on its own,
+      and shows it back for approval before anything is saved. Anything it
+      cannot work out lands in the same form, filled in as far as it got
+- [x] A scheduled run knows nobody is watching: `ask_user` is **withdrawn**, not
+      merely discouraged, because a question with no one to answer it holds the
+      reply until it times out
+
+### Messages
+- [x] **Messages** — one conversation per person that is meant to run for
+      years. It opens on the most recent turns and pages older ones in as you
+      scroll up
+- [x] **Bounded in the request, unbounded on disk.** Only the latest chunk is
+      sent to the model; everything else stays exactly where it was written.
+      Nothing is folded into text and nothing is deleted
+- [x] Anything scheduled can post here, and the schedules that do are listed
+      beside the conversation rather than two pages away
+
+### Reports
+- [x] **Reports** — a section of its own for finished work: an investigation
+      written up, an account of what an agent chat changed, whatever a schedule
+      leaves behind. Filed with `report_write`, searched with FTS5, read on its
+      own page
+- [x] **Nothing here can be replied to**, and that is the section rather than a
+      restriction on it. No composer, no route that accepts a message, and
+      nothing on either page that renders the streaming shell — so there is
+      nothing that could start a generation
+- [x] Its own family, permission and capability flag, so a model that keeps
+      notes need not file reports and a model that files reports need not have
+      a library at all
+
 ### Audio
 - [x] **Dictation** — record in the composer, transcribed by any OpenAI-shaped
       `/v1/audio/transcriptions` endpoint. The recording never touches disk
@@ -344,6 +394,16 @@ Running several workers needs that state in the database or a broker, because
 the request following a reply would not necessarily land in the process writing
 it.
 
+The schedule ticker is now the strongest reason this is not merely a
+convenience. It is in-process like the rest, so **two workers means two tickers
+and every schedule firing twice**. The claim that prevents a double-fire is a
+Python lock plus a write committed in the same transaction, not `SELECT ... FOR
+UPDATE`, which SQLite does not have. Scheduling also makes downtime visible in a
+way nothing else here does: a dropped reply is one somebody watched fail, while
+a missed run is one nobody saw at all — which is what the catch-up in the sweep
+is for, and why it lives there rather than in a startup hook (a suspended host
+or a long stall reproduces it with no restart to hang one on).
+
 **A restart abandons replies in flight.** Shutdown cancels them and keeps what
 each had. There is no resume.