From f3634db18477a06af94ec4eae227ee96378aae0a Mon Sep 17 00:00:00 2001
From: Your Name <you@example.com>
Date: Mon, 29 Jun 2026 11:04:01 +0800
Subject: [PATCH] fix(ci): restore non110 cd push trigger

---
 .gitea/workflows/cd.yaml | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/.gitea/workflows/cd.yaml b/.gitea/workflows/cd.yaml
index d364f155..9dc92de8 100644
--- a/.gitea/workflows/cd.yaml
+++ b/.gitea/workflows/cd.yaml
@@ -10,12 +10,14 @@
 name: CD Pipeline
 
 on:
-  # 2026-06-28 Codex: 110 host runner/CD lane pressure incident.
-  # Production CD remains workflow_dispatch only until a non-110 or hard-limited
-  # runner passes readiness. Host pressure and Docker lock gates stay fail-hard
-  # during the 110 capacity incident.
-  # Push-triggered CD stays off until runner relocation or non-110 hard limits
-  # satisfy ops/runner/guard-gitea-runner-pressure.py.
+  # 2026-06-29 Codex: restore main push CD only after the non-110
+  # awoooi-non110-* runner lane read back registration metadata, active
+  # service, capacity=1, pressure OK, rollback unit, and label target-match.
+  # 110 incident runner labels and generic labels remain fail-closed via
+  # ops/runner/guard-gitea-runner-pressure.py.
+  push:
+    branches:
+      - main
   workflow_dispatch:
     # 手動觸發永遠可用（用於補跑、緊急部署）