fix(forms): Safari focused none of them, and a board could not make a section

Two reports, one sentence between them: "sections have no function, because you
cannot create more than one."

`autofocus` does not work in Safari for anything inserted after the page has
loaded, and every inline form here is inserted after the page has loaded — rename
a project, add a section, name a group. In Safari they all opened with no cursor
in them and what you typed went nowhere. That does not look like a bug. It looks
like the feature does not work. `use:focusOnMount` replaces all seventeen.

And the board had no way to add a section at all. The button lived only in the
list view, which is the one place nobody looks for it: a column on a board *is* a
section, so that is where you go to make one.

Chasing this turned up a third. The task drawer's three fields save on blur, and
closing the drawer *is* a blur — the input is being unmounted and the browser
fires blur on the way out. If the task left the store in the same moment, `task`
was already null and the handler threw `Cannot read properties of null`, stopping
the page. It only became reproducible once focus actually worked.

Fields are 16px on a touch device now, whatever the component asked for. Below
16px, iOS Safari zooms in when a field takes focus and does not zoom back out —
so the whole interface is left too large and has to be pinched back by hand, once
per field. The type scale tops out at 15px, so every input in the app did it.

The sidebar's resize handle sat at `right: -3px`. An absolutely positioned child
counts towards its container's scrollable overflow, and `overflow-y: auto`
resolves the other axis to `auto` too — so those three pixels gave the whole menu
a horizontal scrollbar on every desktop, always. The account name could do it as
well: `overflow: hidden` with no `min-width: 0` cannot shrink, so the row grew
instead of ellipsing.

There is a WebKit pass in the suite now, over one test. The rest stays Chromium
on purpose — a smoke test exists to catch a build that does not work, and three
engines find the same bug three times — but focus is the exception, and it took a
person using the app to find that out.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

web/src/lib/components/TaskRow.svelte

@@ -83,7 +83,7 @@
 			<span class="description">{task.description}</span>
 		{/if}
 
-		{#if assignee || due || task.labels?.length || task.recurrence_text}
+		{#if assignee || due || task.labels?.length || task.recurrence_text || task.subtask_count || task.attachment_count}
 			<span class="meta">
 				{#if assignee}
 					<!-- First in the row, because "who" changes what the rest of the line
@@ -112,6 +112,36 @@
 						{task.recurrence_text}
 					</span>
 				{/if}
+				<!-- What is underneath, said as a fraction rather than a total: "3" tells
+				     you there is something there, "1/3" tells you whether there is
+				     anything left to do, which is the question the list is for. -->
+				{#if task.subtask_count}
+					<span
+						class="badge"
+						class:all-done={task.subtask_done === task.subtask_count}
+						title="{task.subtask_done} af {task.subtask_count} undertasks er lukket"
+					>
+						<svg viewBox="0 0 24 24" aria-hidden="true">
+							<path d="M9 6h11" />
+							<path d="M9 12h11" />
+							<path d="M9 18h11" />
+							<path d="M4 6l1 1 2-2" />
+							<path d="M4 12l1 1 2-2" />
+							<path d="M4 18l1 1 2-2" />
+						</svg>
+						{task.subtask_done}/{task.subtask_count}
+					</span>
+				{/if}
+				{#if task.attachment_count}
+					<span class="badge" title="{task.attachment_count} vedhæftet">
+						<svg viewBox="0 0 24 24" aria-hidden="true">
+							<path
+								d="M21.44 11.05l-9.19 9.19a6 6 0 01-8.49-8.49l9.19-9.19a4 4 0 015.66 5.66l-9.2 9.19a2 2 0 01-2.83-2.83l8.49-8.48"
+							/>
+						</svg>
+						{task.attachment_count}
+					</span>
+				{/if}
 				{#each task.labels ?? [] as label}
 					<span class="label">{label}</span>
 				{/each}
@@ -291,6 +321,32 @@
 		flex: none;
 	}
 
+	/* A mark, not a chip: it sits in the same row as the date and the labels and
+	   must not out-shout them. The task's own text is the thing being read. */
+	.badge {
+		display: inline-flex;
+		align-items: center;
+		gap: 3px;
+		color: var(--ink-faint);
+		flex: none;
+	}
+
+	.badge svg {
+		width: 12px;
+		height: 12px;
+		fill: none;
+		stroke: currentColor;
+		stroke-width: 2;
+		stroke-linecap: round;
+		stroke-linejoin: round;
+	}
+
+	/* Everything underneath is closed. Worth saying, because "3/3" and "1/3" are
+	   the two answers you actually look for and only one of them is good news. */
+	.badge.all-done {
+		color: var(--accent);
+	}
+
 	.label {
 		color: var(--ink-muted);
 		background: var(--surface-raised);