2026-10-05 (Dustin’s ask; implementation choices by Claude, stated in the session summary): changing a site visit’s assigned inspector is an Unlikely owner/admin action from the project page’s site-visit section, and it notifies on the write itself — no confirmation prompt like the time-change flow, because the ask was “any changes should notify the affected inspectors”. Both inspectors (the one losing the stop, the one taking it) are named on ONE field NOTICE; Slack only, no SMS (the ask named the field channel). The board is corrected only where it is now wrong: a same-day hand-off re-posts the whole day (the established “resend everything in the correct order” shape), tomorrow’s preview is re-posted once it has gone out, later days get the NOTICE alone. Visits nobody drives are reassigned silently: same inspector, past date, completed/cancelled/no-show, desk review, tentative Week Board visit. An unassigned visit counts as Darius’s (unassigned stops ride his list). Open: the Route Board’s apply-move still hands a stop across techs with no notice (chip task_e54d56d0); a combined NOTICE when a move changes both time and inspector.
2026-10-05 (later the same day; entirely-api 475ae07 + entirely-portal a12fec1, deployed ~07:55 ET): the open Route Board gap is CLOSED — POST /portal/scheduling/apply-move pre-reads the visit, writes date + tech, then awaits field_schedule_change.send_reassignment(new_start=…): ONE combined field NOTICE to both inspectors (“TODAY’S 11:30 AM APPT. REASSIGNED FROM DARIUS TO DUSTIN AND MOVED TO 4:15 PM”) and the board re-posted once (card marked “reassigned from Darius · moved from 11:30 AM”); response/audit carry reassignment incl. moved_from; the Route Board shows the outcome line and withholds its day-of/tomorrow time-change prompt when that notice covered the same board (reassignCoversRouteChange). Provisional choice by Claude, for Dustin to confirm: one combined notice rather than reassignment NOTICE + time-change NOTICE (the latter also pages Darius by SMS, which the reassignment ask ruled out); to flip to “both fire”, drop the reassignCoversRouteChange guard in RouteBoard.tsx (API unchanged). Same-inspector moves unchanged (prompt on confirm). Cross-day hand-offs (never produced by the Route Board) leave the old day’s board uncorrected. First real send not yet exercised.
2026-10-05 08:30 ET RULING (Dustin): keep the combined notice — a cross-tech Route Board move posts ONE NOTICE (reassigned + moved) and the time-change NOTICE does not also fire; the provisional status is lifted. First real send: Dustin cleared it, but the week’s engine suggestions were all same-day time moves (no cross-tech hand-off), and of the three real hand-offs Claude offered (MAN-9230 Tue 1 PM, MAN-9248 Fri 1 PM, MAN-9253 today 12 PM, each Darius → Dustin) he chose “none, wait for a real one” — nothing was written or posted; the first real send happens when Dustin hands a stop over himself from the Route Board or the project page.