project-auto-wizard 0.13.3 → 0.14.0

package/payload/workflows/common/PROJECT-COMMON-AUTO-CHANGELOG-CONTROL.yaml

@@ -69,7 +69,7 @@ permissions:
   copilot-requests: write
 
 env:
-  # 스크립트 import가 .github/scripts/__pycache__를 만들어 봇 커밋에 섞이지 않게 한다
+  # Keep script imports from creating .github/scripts/__pycache__ so it never ends up in bot commits
   PYTHONDONTWRITEBYTECODE: "1"
 
 jobs:
@@ -96,9 +96,11 @@ jobs:
           GH_REPO: ${{ github.repository }}
         run: |
           PR_NUMBER=${{ github.event.pull_request.number }}
-          # 파이프라인 도중 {{DEVELOP_BRANCH}}에 push하면 그 실행은 대기열에서 기다렸다가 이미 병합된
-          # PR을 다시 처리한다 — 빈 요약 댓글, 중복 CHANGELOG 항목, {{DEVELOP_BRANCH}}에만 남는 확정 커밋이 생긴다.
-          # 이벤트 시점이 아니라 지금 상태를 본다. 조회에 실패하면 릴리스를 막지 않고 진행한다.
+          # A push to {{DEVELOP_BRANCH}} mid-pipeline queues a run that later reprocesses the
+          # already-merged PR - an empty summary comment, duplicate CHANGELOG entries and a
+          # confirm commit that lands only on {{DEVELOP_BRANCH}}.
+          # Look at the current state, not the event-time state. If the lookup fails,
+          # do not block the release and carry on.
           STATE=$(gh pr view "$PR_NUMBER" --json state -q .state 2>/dev/null || echo "UNKNOWN")
           if [ "$STATE" = "MERGED" ] || [ "$STATE" = "CLOSED" ]; then
             echo "open=false" >> "$GITHUB_OUTPUT"
@@ -152,8 +154,9 @@ jobs:
         run: |
           git fetch origin {{MAIN_BRANCH}}
           git log --pretty=%s "origin/{{MAIN_BRANCH}}..HEAD" > commits.txt
-          # 본문 푸터 BREAKING CHANGE:는 제목 목록 뒤에 한 줄씩 덧붙인다 — 스크립트는 한 줄을
-          # 한 항목으로 읽으므로 본문 전체(%B)를 넣으면 설명 줄까지 변경 항목으로 잡힌다.
+          # Body-footer BREAKING CHANGE: lines are appended after the subject list, one per
+          # line. The script reads each line as one entry, so passing the whole body (%B)
+          # would turn description lines into change entries.
           git log --pretty=%b "origin/{{MAIN_BRANCH}}..HEAD" | grep -E '^BREAKING[ -]CHANGE[[:space:]]*:' >> commits.txt || true
           git diff --stat "origin/{{MAIN_BRANCH}}...HEAD" > _full_diff_stat.txt
           if [ "$(wc -l < _full_diff_stat.txt)" -gt 49 ]; then
@@ -170,6 +173,7 @@ jobs:
           GH_TOKEN: ${{ github.token }}
           GITHUB_TOKEN: ${{ github.token }}
         run: |
+          m() { python3 "$GITHUB_WORKSPACE/.github/scripts/messages.py" get "$@"; }
           git log --pretty=%H "origin/{{MAIN_BRANCH}}..HEAD" > commit_shas.txt
 
           gh pr list --state merged --base {{DEVELOP_BRANCH}} \
@@ -177,7 +181,7 @@ jobs:
 
           MERGED_PR_COUNT=$(python3 -c "import json; print(len(json.load(open('merged_prs.json'))))")
           if [ "$MERGED_PR_COUNT" -ge 200 ]; then
