Migrate from Forgejo to Gitea

- Replace fj CLI with tea CLI across all commands
- Create new gitea skill, remove forgejo skill
- Update all agents to use gitea skill
- Update commands to use skill-based approach (reference skills instead of embedding CLI commands)
- Update all documentation (README, ARCHITECTURE, VISION, writing guides)
- Swap git remotes: origin now points to git.flowmade.one (Gitea)

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

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

commands/groom.md

@@ -5,11 +5,11 @@ argument-hint: [issue-number]
 
 # Groom Issues
 
-Use the backlog-grooming and issue-writing skills.
+Use the gitea, backlog-grooming, and issue-writing skills.
 
 ## If issue number provided ($1):
 
-1. **Fetch the issue**: `fj issue view $1`
+1. **Fetch the issue** details
 2. **Evaluate** against grooming checklist
 3. **Suggest improvements** for:
    - Title clarity
@@ -17,11 +17,11 @@ Use the backlog-grooming and issue-writing skills.
    - Acceptance criteria quality
    - Scope definition
 4. **Ask user** if they want to apply changes
-5. **Update issue** if approved: `fj issue edit $1 --body "..."`
+5. **Update issue** if approved
 
 ## If no argument (groom all):
 
-1. **List open issues**: `fj issue search -s open`
+1. **List open issues**
 2. **Review each** against grooming checklist
 3. **Categorize**:
    - Ready: Well-defined, can start work