sanitize: Remove personal information from bug reports before production

Redacted:
- User names (Christopher → User)
- Home address (156 Cedar Street → <address>)
- Family member names (Gabby/Cyrus/Des → <child_name>)
- Domain names (helpdeskpro.ca → <domain>)
- User UUIDs (10d7d879-... → <user_uuid>)
- Test data (replaced with generic placeholders)

dBug-025, dBug-026 now safe for production release.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>

Author: tkalevra

BUGS/dBug-025-entity-duplication-blocks-taxonomy-filtering.md

@@ -4,19 +4,19 @@
 
 **Status:** CONFIRMED (validated via pre-prod database inspection 2026-05-15)
 
-**User Context:** Christopher, user_id=`10d7d879-63cd-4f31-92ce-f2c9edb760ab`
+**User Context:** User, user_id=`<user_uuid>`
 
 ## Problem Summary
 
 User query: `"Tell me about my family"`
 
-Expected response: Only Person + Animal entities (Gabby, Cyrus, Des, Mars, Aurora)
+Expected response: Only Person + Animal entities (<child_name>, <child_name>, <child_name>, <spouse>, Aurora)
 
 Actual response: Mixed entities including:
-- Addresses (156 Cedar Street S) — Location type
-- Servers (aurora.helpdeskpro.ca, titan.helpdeskpro.ca) — unknown type, no filtering possible
+- Addresses (<address>) — Location type
+- Servers (aurora.<domain>, titan.<domain>) — unknown type, no filtering possible
 - Garbage entities (computer, domain_name, son, it) — type labels and pronouns mistaken for entities
-- Duplicate/orphaned string-ID entities (cyrus, des, gabby) — entity_type=unknown
+- Duplicate/orphaned string-ID entities (<child_name>, <child_name>, <child_name>) — entity_type=unknown
 
 Response feels "stalkerish" because PII leaks and infrastructure noise mixed with family relationships.
 
@@ -26,23 +26,23 @@ Response feels "stalkerish" because PII leaks and infrastructure noise mixed wit
 
 ### Family Members (Duplicated)
 ```
-Entity: Cyrus
-├─ UUID-based: 55c13545-3f9a-5798-8827-c35e7c9cfa70
+Entity: <child_name>
+├─ UUID-based: <entity_uuid>
 │  └─ entity_type = Person ✓ (correct, filterable)
-│  └─ facts: pref_name="cyrus" (confidence 1.0)
+│  └─ facts: pref_name="<child_name>" (confidence 1.0)
 │
-└─ String-ID-based: "cyrus" (display name as entity ID)
+└─ String-ID-based: "<child_name>" (display name as entity ID)
    └─ entity_type = unknown ✗ (can't filter by taxonomy)
    └─ alias in entity_aliases (is_preferred=false, orphaned)
 
-Similar duplication for: Gabby, Des, Mars, Aurora
+Similar duplication for: <child_name>, <child_name>, <spouse>, Aurora
 ```
 
 ### Garbage Entities (Misclassified)
 ```
 Unclassified (entity_type=unknown):
-- aurora.helpdeskpro.ca (should be Object, not entity)
-- titan.helpdeskpro.ca (should be Object, not entity)
+- aurora.<domain> (should be Object, not entity)
+- titan.<domain> (should be Object, not entity)
 - "computer" (type label, not entity)
 - "domain_name" (type label, not entity)
 - "it" (pronoun, should not be entity)
@@ -57,31 +57,31 @@ Addresses: entity_type=Location ✓ (correct type, but no filtering in /query)
 ## Evidence (Pre-Prod Database)
 
 ```sql
--- Entity duplication for "cyrus"
+-- Entity duplication for "<child_name>"
 SELECT id, entity_type FROM entities 
-WHERE user_id='10d7d879-63cd-4f31-92ce-f2c9edb760ab' 
-AND (id='55c13545-3f9a-5798-8827-c35e7c9cfa70' OR id='cyrus');
+WHERE user_id='<user_uuid>' 
+AND (id='<entity_uuid>' OR id='<child_name>');
 
 Result:
