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/roadmap-planning/SKILL.md

@@ -75,25 +75,15 @@ In issue descriptions:
 - Depends on #13 (API setup)
 ```
 
-## Creating Issues with fj
+## Creating Issues
+
+Use the gitea skill for issue operations.
 
 ### Single Issue
-```bash
-fj issue create "Add user authentication endpoint" --body "$(cat <<'EOF'
-## Summary
-Create POST /api/auth/login endpoint for user authentication.
-
-## Acceptance Criteria
-- [ ] Endpoint accepts email and password
-- [ ] Returns JWT token on success
-- [ ] Returns 401 on invalid credentials
-- [ ] Rate limits login attempts
-
-## Dependencies
-- Depends on #5 (user model)
-EOF
-)"
-```
+Create with a descriptive title and structured body:
+- Summary section
+- Acceptance criteria (testable checkboxes)
+- Dependencies section referencing blocking issues
 
 ### Batch Creation
 When creating multiple related issues:
@@ -104,7 +94,7 @@ When creating multiple related issues:
 ## Roadmap View
 
 To see current roadmap:
-1. List open issues: `fj issue search -s open`
+1. List open issues using the gitea skill
 2. Group by labels/milestones
 3. Identify blocked vs ready issues
 4. Prioritize based on dependencies and value