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>

src/lembas/api/pages.py

@@ -2,21 +2,35 @@
 
 from __future__ import annotations
 
+from zoneinfo import available_timezones
+
 from fastapi import APIRouter, HTTPException, Request, Response, status
 from fastapi.responses import FileResponse, JSONResponse, RedirectResponse
 from sqlalchemy import select
 from sqlalchemy.orm import Session as DBSession
 
 from lembas.api.deps import Db, RequiredUser
-from lembas.db.models import KIND_CHAT, KINDS, Chat, Folder, KnowledgeBase, Message, User
+from lembas.db.models import (
+    KIND_CHAT,
+    KIND_MESSAGES,
+    KIND_TASK,
+    KINDS,
+    Chat,
+    Folder,
+    KnowledgeBase,
+    Message,
+    User,
+)
 from lembas.security import permissions
 from lembas.services import audio as audio_service
 from lembas.services import canvas as canvas_service
 from lembas.services import chat as chat_service
 from lembas.services import compaction as compaction_service
+from lembas.services import reports as reports_service
 from lembas.services import settings_store
 from lembas.services import suggestions as suggestions_service
 from lembas.services.library import documents as documents_service
+from lembas.services.schedule import clock
 from lembas.web.templating import STATIC_DIR, render
 
 router = APIRouter(tags=["pages"])
@@ -141,6 +155,7 @@ _GATE_LABELS = {
     "memory": "Memory",
     "skills": "Skills",
     "ask": "Asking you questions",
+    "report": "Filing reports",
     "agent": "Running commands",
     "custom": "Custom tools",
     "mcp": "MCP servers",
@@ -309,9 +324,13 @@ def sidebar_context(db: DBSession, user: User) -> dict:
         Chat.folder_id.is_(None),
         Chat.archived.is_(False),
         Chat.temporary.is_(False),
+        # `kind` empty means "both sides of the switch", never "no filter" --
+        # see `Folder.visible_chats`. Task chats and the Messages conversation
+        # have sections of their own and must never appear in this list, and
+        # the case that reaches here with "" is precisely an instance with
+        # agents disabled, where nobody would ever see the leak coming.
+        Chat.kind.in_((kind,) if kind else KINDS),
     )
-    if kind:
-        narrowed = narrowed.where(Chat.kind == kind)
     unfiled = list(
         db.scalars(narrowed.order_by(Chat.pinned.desc(), Chat.updated_at.desc()))
     )
@@ -326,6 +345,22 @@ def sidebar_context(db: DBSession, user: User) -> dict:
         # not there on any of them. The picker lists every model in the
         # administrator's order, pinned or not; pinning is not ordering.
         "pinned_models": [m for m in chat_service.available_models(db, user) if m.pinned],
+        # Whether the Reports entry starts with its dot showing. Only the first
+        # paint: from then on `/api/chats/unread` moves it out of band, the same
+        # deal a chat row's dot has. Counted rather than existence-checked
+        # because the same query answers both and a count is what a title would
+        # want if this ever grows one.
+        "unread_reports": reports_service.unread_count(db, user),
+        # Read rather than created, for the reason the poll does the same: this
+        # runs on every page, and `messages.for_user` would write a conversation
+        # for every account that has never opened the section.
+        "unread_messages": bool(
+            db.scalar(
+                select(Chat.unread).where(
+                    Chat.user_id == user.id, Chat.kind == KIND_MESSAGES
+                )
+            )
+        ),
         "sidebar_kind": kind,
         # Whether the switch is worth showing at all. A two-way switch with one
         # useful side is worse than no switch: it offers a view that is empty by
@@ -571,12 +606,45 @@ async def chat_detail(request: Request, db: Db, user: RequiredUser, chat_id: str
             "bodies": bodies,
             "inherited_prompt": inherited,
             "inherited_from": inherited_from,
+            **_schedule_context(db, user, chat),
             **_chat_context(db, user, chat),
             **sidebar_context(db, user),
         },
     )
 
 
+def _schedule_context(db: DBSession, user: User, chat: Chat) -> dict:
+    """What the strip below a task chat needs.
+
+    Empty for every other kind, so the three keys exist unconditionally and the
+    template can ask about `schedule` without a `default(false)` -- the same
+    reason `audio_service.template_flags` is passed by all four bubble
+    renderers rather than by whichever one remembered.
+
+    `schedule` being None on a task chat is a real state, not an error: removing
+    a schedule keeps its chat by default, and the strip says so.
+    """
+    from lembas.services import schedules as schedules_service
+
+    if chat is None or chat.kind != KIND_TASK:
+        return {"schedule": None, "schedule_summary": "", "schedule_next": None}
+
+    schedule = schedules_service.for_chat(db, chat)
+    if schedule is None:
+        return {"schedule": None, "schedule_summary": "", "schedule_next": None}
+
+    zone = clock.zone_for(user)
+    return {
+        "schedule": schedule,
+        "schedule_summary": schedules_service.describe(schedule, owner=user),
+        "schedule_next": (
+            clock.as_utc(schedule.next_fire_at).astimezone(zone)
+            if schedule.next_fire_at
+            else None
+        ),
+    }
+
+
 @router.get("/settings")
 async def settings_page(
     request: Request,
@@ -606,6 +674,12 @@ async def settings_page(
             "voice_error": voice_error,
             "memories": memories_service.all_for(db, user),
             "memory_limit": memories_service.MAX_MEMORY_CHARS,
+            # Sorted rather than left in set order, because a list of six
+            # hundred zones that is not alphabetical is one nobody can use.
+            "timezones": sorted(available_timezones()),
+            "timezone": clock.name_for(user),
+            "server_timezone": str(clock.server_zone()),
+            "local_now": clock.now_for(user).strftime("%H:%M on %A %-d %B"),
             **context,
             **sidebar_context(db, user),
         },