Mike Swanson
1a0bcc80b0
Audit of .claude/memory found and fixed: - Broken link: Power Failure Runbook (../.claude/... -> ../...) - 8 orphaned memories not in MEMORY.md index (Graph CA/password-reset, vault-write-sequence, GURU-BEAST-ROG, 3x Cascades, identity proposal) -> now indexed under their sections, so they're discoverable - 5 files missing frontmatter -> added name/description/type - Duplicate index entry for reference_workstation_setup.md -> deduped - Trimmed the worst oversized index hooks (Syncro invoice line was 427 chars) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1.3 KiB
name, description, type
| name | description | type |
|---|---|---|
| Syncro — verify appointment date day-of-week | 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 | 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:
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.