Phase 6: schedules, blocklists, allowlists (editors + effective state)

- Weekly schedule editor per device: a Monday-Sunday grid of blocking
  windows, including windows that cross midnight.
- Blocklist/allowlist editor per device: app (Android package / Windows
  process) and site (hostname) entries, tagged by the device platform.
- Effective desired state: a manual lock, an active schedule window, or
  neither. While blocked the allowlist is honoured (Spotify stays while
  other apps are blocked). Published retained with reason schedule/manual.
- Boundary-aware republish loop so a window turns on and off on time,
  and manual lock expiry is cleared promptly.
- CONTROL_TIMEZONE (default Australia/Sydney) with embedded tzdata, so
  wall-clock windows are evaluated in the family zone, not the container.
- Every change is written to the append-only audit log (FR-15).

Co-Authored-By: Paperclip <noreply@paperclip.ing>

internal/web/templates/partials/device-cards.html

@@ -12,7 +12,7 @@
     </header>
 
     <p class="device-card__state">
-      {{if .Locked}}Blocked{{if .TimeLeft}} · {{.TimeLeft}}{{end}}{{else}}No block active{{end}}
+      {{if .Locked}}Blocked{{if .ReasonLabel}} {{.ReasonLabel}}{{end}}{{if .TimeLeft}} · {{.TimeLeft}}{{end}}{{else}}No block active{{end}}
     </p>
     {{if .Until}}<p class="device-card__until">Lifts {{.UntilLocal}}</p>{{end}}
 
@@ -34,6 +34,8 @@
       </form>
       {{end}}
       <a class="button-utility" href="/devices/{{.ID}}/edit">Edit</a>
+      <a class="button-utility" href="/devices/{{.ID}}/schedule">Schedule</a>
+      <a class="button-utility" href="/devices/{{.ID}}/lists">Lists</a>
     </div>
 
     <p class="device-card__foot">