Remove emojis from all markdown docs, add consolidation plan

- Strip emojis from 47 markdown files across docs/, sql/, and root
- Add docs/DOCS_CONSOLIDATION_PLAN.md with plan to reduce 45 docs to 8
- Establish no-emoji rule for documentation going forward

🤖 Generated with [Claude Code](https://claude.com/claude-code)

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

docs/INFRASTRUCTURE_FINAL_ARCHITECTURE.md

@@ -23,9 +23,9 @@ idfs:
 cameras:
   - cameraid INT(11) PK
   - modelid INT(11) → models.modelnumberid → vendors
-  - idfid INT(11) → idfs.idfid ✅ Already has parent!
+  - idfid INT(11) → idfs.idfid  Already has parent!
   - serialnumber VARCHAR(100)
-  - macaddress VARCHAR(17) ✅ Camera-specific
+  - macaddress VARCHAR(17)  Camera-specific
   - ipaddress VARCHAR(45)
   - description VARCHAR(255)
   - maptop, mapleft INT(11)
@@ -382,13 +382,13 @@ Response.Write("];")
 
 ## Summary: Why This Approach?
 
-✅ **Hierarchical relationships** - Cameras/switches belong to IDFs
-✅ **Type-specific fields** - MAC address for cameras, idfname for IDFs
-✅ **Flexible** - Can add more fields per type later
-✅ **Clean data model** - Proper normalization
-✅ **Unified list view** - See all infrastructure in one place
-✅ **Type-specific edit** - Appropriate fields per device type
-✅ **Map integration** - All devices can be mapped
+ **Hierarchical relationships** - Cameras/switches belong to IDFs
+ **Type-specific fields** - MAC address for cameras, idfname for IDFs
+ **Flexible** - Can add more fields per type later
+ **Clean data model** - Proper normalization
+ **Unified list view** - See all infrastructure in one place
+ **Type-specific edit** - Appropriate fields per device type
+ **Map integration** - All devices can be mapped
 
 **Total Files:** 7 ASP files (1 list + 4 detail + 1 add + 1 save)