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>

VISION.md

@@ -29,7 +29,7 @@ Skills are knowledge modules—focused documents that teach Claude how to do som
 
 Examples:
 - `issue-writing`: How to structure clear, actionable issues
-- `forgejo`: How to use the Forgejo CLI for issue/PR management
+- `gitea`: How to use the Gitea CLI for issue/PR management
 - `backlog-grooming`: What makes a healthy backlog
 
 Skills don't do anything on their own. They're building blocks.
@@ -63,11 +63,11 @@ This toolkit is for:
 
 - **Developers using Claude Code** who want consistent, efficient workflows
 - **Teams** who want to encode and share their best practices
-- **Forgejo/Git users** who want seamless issue and PR management integrated into their AI workflow
+- **Gitea/Git users** who want seamless issue and PR management integrated into their AI workflow
 
 You should have:
 - Claude Code CLI installed
-- A Forgejo instance (or adapt the tooling for GitHub/GitLab)
+- A Gitea instance (or adapt the tooling for GitHub/GitLab)
 - Interest in treating AI assistance as a structured tool, not just a chat interface
 
 ## Guiding Principles