pr-draftlisted

# Draft a pull request Turn the current branch into a ready-to-paste PR title and body, grounded in the real commits and diff. Draft only: it does not create the PR. ## Step 1: Context - Current branch: `git rev-parse --abbrev-ref HEAD`. - **Key**: extract `PROJECT-NUMBER` from the branch name (e.g. `HHH-20527-modernize-...` -> `HHH-20527`). If the branch has no such key, ask the user for it. - **Base**: use the first ref that exists, checked with `git rev-parse --verify <ref>`: `upstream/main`, then `origin/main`, then `main`. If `$ARGUMENTS` names a base, use that. If still unclear, ask. ## Step 2: Read the changes (grounding) ```bash git log <base>..HEAD --oneline git diff <base>...HEAD --stat ``` Read the key hunks of the diff if needed. Draft from what actually changed, not from memory. ## Step 3: Title `[XXX-0000] <summary>` - `[XXX-0000]` is the key from Step 1 (e.g. `[HHH-20527]`, `[CBRD-1234]`). - `<summary>` is concise **English** using easy words anyone can understand, one line, no trailing period. ## Step 4: Body (Korean, three sections) ```markdown ## Purpose <왜 이 작업을 하는가(무엇이 문제/필요인가) -> 이 PR이 무엇을 하는가 -> 그렇게 한 근거. (필수)> ## Implementation <이 PR을 구현하기 위해 어떻게 했는가. (선택: 없으면 N/A)> ## Remarks <주의사항, 후속 작업, 리뷰 포인트 등. (선택: 없으면 N/A)> ``` **도식(선택)**: 구조·흐름 변화가 말로만 설명하기 복잡하면 Implementation에 `mermaid` 코드블록을 넣어도 좋다(GitHub PR 본문이 자동 렌더, 노드는 텍스트에 맞춰 자동 크기 조정이라 짤림 없음). 꼭 필요할 때만 간결하게. Rules: **Purpose is required.** Implementation and Remarks are optional and becom