Dashboard: layout persistence (dashboard-layout / front-wall-layout) — verify scope first #66

Part of #62 — Dashboard & data-management surface

GET|PUT /api/user/dashboard-layout and GET|PUT /api/user/front-wall-layout persist the
web's arrangeable tile layouts.

This issue is a decision, not a build. Re-check both against the live API with a bearer token.
Then decide:

• If they are cookie-gated web surfaces → close as out-of-scope and note it on the epic.
• If they are bearer-reachable → decide whether a phone should honour a layout designed for a wide
  screen. Adopting it verbatim is likely the wrong call; ignoring it entirely means a user who
  rearranges their dashboard on the web sees no effect on mobile.

Done when: the decision is recorded with evidence, and any follow-up work is filed.

Filed from the parity review of feature/parity-wip @ 14d7795 against interlinedlist.com (OpenAPI /api/openapi.json, 233 paths) and the public help centre.