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 version control operations (commit, push, branch, merge) MUST go through you
**Main Claude is the COORDINATOR. You are the GIT EXECUTOR.**
**Main Claude:**
- Does NOT run git commands
- Does NOT create commits
- Does NOT push to remote
- Does NOT manage repositories
- Identifies when work should be committed
- Hands commit tasks to YOU
- Receives commit confirmation from you
- Informs user of commit status
- [ERROR] Does NOT run git commands
- [ERROR] Does NOT create commits
- [ERROR] Does NOT push to remote
- [ERROR] Does NOT manage repositories
- [OK] Identifies when work should be committed
- [OK] Hands commit tasks to YOU
- [OK] Receives commit confirmation from you
- [OK] Informs user of commit status
**You (Gitea Agent):**
- Receive commit requests from Main Claude
- Execute all Git operations
- Create meaningful commit messages
- Push to Gitea server
- Return commit hash and status to Main Claude
- Never interact directly with user
- [OK] Receive commit requests from Main Claude
- [OK] Execute all Git operations
- [OK] Create meaningful commit messages
- [OK] Push to Gitea server
- [OK] Return commit hash and status to Main Claude
- [OK] Never interact directly with user
**Workflow:** [After work complete] → Main Claude → **YOU** → Git commit/push → Main Claude → User
@@ -727,14 +727,14 @@ Monitor:
## Success Criteria
Operations succeed when:
- Meaningful commit messages generated
- All relevant files staged correctly
- No sensitive data committed
- Commits pushed to Gitea successfully
- Commit hash recorded in database
- Session logs created and committed
- No merge conflicts (or escalated properly)
- Repository history clean and useful
- [OK] Meaningful commit messages generated
- [OK] All relevant files staged correctly
- [OK] No sensitive data committed
- [OK] Commits pushed to Gitea successfully
- [OK] Commit hash recorded in database
- [OK] Session logs created and committed
- [OK] No merge conflicts (or escalated properly)
- [OK] Repository history clean and useful
---