Run the PWA device checklist and close each #249 child that passes #355

Parent

#328. Related: #249, #197, #247, #248, #250, #251, #252, #253, #254, #255, #256, #258, #308, #309, #310, #312

What to build

The #249 PWA work is built and live on https://docs.plus. No child counts as shipped until it passes on a real device. Headless browsers cannot check a splash, a vibrate, an app badge, a share sheet, or a screen reader. This issue runs one checklist on real devices. Each child issue closes when all of its checks pass.

Acceptance criteria

• Every check in the table under "Agent brief" has a result: pass, fail, or not run, with the device and OS version.
• The results are posted as one comment on Deepen the installed PWA #249.
• Each Deepen the installed PWA #249 child whose checks all pass is closed, with a comment that names the device and OS version.
• Harden the offline document mirror: claim persistent storage, and surface a write failure #197 gets a comment with its row result. It stays open, because its storage-full check is not on this list.
• Each failed check has a comment on its child issue, with steps and a screen recording or screenshot. A failure that matches Hide the phone edit toolbar when the pad is read-only #308, A heading deep link puts the first Tab on a TOC row #309, Sheet focus trap: Tab escapes during the open tween, and the backdrop is an unnamed button #310 or A cold push click does not mark the notification read #312 goes on that issue instead.
• Deepen the installed PWA #249 stays open until every child is closed or has a filed failure.

Blocked by

None — can start now.

Agent brief

Type: HITL — a person with an iPhone, an Android phone and a desktop Chromium browser runs each check. They post the results on #249 and close the children that pass. The bounce alert row waits for #354; mark it "not run" until then.

Category: enhancement

Current behavior: The build is live. The production manifest serves share_target with action /receive, and the three iPhone splash images return 200 (checked 2026-09-28). The repo copy is apps/webapp/public/manifest.json. No real-device result is recorded on any #249 child.

Desired behavior: Each #249 child is either closed on a passed device check or carries a filed failure.

The checks, per device. "Issue" is where the result goes. A #249 child closes when all of its rows pass.

The slug check runs read-only on the production Prisma database:

select slug, "documentId", "createdAt", "deletedAt"
from "DocumentMetadata"
where lower(slug) = 'receive';

Zero rows is a pass. One row means an old pad now sits behind the reserved route. Post the row on #253.

To create a bounce alert, use a test account only. A maintainer runs select public.record_email_bounce('<test account email>', 'hard'); in the Supabase SQL editor. That call also pauses the account's email notifications. Turn them back on in Settings → Notifications after the check.

Where to start: Only for writing a precise failure report. Splash: apps/webapp/src/pages/_document.tsx (apple-touch-startup-image). Badge: apps/webapp/src/utils/appBadge.ts. Vibrate: apps/webapp/src/components/chatroom/components/MessageCard/hooks/useLongPressInteraction.ts (navigator.vibrate). Home collapse: apps/webapp/src/components/pages/home/HomePage.tsx (HomeCollapseRegion). Persist: requestPersistentStorage in apps/webapp/src/hooks/useYdocAndProvider.ts. First-visit reload: controllerchange in apps/webapp/src/hooks/useServiceWorker.ts. Find: apps/webapp/src/components/TipTap/find/FindBar.tsx. Command jump: apps/webapp/src/components/commandJump/CommandJump.tsx. Inbound share: apps/webapp/public/service-worker.js and apps/webapp/src/pages/receive.tsx. Line numbers are hints as of 2026-09-28; the agent searches by symbol.

Rules that apply: apps/webapp/CLAUDE.md §Landing Page Shell And PWA (parked guards #257, #259, #260, #261 stay open). AGENTS.md §UI And Theme. Names follow CONTEXT.md (Slash menu, Command jump).

Verify: Run each row on https://docs.plus in light and dark theme where the row shows UI. Record device model, OS version and browser version for each result.

Out of scope

• Fixing a failed check. File or update the child issue, and fix it there.
• The known follow-ups Hide the phone edit toolbar when the pad is read-only #308, A heading deep link puts the first Tab on a TOC row #309, Sheet focus trap: Tab escapes during the open tween, and the backdrop is an unnamed button #310 and A cold push click does not mark the notification read #312. They own their own fixes.
• The Harden the offline document mirror: claim persistent storage, and surface a write failure #197 storage-full check. Harden the offline document mirror: claim persistent storage, and surface a write failure #197 owns it.
• Closing the parked cards Do not force the camera on the profile photo #257, Do not add folders #259, Do not add visit-based Recents #260 and Do not add a second pad window #261. They stay open as guards.