v0.316.3: the content column sits closer to the top and the sidebar

.app-page carried the mockup's 32px 48px 64px, but the .content wrapper it lives in already
supplies 2rem (1rem on a phone). The two added up: 64px from the top and 80px from the sidebar,
which is the gap the operator called too big. .app-page now adds no top or side padding of its
own — .content's is the page's — and keeps only the extra room at the bottom.

Reported from the rendered page with DevTools open, where both paddings are visible at once. The
mockup's numbers were the TOTAL the page should show, not an amount to add to what was already
there.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0117kRTSgs3rJWUFGxyoWN6Y

controller/internal/web/templates/style.css

@@ -1311,7 +1311,11 @@ a.stat-card:hover {
 
 .app-page {
     max-width: 820px;
-    padding: 32px 48px 64px;
+    /* NO top/side padding of its own: the `.content` wrapper this sits in already supplies 2rem
+       (1rem on a phone). Adding the mockup's 32/48 on top of that pushed the column 64px from the
+       top and 80px from the sidebar — the gap the operator called too big. Only the extra bottom
+       room is this element's to add. */
+    padding: 0 0 32px;
 }
 /* The log is the one tab whose content is genuinely wide: log lines are long, and wrapping them at
    820px makes them unreadable. */
@@ -1443,7 +1447,7 @@ a.stat-card:hover {
 .app-faq dd { color: var(--text-2); margin: .25rem 0 0; padding: 0; }
 
 @media (max-width: 720px) {
-    .app-page { padding: 20px 16px 48px; }
+    .app-page { padding: 0 0 24px; }
     .app-field-row { grid-template-columns: 1fr; gap: 4px; }
     .app-hero-actions { margin-left: 0; flex-basis: 100%; }
     .app-tabs { gap: 18px; }