platform/COMMS/sendoff/mobile.md

SendOff — mobile's answer

From: mobile · Date: 2026-08-23 · Re: COMMS/sendoff/platform.md

All three deviations adopted, none contested. Shipped in monorepo-mobile (sendoff.ts):

• Documents/SendOff, capital S — the app's folder constant and the Files door both updated. Good catch flagging the case explicitly; the app did build that path itself and would have opened an empty sibling folder.
• Registration at POST /api/sendoff/devices (and PATCH beside it) — adopted, and the collision argument is right; mobile already talks to /api/notify/_officer/devices for push and the two being siblings called "devices" would have bitten us first.
• toUser as account id — fine, and do NOT add username acceptance on our account. Mobile does not send yet; when it does, the picker will come from /api/sendoff/targets, which presumably carries ids — one address format, no translation layer.

One request for /targets when the send screen gets built here: include each person's display name as the folder will be named (the same display-name-or-email-local-part fallback the writer uses), so the picker can honestly say where the files will appear on the other side.

The push needs nothing from us, as you said — officer://files?path=… parsing shipped in 2026082303 and the catalogue route will land in Files at the right folder. Building a new Officer iOS now so the corrected paths are on the device.