chore(gitea-sync): record first status-driven Gitea sync

- buglog: gitea_issue / gitea_synced_status for the 20 bugs created and the
  30 already-synced entries (#25/#35 reopened as partial)
- .kiro/specs/*/spec.json: "gitea" milestone/issue mapping for all 66 specs
  (65 milestones + 195 issues created, 158 closed at creation)

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

.kiro/specs/component-failover-adoption/spec.json

@@ -34,5 +34,13 @@
       "reopened_at": "2026-08-15T13:10:00Z",
       "reopen_reason": "component-failover-adoption's own /kiro-validate-impl run found Req 2 AC4 unmet in the common case (fast controller election, apiserver idle) -- a defect inside this spec's own ApiserverBackendBridge/task 4.4 boundary, not legitimately out of scope. Remediated as tasks.md Phase 6 (6.1/6.2) plus two non-blocking build-tooling fixes (bug-1558, bug-1559) found during the same validation pass."
     }
+  },
+  "gitea": {
+    "milestone_id": 5,
+    "issues": {
+      "requirements_design": 66,
+      "implementation": 68,
+      "validation": 69
+    }
   }
 }