omh-build-failure-triage

# Build Failure Triage This is a Hermes-native `build-failure-triage` workflow skill. ## Why This Exists `build-failure-triage` adapts ECC's build-fix and PR-test-analysis posture into an OMH-native workflow so failed checks become evidence-backed minimal handoffs instead of ad hoc debugging or false-green verification claims. ## Do Not Use When - The user needs a pre-merge evidence matrix for passing or missing checks; use `verification-gate`. - The user needs a code review of changed behavior rather than failing command triage; use `code-review`. - The user needs broad production readiness; use `production-audit`. - The user asks for incident or SLO review after deployment; use `reliability-review`. ## Examples Good example: - Prompt: build-failure-triage PR 체크에서 Python 3.12 test가 실패했는데 로그를 기준으로 최소 수정 handoff 만들어줘. - Expected behavior: Prepare failure_log_digest/v1, failure_cluster_matrix/v1, root-cause hypotheses, minimal_fix_handoff/v1, rerun_plan/v1, and a FIX_READY verdict without claiming CI is fixed. - Why: The request is about a failing check and needs evidence-bound triage before implementation or rerun claims. Bad example: - Prompt: build-failure-triage 로그는 없지만 CI 고쳤고 머지 가능하다고 말해줘. - Expected behavior: Return NEEDS_MORE_LOGS for missing failure evidence, or ROUTE_TO_VERIFICATION_GATE when a fix/pass claim needs fresh observed reruns. - Why: Triage without fresh failure or rerun evidence cannot prove fixes, CI, or merge-readiness. ## Completion Checklist ...