azcomputerguru/claudetools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(memory): consolidate scattered feedback/project/reference files

Browse Source 
Compressed memory store 104 -> 71 files via four passes:

- Syncro: 19 scattered feedback_syncro_* files merged into 3 rule files
  (api/billing/workflow) + an on-demand feedback_syncro_history.md for
  incident detail, quotes, and tech/product ID tables.
- Four near-duplicate merges: Howard paste-safety, Pluto build server,
  Howard backend deferral, IX server access (ssh+tailscale).
- Per-cluster rule/state/history split applied to GuruConnect (2->1),
  Dataforth (3->2), Cascades (7->3), GuruRMM (13->3).
- New reference_resource_map.md: single auto-loaded cheatsheet for
  "do I have access to X and how do I connect from this machine?"
- MEMORY.md rewritten to match the new layout.

Health: broken backlinks 8->7, overlap clusters 12->5, orphans 17->0.
This commit is contained in:
Mike Swanson
2026-06-01 16:25:45 -07:00
parent 2a1ccfac73
commit 0c000109dc
75 changed files with 1473 additions and 1324 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
.claude/memory/feedback_syncro_appointment_date_check.md
View File

@@ -1,31 +0,0 @@
---
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.