Task #311. The schedule view hides cancelled meetings, but the drag-reorder
path was operating on the raw, unfiltered list — so cancelled rows consumed
time slots and the dnd-kit indices skewed across hidden rows, leaving the
visible list out of chronological order after a drop.
Server (POST /api/executive-meetings/reorder)
- Slot-swap now operates on the in-scope (orderedIds) subset only.
Cancelled rows keep their (startTime, endTime, dailyNumber) untouched, so
they no longer steal slots from the visible list.
- New 400 codes:
- cancelled_in_reorder: payload includes a cancelled meeting
- incomplete_day: any non-cancelled meeting on the day is missing
- Audit oldValue.order now reflects the visible order the user actually saw.
- Phase-1/phase-2 negative-parking still avoids transient unique-constraint
conflicts; cancelled rows' positive dailyNumbers cannot collide because
slot dailyNumbers are a permutation of in-scope rows' existing values.
Client (executive-meetings.tsx reorderRows)
- Index math now derives ids from `orderedMeetings` (the visible list bound
to SortableContext) instead of the raw `meetings` array. useCallback deps
updated.
Tests
- artifacts/api-server/tests/executive-meetings.test.mjs: added
"leaves cancelled rows untouched and only slot-swaps visible meetings",
"rejects orderedIds containing a cancelled meeting", and
"handles a day with a null-startTime meeting deterministically".
- artifacts/tx-os/tests/executive-meetings-keyboard-editing.spec.mjs: added
"Schedule drag-reorder: cancelled rows on the same day do not disturb the
visible chronological order" (drives reorder via authenticated fetch since
dnd-kit pixel drag is unreliable in headless).
Code-review follow-ups addressed:
- Reverted unrelated artifacts/tx-os/public/opengraph.jpg binary change.
- Added the explicit null-startTime reorder regression requested in review.
- The remaining review note (perform an actual pixel drag end-to-end) is
intentionally not implemented: dnd-kit's drag gesture is unreliable in
headless Playwright; the contract is fully covered by the API tests and
the fetch-based UI test.
All 8 reorder tests pass. Other failing api-server tests
(create meeting → 500) are pre-existing sanitize regressions tracked
under follow-up #309 and are out of scope here.
Riyadh
c4e650bd7b