-55c13545-3f9a-5798-8827-c35e7c9cfa70 | Person
-cyrus                                  | unknown
+<entity_uuid> | Person
+<child_name>                                  | unknown
 ```
 
 ```sql
 -- Facts showing both UUID and string-ID references
 SELECT subject_id, rel_type, object_id FROM facts 
-WHERE user_id='10d7d879-63cd-4f31-92ce-f2c9edb760ab' 
+WHERE user_id='<user_uuid>' 
 AND rel_type='pref_name' 
-AND object_id IN ('cyrus', 'des', 'gabby', 'aurora');
+AND object_id IN ('<child_name>', '<child_name>', '<child_name>', 'aurora');
 
 Result: Multiple facts with string object_ids instead of UUID consolidation
 ```
 
 ```sql
 -- Garbage entities
 SELECT id, entity_type FROM entities 
-WHERE user_id='10d7d879-63cd-4f31-92ce-f2c9edb760ab' 
-AND id IN ('computer', 'domain_name', 'it', 'son', 'aurora.helpdeskpro.ca');
+WHERE user_id='<user_uuid>' 
+AND id IN ('computer', 'domain_name', 'it', 'son', 'aurora.<domain>');
 
 Result: All entity_type=unknown (can't be filtered)
 ```
@@ -94,8 +94,8 @@ Result: All entity_type=unknown (can't be filtered)
 
 **Current filtering doesn't work because:**
 
-1. String-ID entities (cyrus, gabby, des) have entity_type=unknown → not excluded
-2. Garbage entities (computer, domain_name, aurora.helpdeskpro.ca) have entity_type=unknown → not excluded
+1. String-ID entities (<child_name>, <child_name>, <child_name>) have entity_type=unknown → not excluded
+2. Garbage entities (computer, domain_name, aurora.<domain>) have entity_type=unknown → not excluded
 3. Address entities have entity_type=Location, which is correct type but still appears in results (no query-side filtering applied)
 
 Result: `/query` returns UUID-based facts (Person-typed, pass filter) + String-ID facts (unknown-typed, can't filter) + unfiltered Location facts.
@@ -132,7 +132,7 @@ When Filter injects these, user sees noise alongside family relationships.
    - Are string-ID entities intended as "fallback" representations?
 
 3. **Trace pref_name/also_known_as ingestion:**
-   - When `/ingest` creates a pref_name fact with string object (e.g., `(uuid, pref_name, "cyrus")`), does it also create entity_id="cyrus"?
+   - When `/ingest` creates a pref_name fact with string object (e.g., `(uuid, pref_name, "<child_name>")`), does it also create entity_id="<child_name>"?
    - Should it?
 
 4. **Identify garbage entity creation:**

BUGS/dBug-026-class-c-routing-verification-incomplete.md

@@ -6,13 +6,13 @@
 
 **Date:** 2026-05-15
 
-**User Context:** Christopher, test user 10d7d879-63cd-4f31-92ce-f2c9edb760ab
+**User Context:** User, test user <user_uuid>
 
 ## Summary
 
 **DEEPSEEK-27A implementation complete** (dprompt-88 edge logging + Class C routing).
 
-**Testing via hairbrush.helpdeskpro.ca (OpenWebUI Filter):**
+**Testing via hairbrush.<domain> (OpenWebUI Filter):**
 
 ✅ **Rejection logging working:**
 ```
@@ -49,7 +49,7 @@ entity_registry.resolve_rejected name=very reason='failed entity name validation
 **Pre-prod database query (2026-05-15 23:00 UTC):**
 ```sql
 SELECT COUNT(*) FROM staged_facts 
-WHERE user_id='10d7d879-63cd-4f31-92ce-f2c9edb760ab' 
+WHERE user_id='<user_uuid>' 
 AND fact_class='C';
 -- Result: 0 rows
 ```