chore: gitea-sync --ids, sync recent bugs (#264-#286), refresh STATUS.md

gitea-sync.py: --ids syncs named bugs regardless of dates (OR'd with
--since). Bulk triage bumped last_seen/status_updated across most of the
buglog, so --since 2026-09-01 matched ~1150 bugs while recently fixed older
bugs (bug-1798..1804, 1714, 1754, 1850, 1854) could never be reached.

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

.claude/skills/gitea-sync/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: gitea-sync
 description: Sync cc-sdd specs and OpenWolf buglog to Gitea milestones/issues in nexa/xce
-argument-hint: [--dry-run] [--spec <name>] [--bugs] [--since <date>]
+argument-hint: [--dry-run] [--spec <name>] [--bugs] [--since <date>] [--ids <ids>]
 triggers:
   - /gitea-sync
   - sync to gitea
@@ -50,6 +50,11 @@ Keep the script and this procedure in step when changing either.
   date; for already-synced bugs (`gitea_issue` set), also mirror those whose
   `status_updated >=` this date, so a status change on an old bug still
   reaches Gitea without flooding it with old never-synced bugs
+- `--ids <bug-N,bug-M,...>`: also sync these bugs regardless of dates (OR'd
+  with `--since`). Needed because bulk triage has bumped `last_seen` /
+  `status_updated` on most of the buglog, and for a never-synced bug
+  `--since` only checks `last_seen` — a recently fixed older bug is otherwise
+  unreachable. Always `--dry-run` first: `--since` alone can match ~1100 bugs.
 
 ### 1. Ensure labels exist