Widget system Phase 2: full cutover to widget-based rendering

device.py's mode-keyed dispatch is replaced by a real compositor:
load a frame's widgets, compute pixel rects via app/grid.py, render
each through its widget module, and composite with render_panel.
Physical NEXT/BACK buttons now execute each frame's assigned
FrameButtonAction rows instead of one hardcoded per-mode action.

api_frames.py, manage.py, and common.py's build_manage_content are
repointed to read/write the frame's widget config rows instead of
the old Frame columns, and every settings page (Photos/Calendar/
Whiteboard tabs) now pre-fills its form from the same widget config
the write endpoints actually save to -- previously the read and
write sides would have silently diverged. The old mode selector and
photo-inlay checkbox are removed along with their now-inert wiring;
arbitrary widget placement subsumes what the fixed inlay split did.

Ships together with Phase 1 (per-type render/action modules) since
splitting the read/write cutover across deploys would have left
settings changes with no visible effect.

server/app/widgets/__init__.py

@@ -6,14 +6,19 @@ optionally responds to named button actions."
 
 Each module in this package exposes:
 
-    render(db, frame, widget, target_w, target_h) -> Image.Image
+    render(db, frame, widget, target_w, target_h, is_normal_wake=True) -> Image.Image
         An RGB image exactly target_w x target_h, unquantized -- the
         widget's content composed into its own region. Never returns
         packed panel bytes or raises for a foreseeable failure (a
         widget's own fetch hiccup shows a small placeholder instead) --
         image_pipeline.render_panel composites every widget's own
         render() result onto one shared canvas and quantizes/packs the
-        whole thing once (see its own docstring).
+        whole thing once (see its own docstring). is_normal_wake
+        distinguishes an ordinary /frame/image GET from a button-
+        triggered re-render -- only app/widgets/calendar.py's render()
+        actually uses it (resetting browse_offset back to "today" on a
+        normal wake), but every module accepts it for one uniform call
+        signature regardless.
 
     ACTIONS: dict[str, Callable[[Session, Frame, Widget], None]]
         Named button actions this widget type supports (e.g. "advance",

server/app/widgets/calendar.py

@@ -34,7 +34,19 @@ from ..routers.common import (
 ACTION_LABELS = {"advance": "Next period", "back": "Previous period"}
 
 
-def render(db: Session, frame: Frame, widget: Widget, target_w: int, target_h: int) -> Image.Image:
+def render(db: Session, frame: Frame, widget: Widget, target_w: int, target_h: int,
+          is_normal_wake: bool = True) -> Image.Image:
+    """is_normal_wake=True (an ordinary /frame/image GET, not a button
+    press) resets browse_offset back to "today" if it had drifted --
+    mirrors the old _render_calendar_mode's identical behavior. A button
+    press explicitly moved the browse position on purpose, so it passes
+    is_normal_wake=False to render its own already-updated offset instead
+    of immediately snapping back to 0."""
+    if is_normal_wake:
+        with widget_locked(db, frame.id, widget.id) as (_, _, locked_cfg):
+            if locked_cfg.browse_offset != 0:
+                locked_cfg.browse_offset = 0
+
     cfg = db.get(CalendarWidgetConfig, widget.id)
     events, fetch_summary = get_or_refresh_calendar_events_for_widget(db, frame, widget)
     weather_cities = get_or_refresh_weather_for_widget(db, frame, widget) if cfg.weather_enabled else None

server/app/widgets/photos.py

@@ -26,7 +26,13 @@ from ._shared import placeholder_image
 ACTION_LABELS = {"advance": "Next photo", "back": "Previous photo"}
 
 
-def render(db: Session, frame: Frame, widget: Widget, target_w: int, target_h: int) -> Image.Image:
+def render(db: Session, frame: Frame, widget: Widget, target_w: int, target_h: int,
+          is_normal_wake: bool = True) -> Image.Image:
+    """is_normal_wake is unused here -- photos mode's advance timing is
+    already fully idempotent via get_current()'s own elapsed-time check,
+    unlike calendar mode's browse_offset (see app/widgets/calendar.py's
+    render()). Accepted anyway so every widget type's render() shares one
+    call signature regardless of which ones actually care."""
     cfg = db.get(PhotoWidgetConfig, widget.id)
     if not cfg.album_id:
         return placeholder_image(target_w, target_h, ["Photos widget", "not configured yet"])

server/app/widgets/whiteboard.py

@@ -22,7 +22,11 @@ from ._shared import placeholder_image
 ACTION_LABELS = {"check_now": "Check for updates"}
 
 
-def render(db: Session, frame: Frame, widget: Widget, target_w: int, target_h: int) -> Image.Image:
+def render(db: Session, frame: Frame, widget: Widget, target_w: int, target_h: int,
+          is_normal_wake: bool = True) -> Image.Image:
+    """is_normal_wake is unused here -- see app/widgets/photos.py's
+    identical note; every widget type's render() shares one call
+    signature regardless of which ones actually care."""
     png_bytes = get_or_refresh_whiteboard_for_widget(db, frame, widget)
     if png_bytes is None:
         return placeholder_image(target_w, target_h, ["Whiteboard widget", "not configured yet"])