chore(roo): establish git branching strategy for workshop monorepo

- Add branch naming convention: type/scope/short-description
- Update gitea-push skill: branch guard in Step 1 (never commit to main)
- Update rules-mcp-builder: create branch before any MCP build
- Update rules-bigmind: create branch before any BigMind task
- Update rules-homelab: create branch before any homelab task
- Add Section 11 to REPO_STRATEGY.md: full branching strategy doc
  (types, scopes, workflow, Lumen responsibilities, examples)
- Ticketing decision: Gitea Issues only, no Docker ticketing service

.roo/rules-bigmind/00-bigmind-behavior.md

@@ -28,8 +28,13 @@ Patrick is working on BigMind itself — the memory system that is Lumen's super
 ## Before Starting Any BigMind Task
 1. **Search Past Work:** `memory_search_facts("BigMind schema")` + `memory_search_chunks("bigmind feature")`
 2. **Check Schema Version:** Never assume — read `db.py` SCHEMA_VERSION before migrating
-3. **Announce Focus:** `memory_announce_focus(session_id, "BigMind: adding feature X", files=["bigmind/db.py", "bigmind/memory_store.py"], ide_hint="VS Code")`
-4. **Form Hypothesis:** `memory_add_hypothesis(session_id, "Feature X requires schema v{n+1} migration with Y new columns")`
+3. **Create a branch (MANDATORY — never work on main):**
+   ```bash
+   git checkout -b feat/bigmind/feature-name
+   # or fix/bigmind/bug-name for a bug fix
+   ```
+4. **Announce Focus (include branch name):** `memory_announce_focus(session_id, "BigMind: adding feature X on branch feat/bigmind/feature-name", files=["bigmind/db.py", "bigmind/memory_store.py"], ide_hint="VS Code")`
+5. **Form Hypothesis:** `memory_add_hypothesis(session_id, "Feature X requires schema v{n+1} migration with Y new columns")`
 
 ## Schema Change Rules (non-negotiable)
 - Every schema change needs a migration function: `_migrate_v{n}_to_v{n+1}(conn)`