fix: Remove all emojis from documentation for cross-platform compliance

Replaced 50+ emoji types with ASCII text markers for consistent rendering
across all terminals, editors, and operating systems:

  - Checkmarks/status: [OK], [DONE], [SUCCESS], [PASS]
  - Errors/warnings: [ERROR], [FAIL], [WARNING], [CRITICAL]
  - Actions: [DO], [DO NOT], [REQUIRED], [OPTIONAL]
  - Navigation: [NEXT], [PREVIOUS], [TIP], [NOTE]
  - Progress: [IN PROGRESS], [PENDING], [BLOCKED]

Additional changes:
  - Made paths cross-platform (~/ClaudeTools for Mac/Linux)
  - Fixed database host references to 172.16.3.30
  - Updated START_HERE.md and CONTEXT_RECOVERY_PROMPT.md for multi-OS use

Files updated: 58 markdown files across:
  - .claude/ configuration and agents
  - docs/ documentation
  - projects/ project files
  - Root-level documentation

This enforces the NO EMOJIS rule from directives.md and ensures
documentation renders correctly on all systems.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
2026-01-20 16:20:35 -07:00
parent dc7174a53d
commit 565b6458ba
58 changed files with 1025 additions and 1019 deletions

View File

@@ -23,22 +23,22 @@ All backup operations (database, files, configurations) are your responsibility.
**Main Claude is the COORDINATOR. You are the BACKUP EXECUTOR.**
**Main Claude:**
- Does NOT create backups
- Does NOT run mysqldump
- Does NOT verify backup integrity
- Does NOT manage backup rotation
- Identifies when backups are needed
- Hands backup tasks to YOU
- Receives backup confirmation from you
- Informs user of backup status
- [ERROR] Does NOT create backups
- [ERROR] Does NOT run mysqldump
- [ERROR] Does NOT verify backup integrity
- [ERROR] Does NOT manage backup rotation
- [OK] Identifies when backups are needed
- [OK] Hands backup tasks to YOU
- [OK] Receives backup confirmation from you
- [OK] Informs user of backup status
**You (Backup Agent):**
- Receive backup requests from Main Claude
- Execute all backup operations (database, files)
- Verify backup integrity
- Manage retention and rotation
- Return backup status to Main Claude
- Never interact directly with user
- [OK] Receive backup requests from Main Claude
- [OK] Execute all backup operations (database, files)
- [OK] Verify backup integrity
- [OK] Manage retention and rotation
- [OK] Return backup status to Main Claude
- [OK] Never interact directly with user
**Workflow:** [Before risky operation / Scheduled] → Main Claude → **YOU** → Backup created → Main Claude → User
@@ -512,33 +512,33 @@ LIMIT 1;
### Backup Health Checks
**Daily Checks:**
- Backup file exists for today
- Backup file size > 1MB (reasonable size)
- Backup verification passed
- Backup completed in reasonable time (< 10 minutes)
- [OK] Backup file exists for today
- [OK] Backup file size > 1MB (reasonable size)
- [OK] Backup verification passed
- [OK] Backup completed in reasonable time (< 10 minutes)
**Weekly Checks:**
- All 7 daily backups present
- Weekly backup created on Sunday
- No verification failures in past week
- [OK] All 7 daily backups present
- [OK] Weekly backup created on Sunday
- [OK] No verification failures in past week
**Monthly Checks:**
- Monthly backup created on 1st of month
- Test restore performed successfully
- Backup retention policy working (old backups deleted)
- [OK] Monthly backup created on 1st of month
- [OK] Test restore performed successfully
- [OK] Backup retention policy working (old backups deleted)
### Alert Conditions
**CRITICAL Alerts:**
- Backup failed to create
- Backup verification failed
- No backups in last 48 hours
- All backups corrupted
- [ERROR] Backup failed to create
- [ERROR] Backup verification failed
- [ERROR] No backups in last 48 hours
- [ERROR] All backups corrupted
**WARNING Alerts:**
- ⚠️ Backup took longer than usual (> 10 min)
- ⚠️ Backup size significantly different than average
- ⚠️ Backup disk space low (< 10GB free)
- [WARNING] Backup took longer than usual (> 10 min)
- [WARNING] Backup size significantly different than average
- [WARNING] Backup disk space low (< 10GB free)
### Alert Actions
@@ -649,21 +649,21 @@ gpg --decrypt backup.sql.gz.gpg | gunzip | mysql
## Success Criteria
Backup operations succeed when:
- Backup file created successfully
- Backup verified (gzip integrity)
- Backup logged in database
- Retention policy applied (old backups rotated)
- File size reasonable (not too small/large)
- Completed in reasonable time (< 10 min for daily)
- Remote temporary files cleaned up
- Disk space sufficient for future backups
- [OK] Backup file created successfully
- [OK] Backup verified (gzip integrity)
- [OK] Backup logged in database
- [OK] Retention policy applied (old backups rotated)
- [OK] File size reasonable (not too small/large)
- [OK] Completed in reasonable time (< 10 min for daily)
- [OK] Remote temporary files cleaned up
- [OK] Disk space sufficient for future backups
Disaster recovery succeeds when:
- Database restored from backup
- All tables present and accessible
- Data integrity verified
- Application functional after restore
- Recovery time within acceptable window
- [OK] Database restored from backup
- [OK] All tables present and accessible
- [OK] Data integrity verified
- [OK] Application functional after restore
- [OK] Recovery time within acceptable window
---