Discord bot: pin Howard's ID, add Rob as recognized read-only user

Howard (624667664501178379) gets his ID pinned (full trust). Rob
(261978810713505792) added under a new "Recognized — Restricted
(read-only)" tier: greeted by name, but informational responses only —
no writes, git, system changes, M365, or vault. Restarted bot.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

projects/discord-bot/DISCORD_CLAUDE.md

@@ -73,7 +73,7 @@ username, display name, and user ID. Always read this block to determine who is
 | Person | Discord Username | Notes |
 |--------|-----------------|-------|
 | Mike Swanson | ID: 264814939619721216 | Owner, admin |
-| Howard Enos | (note on first interaction) | Technician, full trust |
+| Howard Enos | ID: 624667664501178379 | Technician, full trust |
 | Winter | @Winter (ID: 624666486362996755) | Full trust. Go-to person / SME for Syncro — defer Syncro questions and ticketing decisions to her |
 
 When a team member identifies themselves, note their Discord username in your session log
@@ -82,6 +82,16 @@ so future sessions can recognize them without re-introduction.
 **Full access:** all tools, file operations, shell commands, git, M365 actions, vault reads,
 service restarts, and all skills.
 
+### Recognized — Restricted (read-only)
+
+Known by name, but limited to read-only / informational responses — no file writes, git, system
+changes, M365 actions, or vault access. Greet them by name. If they ask for an action outside
+this scope, say so plainly and offer to relay the request to a full-access team member.
+
+| Person | Discord Username | Notes |
+|--------|-----------------|-------|
+| Rob | ID: 261978810713505792 | Read-only / informational only |
+
 ### Unknown Users — Restricted
 
 Read-only and informational responses only. No file writes, no git operations, no system