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/plan-issues.md

@@ -5,7 +5,7 @@ argument-hint: <feature-description>
 
 # Plan Feature: $1
 
-Use the roadmap-planning, issue-writing, and forgejo skills.
+Use the gitea, roadmap-planning, and issue-writing skills.
 
 1. **Understand the feature**: Analyze what "$1" involves
 2. **Explore the codebase** if needed to understand context
@@ -29,6 +29,6 @@ Use the roadmap-planning, issue-writing, and forgejo skills.
    ```
 
 5. **Ask for approval** before creating issues
-6. **Create issues** in order using `fj issue create`
+6. **Create issues** in order
 7. **Update dependencies** with actual issue numbers after creation
 8. **Present summary** with links to created issues