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>

docs/writing-agents.md

@@ -78,7 +78,7 @@ Agents gain their expertise by combining multiple skills. Each skill contributes
 │           Product Manager Agent                │
 │                                                │
 │  ┌──────────┐  ┌──────────────┐                │
-│  │ forgejo  │  │issue-writing │                │
+│  │ gitea  │  │issue-writing │                │
 │  │          │  │              │                │
 │  │ CLI      │  │ Structure    │                │
 │  │ commands │  │ patterns     │                │
@@ -95,7 +95,7 @@ Agents gain their expertise by combining multiple skills. Each skill contributes
 ```
 
 The agent can:
-- Use **forgejo** to interact with issues and PRs
+- Use **gitea** to interact with issues and PRs
 - Apply **issue-writing** patterns when creating content
 - Follow **backlog-grooming** checklists when reviewing
 - Use **roadmap-planning** strategies when breaking down features
@@ -106,9 +106,9 @@ When skills combine, new capabilities emerge:
 
 | Skills Combined | Emergent Capability |
 |-----------------|---------------------|
-| forgejo + issue-writing | Create well-structured issues programmatically |
+| gitea + issue-writing | Create well-structured issues programmatically |
 | backlog-grooming + issue-writing | Improve existing issues systematically |
-| roadmap-planning + forgejo | Plan and create linked issue hierarchies |
+| roadmap-planning + gitea | Plan and create linked issue hierarchies |
 | All four skills | Full backlog management lifecycle |
 
 ## Use Cases for Agents
@@ -225,7 +225,7 @@ Command spawns product-manager agent
 |----------|--------|--------|
 | Create one issue | No | Single skill, simple task |
 | Review 20 issues | Yes | Batch processing, isolation |
-| Quick CLI lookup | No | Just need forgejo reference |
+| Quick CLI lookup | No | Just need gitea reference |
 | Plan new feature | Yes | Multiple skills, exploration |
 | Fix issue title | No | Trivial edit |
 | Reorganize backlog | Yes | Complex, multi-skill workflow |
@@ -245,14 +245,14 @@ Specialized agent for backlog management and roadmap planning.
 ```markdown
 ## Skills
 
-- forgejo
+- gitea
 - issue-writing
 - backlog-grooming
 - roadmap-planning
 ```
 
 **Skills section** lists all knowledge the agent has access to. These skills are loaded into the agent's context when spawned. The combination enables:
-- Reading/writing issues (forgejo)
+- Reading/writing issues (gitea)
 - Creating quality content (issue-writing)
 - Evaluating existing issues (backlog-grooming)
 - Planning work strategically (roadmap-planning)
@@ -270,7 +270,7 @@ This agent can:
 
 **Capabilities section** tells spawners what to expect. Each capability maps to skill combinations:
 - "Review and improve" = backlog-grooming + issue-writing
-- "Create new issues" = forgejo + issue-writing
+- "Create new issues" = gitea + issue-writing
 - "Analyze backlog" = backlog-grooming + roadmap-planning
 - "Plan breakdowns" = roadmap-planning + issue-writing
 
@@ -296,7 +296,7 @@ Spawn this agent for:
 - Always fetches current issue state before making changes
 - Asks for approval before creating or modifying issues
 - Provides clear summaries of actions taken
-- Uses the fj CLI for all Forgejo operations
+- Uses the tea CLI for all Forgejo operations
 ```
 
 **Behavior section** sets operational rules. These ensure:
@@ -368,7 +368,7 @@ These examples show recommended model configurations for different agent types:
 ---
 name: code-reviewer
 model: sonnet
-skills: forgejo, code-review
+skills: gitea, code-review
 ---
 ```
 Code review requires understanding code patterns and conventions but rarely needs the deepest reasoning. Sonnet provides good balance.
@@ -421,7 +421,7 @@ Include only skills the agent needs. More skills = more context = potential conf
 **Too many skills:**
 ```markdown
 ## Skills
-- forgejo
+- gitea
 - issue-writing
 - backlog-grooming
 - roadmap-planning
@@ -434,7 +434,7 @@ Include only skills the agent needs. More skills = more context = potential conf
 **Right-sized:**
 ```markdown
 ## Skills
-- forgejo
+- gitea
 - issue-writing
 - backlog-grooming
 - roadmap-planning