[STORY][CFP-2346 S5] 진단 D — consumer system-invariants.md + impl PR 확장 게이트

[mccho-mclayer]

Story SSOT: wrapper/stories/CFP-2351.md

[github-actions]

작업 환경 준비 — worktree-first 의무 reminder

이 Story 진입 직전 worktree 생성 의무. 본 Issue 가 Phase 1 PR 으로 진척하기 전 다음 명령 실행:

```bash
bash templates/scripts/worktree-create.sh ${STORY_KEY} origin/main
```

Story 작업 모두 worktree 안에서 수행 — main working tree 직접 편집 금지.

참조:

• ADR-040 §결정 5 (Stale GC) + Amendment 3 §결정 7 (Normative ↔ mechanical boundary mandate)
• playbook §3.0.11 worktree-first normative + §3.5 worktree dispatch
• CFP-425 Epic (worktree-first mechanical enforcement 영구화) — 본 Story = child / parent

[github-actions]

⚠️ Phase progression invariant violation (CFP-85 / CFP-90)

Story Issue closed at non-terminal phase: phase:설계-리뷰.

Expected: phase:보안-테스트 (default after security test PASS) OR phase:완료 + gate:design-review-pass + gate:retro-complete (CFP-1577 lifecycle 완주 — CFP-2149) OR early-close:<reason> label (Epic 종료 / 중복 / Out-of-scope reclassify 등 명시).

Action required (one of):

1. 올바른 progression: Issue 재open → 정상 lane 진행 → terminal phase 도달 후 close
2. Early close 정당화: early-close:<reason> label 부착 (예: early-close:duplicate, early-close:reclassified, early-close:epic-rolled-up)

본 alert = policy_violation defect 추적 source (ADR-025 stop discipline metric).

자동 재open 안 함 (manual decision 의무).

[github-actions]

[PMO] Retro mandatory check (CFP-138 / ADR-045)

Phase 2 PR #2355 merged Phase marker absent (option C-prime PR — L5 fallback, CFP-654).
First attempt (PR merge + 5min grace) 후에도 gate:retro-complete label 부재 — retro 자동 작성 trigger 필요.

Action required:

1. PMOAgent re-spawn (Orchestrator 자동 또는 사용자 요청)
2. retro file 작성 → /wrapper/retros/-cfp-NNN-.md
3. Story §11 schema update (retro_file / retro_summary / learnings_count / feedback_back_to_codeforge)
4. gate:retro-complete label add (PMOAgent self-write)

Retry policy (ADR-045 D-4 cumulative offset from PR merge):

• First attempt: PR merge + 5min (grace period — 본 attempt fail)
• Retry 1: PR merge + 10min (5min wait)
• Retry 2: PR merge + 20min (10min wait)
• Retry 3: PR merge + 35min (15min wait, final attempt)
• Total attempts = 4 (1 initial + 3 retries)
• Total max latency = 35min from PR merge → ESCALATE 사용자 + Story close 차단 유지

본 alert 는 retry 시 중복 게시 안 함 (idempotent).

NOTE: Phase 1 PR scope 본 workflow = first attempt 만 implement. retry 1/2/3 state machine = Phase 2 PR scope deferred (ADR-045 §D-4 Phase 2 implementation spec).