@@ -178,6 +213,34 @@ public partial class PlaceDetailPanel : IAsyncDisposable
 		if (firstRender)
 		{
 			await TryFocusAsync(_closeButton);
+			await ReadPointerTypeAsync();

@@ -662,3 +659,1 @@
- * selecting or deselecting a place never zooms: a reader pressing this button is asking directly, which
- * is not the same event as a selection changing. `panIntoView` below is what a mere selection reaches
- * instead.
+ * Pans and zooms an existing map to a new centre. Reached only from a `Centre` parameter change

@@ -0,0 +37,4 @@
+	{
+		var panelDeclarations = DeclarationsIn(PlaceDetailPanelStylesheet(), ".place-detail-panel");
+
+		panelDeclarations.ShouldContainKeyAndValue("width", FixedContentWidth);

@@ -4,3 +4,4 @@
 using Bunit;
 using Microsoft.AspNetCore.Components.Web;
+using Microsoft.JSInterop;
 using Microsoft.Extensions.DependencyInjection;

@@ -329,0 +395,4 @@
+	/// the panel name a control it is not rendering — so the exhausted outcome brings it back.
+	/// </summary>
+	[Fact]
+	public async Task PlaceDetailPanel_PointerIsFineAndShareIsExhausted_RevealsTheOpenInMapsAppLinkItsOwnMessageNames()

@@ -5,3 +5,3 @@
   "PlaceMark.Domain": 100.0,
   "PlaceMark.Infrastructure": 99.1,
-  "PlaceMark.WebUI": 91.5
+  "PlaceMark.WebUI": 91.4

@@ -0,0 +4,4 @@
+- **Date:** 2026-08-20
+- **Source:** Decided here, working Vikunja task 251, on Rob's own instruction: "drop 'Zoom to place'
+  entirely."
+- **Supersedes:** [ADR-0132](0132-zoom-to-the-selected-place-from-an-explicit-control.md) — its

@@ -0,0 +105,4 @@
+this returns to — with the difference that ADR-0130's clustering has since made a badge click a
+genuine second route, which it was not when ADR-0101 was written.
+
+**`LeafletMap`'s parameter surface shrinks back to what ADR-0101 and ADR-0133 left it.** `Centre`,

@@ -111,0 +131,4 @@
+  button on a fine one — so both carry the medium margin that opens this group of controls, rather than
+  the anchor alone carrying it as it did while the pair was always rendered together (task 226,
+  ADR-0142). The adjacent-sibling rule below restores the small inter-peer gap for the one case where
+  both do render: the pointer read has not landed yet, or Share has exhausted itself and its own

@@ -337,0 +349,4 @@
+	/// Task 255, ADR-0168: <c>Home</c> is what reads <c>(pointer: coarse)</c>, not the panel, so this is
+	/// where the read is proved end to end — the query going out, and the answer reaching the control
+	/// the panel actually renders from it. Reddens if the read is dropped from
+	/// <c>OnInitializedAsync</c>'s own await group, or if <c>PointerIsCoarse</c> stops being passed

@@ -0,0 +175,4 @@
+pre-existing, untouched here, and timing-dependent — is covered on some runs and not others. That is
+91.4734% or 91.5091%, which reportgenerator reports as 91.4 or 91.5. `main` has the same flaky line,
+confirmed by running it there too, but sits at 2550–2551 of 2786 and so reports 91.5 either way. This
+branch adds 17 coverable lines, two of them genuinely unreachable, which is enough to move the value