sync: auto-sync from GURU-5070 at 2026-06-02 07:25:49
Author: Mike Swanson Machine: GURU-5070 Timestamp: 2026-06-02 07:25:49
This commit is contained in:
31
.claude/memory/feedback_syncro_appointment_date_check.md
Normal file
31
.claude/memory/feedback_syncro_appointment_date_check.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
name: Syncro — verify appointment date day-of-week
|
||||
description: Before creating any Syncro appointment, verify the computed date falls on the intended weekday (py datetime) and show the day name in the preview. Wrong-day incident #32312 2026-05-21.
|
||||
type: feedback
|
||||
---
|
||||
|
||||
# Syncro — Verify appointment date day-of-week before creating
|
||||
|
||||
**Rule:** Before creating any Syncro appointment, always verify that the computed date
|
||||
actually falls on the intended day of the week.
|
||||
|
||||
**Why:** Day-of-week math is easy to get wrong. In the incident that prompted this rule
|
||||
(2026-05-21, ticket #32312), "Saturday" was computed as May 24 — which is actually a Sunday.
|
||||
The appointment landed on the wrong day and didn't appear where Winter expected it on the calendar.
|
||||
|
||||
**How to verify:**
|
||||
|
||||
Use Python or Bash to print the weekday before including it in the preview:
|
||||
|
||||
```bash
|
||||
py -c "import datetime; d = datetime.date(2026, 5, 24); print(d.strftime('%A %Y-%m-%d'))"
|
||||
# Output: Sunday 2026-05-24 ← would have caught the error
|
||||
```
|
||||
|
||||
Or include the day name in the TICKET PREVIEW and require explicit user confirmation
|
||||
that the day-of-week matches their intent.
|
||||
|
||||
**Catch:** Always show `Day YYYY-MM-DD` (e.g., "Saturday 2026-05-23") in the preview —
|
||||
never just the numeric date — so the user can verify at a glance.
|
||||
|
||||
Reported by Winter, 2026-05-21.
|
||||
Reference in New Issue
Block a user