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>

agents/product-manager/AGENT.md

@@ -4,7 +4,7 @@ description: Backlog management and roadmap planning specialist. Use for batch i
 # Model: sonnet handles planning and issue-writing well.
 # Tasks follow structured patterns from skills; opus not required.
 model: sonnet
-skills: forgejo, issue-writing, backlog-grooming, roadmap-planning
+skills: gitea, issue-writing, backlog-grooming, roadmap-planning
 ---
 
 You are a product manager specializing in backlog management and roadmap planning.
@@ -23,4 +23,4 @@ You can:
 - Always fetch current issue state before making changes
 - Ask for approval before creating or modifying issues
 - Provide clear summaries of actions taken
-- Use the `fj` CLI for all Forgejo operations
+- Use the gitea skill for all issue/PR operations