-            echo "::warning::gh pr list가 --limit 200에 도달했습니다 — 오래된 병합 PR이 누락됐을 수 있습니다 (조회된 PR: $MERGED_PR_COUNT)"
+            echo "::warning::$(m wf_changelog.pr_list_limit count="$MERGED_PR_COUNT")"
           fi
 
           ISSUE_NUMBERS=$(python3 .github/scripts/changelog_manager.py collect-issue-closes \
@@ -187,7 +191,7 @@ jobs:
           rm -f commit_shas.txt merged_prs.json
 
           if [ -z "$ISSUE_NUMBERS" ]; then
-            echo "이번 릴리스에 연결할 이슈 없음 — 건너뜀"
+            echo "$(m wf_changelog.no_issues)"
             exit 0
           fi
 
@@ -196,7 +200,7 @@ jobs:
             --issue-numbers "$ISSUE_NUMBERS" \
             --replace
 
-          echo "이슈 연결: $ISSUE_NUMBERS"
+          echo "$(m wf_changelog.issues_linked issues="$ISSUE_NUMBERS")"
 
       - name: Confirm release version (bump + sync)
         id: bump
@@ -207,9 +211,11 @@ jobs:
           GITHUB_TOKEN: ${{ github.token }}
           COPILOT_AI: ${{ steps.copilot_options.outputs.copilot_ai }}
         run: |
-          # 멱등: 이 PR에서 이미 확정한(아직 발행 전) 버전을 다시 올리지 않는다.
-          # HEAD 커밋 메시지만 보면 확정 커밋 위에 커밋이 더 쌓일 때({{DEVELOP_BRANCH}} 추가 push,
-          # {{MAIN_BRANCH}} 역병합) 가드가 풀려 발행되지 않은 버전이 생기므로 버전과 태그로 판정한다.
+          # Idempotency: never raise a version this PR already confirmed (not yet published).
+          # Looking only at the HEAD commit message lets the guard slip when more commits
+          # pile on top of the confirm commit (extra {{DEVELOP_BRANCH}} pushes, a
+          # {{MAIN_BRANCH}} back-merge) and an unpublished version appears, so decide by
+          # version and tag instead.
           HEAD_MSG=$(git log -1 --pretty=%s)
           HEAD_VERSION=$(python3 .github/scripts/version_manager.py get | tail -n 1)
           MAIN_VERSION=$(git show "origin/{{MAIN_BRANCH}}:version.yml" 2>/dev/null | grep -m1 '^version:' | sed 's/version:[ \t]*"\{0,1\}\([0-9][0-9.]*\)"\{0,1\}.*/\1/' || true)
@@ -224,8 +230,10 @@ jobs:
           echo "bump level: $BUMP"
 
           if [ -n "$MAIN_VERSION" ] && [ -n "$HEAD_VERSION" ] && version_gt "$HEAD_VERSION" "$MAIN_VERSION" && ! is_tagged "$HEAD_VERSION"; then
-            # 이미 확정된 버전 — {{MAIN_BRANCH}} 버전 기준으로 다시 계산해 더 높아질 때만(예: 확정 뒤 feat 추가) 올린다.
-            # 버전을 건너뛰지 않고, AI 보조 판정이 재실행마다 달라도 낮아지지 않는다.
+            # Already-confirmed version - recompute from the {{MAIN_BRANCH}} version and raise it
+            # only when the result is higher (e.g. a feat added after confirming).
+            # Versions are never skipped, and they never drop even if an AI-assisted
+            # classification differs between re-runs.
             TARGET=$(python3 -c 'import sys; sys.path.insert(0, ".github/scripts"); from version_manager import increment_version; print(increment_version(sys.argv[1], sys.argv[2]))' "$MAIN_VERSION" "$BUMP")
             if version_gt "$TARGET" "$HEAD_VERSION"; then
               NEW_VERSION=$(python3 .github/scripts/version_manager.py set "$TARGET" | tail -n 1)
@@ -235,7 +243,7 @@ jobs:
               echo "version already confirmed and not yet released — reusing $NEW_VERSION ({{MAIN_BRANCH}} is $MAIN_VERSION)"
             fi
           elif [ -z "$MAIN_VERSION" ] && printf '%s\n' "$HEAD_MSG" | grep -q "^chore(version): confirm v.* \[skip ci\]"; then
-            # {{MAIN_BRANCH}}에 아직 version.yml이 없는 첫 릴리스의 재실행
+            # Re-run of a first release where {{MAIN_BRANCH}} has no version.yml yet
             NEW_VERSION="$HEAD_VERSION"
             echo "version already confirmed by a previous run — reusing $NEW_VERSION (no re-increment)"
           else
@@ -270,7 +278,7 @@ jobs:
             --pr-title "$PR_TITLE" \
             --diff-stat-file diff_stat.txt | tail -n 1)
           ENGINE=$(python3 -c 'import json,sys; print(json.loads(sys.argv[1]).get("engine") or "unknown")' "$SUMMARY_RESULT" 2>/dev/null || echo "unknown")
