sync: auto-sync from GURU-BEAST-ROG at 2026-06-02 10:44:23

Author: Mike Swanson
Machine: GURU-BEAST-ROG
Timestamp: 2026-06-02 10:44:23

projects/discord-bot/DISCORD_CLAUDE.md

@@ -73,6 +73,23 @@ drive the human's interactive session.
 
 ---
 
+## Pricing — Always Verify, Never Guess
+
+**MANDATORY:** Before presenting any cost to Mike, Howard, or a client, verify current pricing
+via live web lookup. Never estimate or recall costs from training data — hardware prices,
+software licensing, and labor rates change constantly.
+
+Rules:
+- Any dollar amount for hardware, parts, software, or services requires a real-time lookup
+  before being stated.
+- Use WebFetch / WebSearch first. Fall back to headless Chrome if bot-blocked.
+- Cite the source and date: `[$X.XX — Amazon, 2026-06-02]`
+- If you cannot reach a pricing source, say so explicitly — do NOT substitute a guess.
+- Applies to all estimate types: parts, repair quotes, hardware refreshes, software licensing,
+  labor, and third-party services.
+
+---
+
 ## Task Loop
 
 For every request, work this loop:
@@ -86,13 +103,41 @@ For every request, work this loop:
 4. **Offer Syncro** — once they have nothing else, ask whether to log the work in Syncro
    ("Want me to log this in Syncro?"). If yes, invoke `/syncro` to create or update the ticket.
 5. **Save** — after the loop closes, run `/save` to write the session log and sync the repo.
+6. **Kill the thread** — after `/save` completes successfully, delete the thread:
+   ```bash
+   bash C:/Users/guru/ClaudeTools/projects/discord-bot/scripts/delete-thread.sh <Thread ID>
+   ```
+   The Thread ID is in every `[DISCORD_CONTEXT]` block as `Thread ID: <id>`. Do not delete
+   if `/save` failed or errored. Do not post a closing message — the deletion is immediate.
+
+---
+
+## Thread Lifecycle — Auto-Delete on Completion
+
+Every `[DISCORD_CONTEXT]` block now includes `Thread ID: <id>` (injected by the bot after
+the thread is resolved or created). This ID is what you pass to the delete script.
+
+**When to delete:** Only after step 6 of the Task Loop — `/save` succeeded, session log
+committed and pushed. The thread is the conversation record; don't kill it before the log lands.
+
+**When NOT to delete:**
+- `/save` failed or sync errored
+- The user said "yes" to continuing (open follow-up items remain)
+- The thread is an ongoing informational channel, not a single-task session
+
+**Script:**
+```bash
+bash C:/Users/guru/ClaudeTools/projects/discord-bot/scripts/delete-thread.sh <Thread ID>
+```
+Source: `projects/discord-bot/scripts/delete-thread.sh` — reads bot token from `.env`, calls
+`DELETE /channels/{id}` on the Discord API. Exits 0 on HTTP 200/204, 1 on error.
 
 ---
 
 ## Who Is Asking: Discord User Identity
 
 Every message is prefixed with a `[DISCORD_CONTEXT]` block containing the sender's Discord
-username, display name, and user ID. Always read this block to determine who is asking.
+username, display name, user ID, and Thread ID. Always read this block to determine who is asking.
 
 ### Known Team Members — Full Access