hns-workflow-ci-loop

# CI Loop (`hns-workflow-ci-loop`) Unified CI watch + auto-fix loop. The orchestrator invokes this skill after `/moai sync` Phase 4 (`gh pr create`) returns a PR number. The skill polls required checks, classifies failures into mechanical vs semantic, attempts safe patches up to 3 iterations, and escalates semantic failures via AskUserQuestion. ## Quick Reference **Trigger**: `/moai sync` Phase 4 PR-create returns a PR number, or an existing PR needs CI monitoring. **Two phases, one skill**: 1. **Watch** — Poll `gh pr checks` every 30s, classify required vs auxiliary via `.github/required-checks.yml` SSoT; exit on green/fail/timeout. 2. **Auto-fix** — On required-fail (exit 2), receive JSON handoff, run up to 3 patch iterations, escalate semantic failures immediately. **One-liner**: ```bash MOAI_CIWATCH_GH=gh sh scripts/ci-watch/run.sh <PR_NUMBER> <BRANCH> ``` **Exit codes**: - `0` — all required passed → ready-to-merge AskUserQuestion - `1` — fatal error → surface remediation - `2` — required failure → JSON handoff → auto-fix phase - `3` — 30-min hard timeout → blocker message, return control **HARD invariants**: - AskUserQuestion is orchestrator-only — CLI, shell scripts, and the `manager-develop` (cycle_type=autofix) subagent MUST NOT call it. - Force-push is absolutely prohibited (`--force`, `-f`, `--force-with-lease` all banned). - Max 3 auto-fix iterations; iteration 4+ triggers mandatory blocking AskUserQuestion. - Semantic failures (race, deadlock, panic,...