ci(gitea): add parallel workflow for backend frontend and infra checks

.sisyphus/notepads/club-work-manager/decisions.md

@@ -70,3 +70,29 @@ Attempted to set PostgreSQL session variable (`SET LOCAL app.current_tenant_id`)
 - Error handling via try/catch with logging
 - Synchronous operation in callback is expected pattern
 
+
+---
+
+## Decision 4: actions/upload-artifact@v3 Over v4 for Gitea Compatibility (2026-03-06)
+
+### Context
+Gitea CI pipeline needs artifact uploads for test results and build logs on failure. GitHub Actions has v3 and v4 of upload-artifact available.
+
+### Decision: Use actions/upload-artifact@v3
+
+**Rationale:**
+- v3: Stable across Gitea 1.18-1.22+ (verified by community reports)
+- v4: Breaking changes in cache format (requires Gitea 1.21+)
+- Project may deploy to various Gitea instances (internal/external)
+- CI reliability > performance improvement (~30% upload speed gain in v4)
+
+**Tradeoffs Considered:**
+- v4 Performance: 30% faster uploads, better compression
+- v3 Compatibility: Works on wider range of Gitea versions
+- Decision: Prioritize compatibility for this infrastructure-critical workflow
+
+**Implications:**
+- Slightly slower artifact uploads (non-critical for failure-only uploads)
+- If Gitea version known to be 1.21+, can upgrade to v4
+- Document decision to prevent confusion during future reviews
+