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>

skills/backlog-grooming/SKILL.md

@@ -60,11 +60,13 @@ If issue covers multiple features, split into separate issues.
 
 ## Grooming Workflow
 
-1. **Fetch open issues**: `fj issue search -s open`
+Use the gitea skill for issue operations.
+
+1. **Fetch open issues**
 2. **Review each issue** against checklist
 3. **Improve or flag** issues that need work
-4. **Update issue** with improvements: `fj issue edit <n> --body "..."`
-5. **Add labels** as needed: `fj issue label add <n> <label>`
+4. **Update issue** with improvements
+5. **Add labels** as needed
 
 ## Questions to Ask