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>

ARCHITECTURE.md

@@ -23,7 +23,7 @@ The architecture follows a layered composition model where each component type s
 │  │     AGENTS      │ │              SKILLS                  │   │
 │  │  Specialized    │ │         Knowledge modules            │   │
 │  │   subagents     │ │                                      │   │
-│  │                 │ │  issue-writing    forgejo            │   │
+│  │                 │ │  issue-writing    gitea            │   │
 │  │ product-manager │ │  backlog-grooming roadmap-planning   │   │
 │  └─────────────────┘ └─────────────────────────────────────┘   │
 │              │                    ▲                            │
@@ -49,13 +49,13 @@ Each command file contains:
 
 ```yaml
 ---
-description: Work on a Forgejo issue
+description: Work on a Gitea issue
 argument-hint: <issue-number>
 ---
 
 # Work on Issue #$1
 
-1. **View the issue**: `fj issue view $1`
+1. **View the issue**: `tea issue view $1`
 2. **Create a branch**: `git checkout -b issue-$1-<title>`
 ...
 ```
@@ -79,13 +79,13 @@ Create a command when you have:
 
 | Command | Purpose | Skills Used |
 |---------|---------|-------------|
-| `/work-issue` | Implement an issue end-to-end | forgejo |
-| `/dashboard` | View open issues and PRs | forgejo |
-| `/review-pr` | Review and act on a PR | forgejo |
-| `/create-issue` | Create single or batch issues | forgejo, issue-writing |
+| `/work-issue` | Implement an issue end-to-end | gitea |
+| `/dashboard` | View open issues and PRs | gitea |
+| `/review-pr` | Review and act on a PR | gitea |
+| `/create-issue` | Create single or batch issues | gitea, issue-writing |
 | `/groom` | Improve issue quality | backlog-grooming, issue-writing |
-| `/roadmap` | View issues organized by status | forgejo, roadmap-planning |
-| `/plan-issues` | Break down features into issues | roadmap-planning, issue-writing, forgejo |
+| `/roadmap` | View issues organized by status | gitea, roadmap-planning |
+| `/plan-issues` | Break down features into issues | roadmap-planning, issue-writing, gitea |
 
 ---
 
@@ -134,7 +134,7 @@ Create a skill when you find yourself:
 
 | Skill | Purpose |
 |-------|---------|
-| `forgejo` | How to use the Forgejo CLI for issues and PRs |
+| `gitea` | How to use the Gitea CLI for issues and PRs |
 | `issue-writing` | How to structure clear, actionable issues |
 | `backlog-grooming` | How to review and improve existing issues |
 | `roadmap-planning` | How to plan features and create issue breakdowns |
@@ -204,8 +204,8 @@ Create an agent when you need:
 
 | Agent | Skills | Use Case |
 |-------|--------|----------|
-| `product-manager` | forgejo, issue-writing, backlog-grooming, roadmap-planning | Batch issue operations, backlog reviews, feature planning |
-| `code-reviewer` | forgejo, code-review | Automated PR review, quality checks |
+| `product-manager` | gitea, issue-writing, backlog-grooming, roadmap-planning | Batch issue operations, backlog reviews, feature planning |
+| `code-reviewer` | gitea, code-review | Automated PR review, quality checks |
 
 ---
 
@@ -222,7 +222,7 @@ User invokes command
 │ workflow steps    │
 └───────────────────┘
         │
-        ├─── Direct action (git, fj CLI)
+        ├─── Direct action (git, tea CLI)
         │
         ├─── Reference skill for knowledge
         │           │
@@ -253,7 +253,7 @@ User invokes command
 2. **Skills consulted**:
    - `roadmap-planning`: How to break down features
    - `issue-writing`: How to structure each issue
-   - `forgejo`: How to create issues via CLI
+   - `gitea`: How to create issues via CLI
 
 3. **Workflow executed**:
    - Analyze what "dark mode" involves
@@ -304,7 +304,7 @@ Agents declare their skills in the YAML frontmatter:
 ```yaml
 ---
 name: product-manager
-skills: forgejo, issue-writing, backlog-grooming
+skills: gitea, issue-writing, backlog-grooming
 ---
 ```
 
@@ -335,7 +335,7 @@ The agent works autonomously and returns results to the command.
 Small, focused components combine to handle complex scenarios:
 
 ```
-/plan-issues = roadmap-planning + issue-writing + forgejo
+/plan-issues = roadmap-planning + issue-writing + gitea
 product-manager = all four skills combined
 ```
 
@@ -368,7 +368,7 @@ ai/
 │   ├── roadmap.md
 │   └── plan-issues.md
 ├── skills/                      # Knowledge modules
-│   ├── forgejo/
+│   ├── gitea/
 │   │   └── SKILL.md
 │   ├── issue-writing/
 │   │   └── SKILL.md