-          # fallback이면 사유(스크립트가 ::warning::으로도 남김)를 engine 줄에 붙인다 — 잡 로그를 열지 않아도 원인이 보이게
+          # On fallback, append the reason (the script also emits it as ::warning::) to the engine line so the cause is visible without opening the job log
           FALLBACK_REASON=$(python3 -c 'import html,json,sys; print(html.escape((json.loads(sys.argv[1]).get("fallback_reason") or "")[:200]))' "$SUMMARY_RESULT" 2>/dev/null || echo "")
           ENGINE_LINE="$ENGINE${FALLBACK_REASON:+ ($FALLBACK_REASON)}"
           echo "summary engine: $ENGINE_LINE"
@@ -289,7 +297,7 @@ jobs:
           GH_TOKEN: ${{ github.token }}
         run: |
           PR_NUMBER=${{ github.event.pull_request.number }}
-          # 재실행·재동기화 때 댓글이 쌓이지 않도록 이 봇이 남긴 요약 댓글을 표식으로 찾아 교체한다
+          # Find this bot's earlier summary comment by its marker and replace it so re-runs and re-syncs do not pile up comments
           MARKER="<!-- project-auto-wizard:pr-summary -->"
 
           {
@@ -343,17 +351,18 @@ jobs:
           # Working files must not land in the repo
           rm -f pr_body.md summary.md commits.txt diff_stat.txt comment_body.md comment_payload.json commit_shas.txt merged_prs.json
 
-          # "Re-run failed jobs"는 precheck 결과를 재사용한다 — 그사이 PR이 병합·종료됐다면
-          # 확정 커밋을 올리지 않는다 (병합 뒤 {{DEVELOP_BRANCH}}에만 남는 커밋이 된다).
+          # "Re-run failed jobs" reuses the precheck result - if the PR was merged or closed
+          # in the meantime, do not push the confirm commit (it would exist only on
+          # {{DEVELOP_BRANCH}} after the merge).
           PR_STATE=$(gh pr view "${{ github.event.pull_request.number }}" --json state -q .state 2>/dev/null || echo "UNKNOWN")
           if [ "$PR_STATE" = "MERGED" ] || [ "$PR_STATE" = "CLOSED" ]; then
             echo "::notice::PR is already $PR_STATE — not pushing release docs"
             exit 0
           fi
 
-          # -A는 러너가 만든 임시 파일·캐시까지 사용자 레포에 커밋한다.
-          # 버전 파일은 이미 추적 중이라 -u로 충분하고, 첫 릴리스에 새로 생기는
-          # CHANGELOG만 따로 올린다 (.gitignore에 있으면 건너뛴다).
+          # -A would also commit runner temp files and caches into the user's repo.
+          # Version files are already tracked, so -u is enough; only a CHANGELOG
+          # created by the first release is added separately (skipped if ignored).
           git add -u
           git ls-files -z --others --exclude-standard -- CHANGELOG.json CHANGELOG.md | xargs -0 -r git add --
 
@@ -399,6 +408,7 @@ jobs:
           # (RELEASE-PUBLISH etc.); GITHUB_TOKEN merges do not.
           GH_TOKEN: ${{ secrets.WORKFLOW_PAT || github.token }}
         run: |
+          m() { python3 "$GITHUB_WORKSPACE/.github/scripts/messages.py" get "$@"; }
           PR_NUMBER=${{ github.event.pull_request.number }}
           VERSION="${{ steps.bump.outputs.new_version }}"
 
@@ -407,8 +417,9 @@ jobs:
           SUBJECT="chore(release): v${VERSION} (PR #${PR_NUMBER})"
           ERR_FILE="${RUNNER_TEMP:-/tmp}/merge_err.txt"
 
-          # 확정 커밋 push 직후에는 GitHub가 PR head 갱신을 아직 반영하지 못해 "Head branch is
-          # out of date"·"not mergeable"로 간헐 실패한다. 간격을 늘려 가며 다시 시도한다.
+          # Right after the confirm commit is pushed, GitHub may not have picked up the new PR
+          # head yet and intermittently fails with "Head branch is out of date" / "not
+          # mergeable". Retry with growing intervals.
           MERGED=false
           MAX_ATTEMPTS=4
           for ATTEMPT in $(seq 1 $MAX_ATTEMPTS); do
@@ -430,11 +441,12 @@ jobs:
             fi
             cat "$ERR_FILE" >&2
             [ "$ATTEMPT" -ge "$MAX_ATTEMPTS" ] && break
-            # 충돌은 기다려도 풀리지 않는다
+            # A conflict never resolves by waiting
             [ "$(gh pr view "$PR_NUMBER" --json mergeable -q .mergeable 2>/dev/null)" = "CONFLICTING" ] && break
             if grep -qi "out of date" "$ERR_FILE"; then
-              # 브랜치 보호의 "최신 상태 요구"로 실제로 뒤처졌다면 base를 head에 병합해 따라잡는다
-              # (단순 반영 지연이면 "새 커밋 없음"으로 거절되고 그대로 재시도한다)
+              # If the head really fell behind because of branch protection's "require up to
+              # date" rule, merge base into head to catch up (a mere propagation delay is
+              # rejected as "no new commits" and simply retried)
               gh api -X PUT "repos/${GITHUB_REPOSITORY}/pulls/${PR_NUMBER}/update-branch" > /dev/null 2>&1 \
                 && echo "head branch updated from base" || true
             fi
@@ -448,10 +460,10 @@ jobs:
             MERGEABLE=$(gh pr view "$PR_NUMBER" --json mergeable -q .mergeable 2>/dev/null || echo "unknown")
             ALLOW_MERGE_COMMIT=$(gh api "repos/${GITHUB_REPOSITORY}" --jq '.allow_merge_commit' 2>/dev/null || echo "unknown")
             if [ "$MERGEABLE" = "CONFLICTING" ]; then
-              # 주로 {{MAIN_BRANCH}} 직접 push 뒤 안전망 버전 bump가 {{DEVELOP_BRANCH}}에 반영되지 않았을 때다
-              echo "::error::릴리스 PR이 {{MAIN_BRANCH}}와 충돌합니다 (버전 파일·CHANGELOG 등) — {{MAIN_BRANCH}}에만 있는 커밋을 {{DEVELOP_BRANCH}}에 병합한 뒤 push하세요: git checkout {{DEVELOP_BRANCH}} && git merge origin/{{MAIN_BRANCH}} (버전 줄 충돌은 어느 쪽을 택해도 다음 실행이 알맞게 다시 확정합니다)"
+              # Mostly happens when a safety-net version bump after a direct {{MAIN_BRANCH}} push never reached {{DEVELOP_BRANCH}}
+              echo "::error::$(m wf_changelog.merge_conflict prod="{{MAIN_BRANCH}}" dev="{{DEVELOP_BRANCH}}")"
             elif [ "$ALLOW_MERGE_COMMIT" = "false" ]; then
-              echo "::error::이 레포는 merge commit이 비활성화되어 있습니다 — Settings에서 'Allow merge commits'를 켜세요; 릴리스 감지는 merge commit subject를 사용합니다"
+              echo "::error::$(m wf_changelog.merge_commit_disabled)"
             else
               echo "::error::PR merge failed after $MAX_ATTEMPTS attempts (allow_merge_commit=$ALLOW_MERGE_COMMIT) — check branch protection rules, required checks, and token permissions"
             fi
@@ -459,20 +471,32 @@ jobs:
           fi
 
   wait-for-merge-and-trigger-release:
-    name: Wait for merge and trigger RELEASE-PUBLISH (WORKFLOW_PAT 없이도 동작)
+    name: Wait for merge and trigger RELEASE-PUBLISH (works without WORKFLOW_PAT)
     needs: changelog-and-merge
     runs-on: ubuntu-latest
     timeout-minutes: 35
     permissions:
+      # contents: read is needed for the sparse checkout that loads the message catalog
+      contents: read
       pull-requests: read
       actions: write
     steps:
+      # Only the message catalog and version.yml (language) are needed here
+      - name: Checkout message catalog
+        uses: actions/checkout@v7
+        with:
+          sparse-checkout: |
+            .github/scripts/messages.py
+            version.yml
+          sparse-checkout-cone-mode: false
+
       - name: Poll for merge completion
         id: wait
         env:
           GH_TOKEN: ${{ github.token }}
           GH_REPO: ${{ github.repository }}
         run: |
+          m() { python3 "$GITHUB_WORKSPACE/.github/scripts/messages.py" get "$@"; }
           PR_NUMBER=${{ github.event.pull_request.number }}
           MAX_WAIT=1800
           INTERVAL=20
@@ -483,7 +507,7 @@ jobs:
             PR_STATE=$(gh pr view "$PR_NUMBER" --json state -q .state 2>/dev/null || echo "")
             if [ "$PR_STATE" = "MERGED" ]; then
               MERGED=true
-              echo "PR #$PR_NUMBER 병합 확인 (경과 ${ELAPSED}s)"
+              echo "$(m wf_changelog.merge_confirmed pr="$PR_NUMBER" elapsed="$ELAPSED")"
               break
             fi
             sleep $INTERVAL
@@ -491,7 +515,7 @@ jobs:
           done
 
           if [ "$MERGED" != "true" ]; then
-            echo "::warning::PR #$PR_NUMBER 병합을 ${MAX_WAIT}s 내에 확인하지 못했습니다 — RELEASE-PUBLISH 자동 트리거를 건너뜁니다. WORKFLOW_PAT이 등록되어 있다면 기존 경로로 정상 진행되며, 없다면 필요 시 RELEASE-PUBLISH를 수동으로 workflow_dispatch 하세요."
+            echo "::warning::$(m wf_changelog.merge_timeout pr="$PR_NUMBER" max="$MAX_WAIT")"
           fi
 
           echo "merged=$MERGED" >> "$GITHUB_OUTPUT"
@@ -503,5 +527,6 @@ jobs:
           GH_TOKEN: ${{ github.token }}
           GH_REPO: ${{ github.repository }}
         run: |
+          m() { python3 "$GITHUB_WORKSPACE/.github/scripts/messages.py" get "$@"; }
           gh workflow run PROJECT-COMMON-RELEASE-PUBLISH.yaml --ref {{MAIN_BRANCH}}
-          echo "RELEASE-PUBLISH workflow_dispatch 트리거 요청 완료 (WORKFLOW_PAT 없이도 동작)"
+          echo "$(m wf_changelog.release_publish_triggered)"

package/payload/workflows/common/PROJECT-COMMON-ISSUE-HELPER.yaml

@@ -1,15 +1,16 @@
 # project-auto-wizard:managed-workflow
 # PROJECT-COMMON-ISSUE-HELPER.yaml
-# 이슈 생성/제목 수정 시 브랜치명·커밋 메시지를 댓글로 안내
+# Suggest a branch name and commit message as a comment when an issue is created or retitled
 #
-# 이슈가 열리거나(opened) 제목이 수정되면(edited + 제목 변경),
-# 정규화된 브랜치명과 커밋 메시지를 이슈 댓글로 생성/갱신한다.
-# ISSUE_HELPER_CREATE_BRANCH=true로 바꾸면 브랜치도 함께 생성한다
-# (기본값은 false — 이슈를 열 때마다 브랜치가 자동 생성되는 것을
-# 막기 위해 옵트인으로 전환됨).
+# When an issue is opened, or its title is edited (edited + title changed),
+# the normalized branch name and commit message are posted (or updated) as an
+# issue comment.
+# Set ISSUE_HELPER_CREATE_BRANCH=true to also create the branch
+# (default is false - opt-in, so a branch is not created automatically
+# every time an issue is opened).
 #
-# 로직 본체는 .github/scripts/issue_helper.py (Chuseok22/github-issue-helper의
-# Python 재작성, 동일 작성자).
+# The logic lives in .github/scripts/issue_helper.py (a Python rewrite of
+# Chuseok22/github-issue-helper, same author).
 
 name: PROJECT-ISSUE-HELPER
 
@@ -17,30 +18,31 @@ on:
   issues:
     types: [opened, edited]
 
-# contents는 항상 write로 고정한다. ISSUE_HELPER_CREATE_BRANCH="true"일 때
-# git/refs API로 브랜치를 생성하려면 write가 필요한데, 이 값은 @wizard ask로
-# 설치 후에도 사용자가 직접 켤 수 있어(마법사 재실행 없이) 그 시점에 맞춰
-# permissions를 조건부로 올릴 방법이 없다.
+# contents is always fixed to write. Creating a branch through the git/refs API
+# when ISSUE_HELPER_CREATE_BRANCH="true" needs write, and users can switch that
+# value on themselves after install (via the wizard ask marker, without re-running the
+# wizard), so there is no way to raise permissions conditionally at that point.
 permissions:
   issues: write
   contents: write
 
 jobs:
   issue-helper:
-    name: 브랜치명 & 커밋 메시지 안내
+    name: Branch name & commit message guide
     if: github.event.action == 'opened' || (github.event.action == 'edited' && github.event.changes.title)
     runs-on: ubuntu-latest
     env:
       GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
       ISSUE_HELPER_BRANCH_PREFIX: ""
       ISSUE_HELPER_MAX_BRANCH_LENGTH: "100"
-      ISSUE_HELPER_COMMIT_TEMPLATE: "${issueTitle} : feat : {변경 사항에 대한 설명} ${issueUrl}"
+      # Optional override of the commit message template (the default follows the workflow language):
+      # ISSUE_HELPER_COMMIT_TEMPLATE: "${issueTitle} : feat : {description of the change} ${issueUrl}"
       ISSUE_HELPER_CREATE_BRANCH: "false" # @wizard ask:false
       ISSUE_HELPER_BASE_BRANCH: "{{MAIN_BRANCH}}"
     steps:
       - name: Checkout repository
         uses: actions/checkout@v7
 
-      - name: 브랜치명 & 커밋 메시지 생성
+      - name: Generate branch name & commit message
         id: issue-helper
         run: python3 .github/scripts/issue_helper.py run

package/payload/workflows/common/PROJECT-COMMON-README-VERSION-UPDATE.yaml

@@ -12,13 +12,12 @@
 # 4. Commits and pushes the change ([skip ci])
 #
 # Supported version line formats (case-insensitive, flexible spacing):
-# - ## 최신 버전 : v1.0.0 (2025-08-15)
-# - ## 최신버전 : v1.0.0 (2025-08-15)
+# - ## <Korean "latest version", with or without a space> : v1.0.0 (2025-08-15)
 # - ## Current Version : v1.0.0 (2025-08-15)
 # - ## Recent Version : v1.0.0 (2025-08-15)
 # - ## Latest Version : v1.0.0
 # - ## Version : v1.0.0
-# - ## 버전 : v1.0.0
+# - ## <Korean "version"> : v1.0.0
 #
 # The marker comment <!-- AUTO-VERSION-SECTION: DO NOT EDIT MANUALLY -->
 # is added automatically above the version line.
@@ -51,7 +50,7 @@ name: README VERSION UPDATE
 env:
   # Whether to show the date next to the version (true/false)
   SHOW_DATE: true
-  # 스크립트 import가 .github/scripts/__pycache__를 만들어 봇 커밋에 섞이지 않게 한다
+  # Keep script imports from creating .github/scripts/__pycache__ so it never ends up in bot commits
   PYTHONDONTWRITEBYTECODE: "1"
 
 concurrency:
@@ -113,10 +112,16 @@ jobs:
       - name: Update version line in README.md
         if: steps.precheck.outputs.readme_exists == 'true'
         run: |
+          m() { python3 "$GITHUB_WORKSPACE/.github/scripts/messages.py" get "$@"; }
           LATEST_VERSION="${{ steps.version_info.outputs.latest_version }}"
           RELEASE_DATE="${{ steps.version_info.outputs.release_date }}"
           SHOW_DATE="${{ env.SHOW_DATE }}"
 
+          # Hangul in the Korean heading patterns below is written as UTF-8 byte escapes so
+          # this file stays ASCII-only; they match the same README headings byte for byte.
+          KO_LATEST=$'\354\265\234\354\213\240'   # Korean "latest"
+          KO_VERSION=$'\353\262\204\354\240\204'  # Korean "version"
+
           # Error message helper
           print_error_message() {
             local error_type="$1"
@@ -132,7 +137,7 @@ jobs:
             echo "  new version text: $version_text"
             echo ""
             echo "Make sure the README version line matches one of:"
-            echo "  ## 최신 버전 : v1.0.0 (2025-08-15)"
+            echo "  $(m wf_readme.hint_first_example)"
             echo "  ## Current Version : v1.0.0"
             echo "  ## Version : v1.0.0"
             echo "Notes:"
@@ -151,12 +156,12 @@ jobs:
 
           # Patterns for recognized version lines (case-insensitive, flexible spacing)
           VERSION_PATTERNS=(
-            "^##[[:space:]]*최신[[:space:]]*버전[[:space:]]*:"
-            "^##[[:space:]]*최신버전[[:space:]]*:"
+            "^##[[:space:]]*${KO_LATEST}[[:space:]]*${KO_VERSION}[[:space:]]*:"
+            "^##[[:space:]]*${KO_LATEST}${KO_VERSION}[[:space:]]*:"
             "^##[[:space:]]*[Cc]urrent[[:space:]]*[Vv]ersion[[:space:]]*:"
             "^##[[:space:]]*[Rr]ecent[[:space:]]*[Vv]ersion[[:space:]]*:"
             "^##[[:space:]]*[Vv]ersion[[:space:]]*:"
-            "^##[[:space:]]*버전[[:space:]]*:"
+            "^##[[:space:]]*${KO_VERSION}[[:space:]]*:"
             "^##[[:space:]]*[Ll]atest[[:space:]]*[Vv]ersion[[:space:]]*:"
           )
 
@@ -175,13 +180,15 @@ jobs:
           # No version line yet — insert a default one
           if [ -z "$VERSION_LINE" ]; then
             echo "no version line found — inserting a new one"
+            # Heading wording follows the configured language; an existing line keeps its own wording
+            DEFAULT_HEADING=$(m wf_readme.default_heading)
 
             if grep -q "^# " README.md; then
               # right after the first title
-              sed -i '/^# /a\\n<!-- AUTO-VERSION-SECTION: DO NOT EDIT MANUALLY -->\n## Latest Version : '"$VERSION_TEXT" README.md
+              sed -i '/^# /a\\n<!-- AUTO-VERSION-SECTION: DO NOT EDIT MANUALLY -->\n## '"$DEFAULT_HEADING"' : '"$VERSION_TEXT" README.md
             else
               # at the very top of the file
-              sed -i '1i\<!-- AUTO-VERSION-SECTION: DO NOT EDIT MANUALLY -->\n## Latest Version : '"$VERSION_TEXT"'\n' README.md
+              sed -i '1i\<!-- AUTO-VERSION-SECTION: DO NOT EDIT MANUALLY -->\n## '"$DEFAULT_HEADING"' : '"$VERSION_TEXT"'\n' README.md
             fi
             echo "default version line inserted: $VERSION_TEXT"
           else