From 0d7b9dfe0154b6de555331ad4f9c20e03d97ceca Mon Sep 17 00:00:00 2001 From: DongHyeonka Date: Thu, 5 Nov 2026 00:22:19 +0900 Subject: [PATCH] =?UTF-8?q?docs(readme):=20=EB=A1=9C=EC=BB=AC=20merge=20?= =?UTF-8?q?=EA=B2=8C=EC=9D=B4=ED=8A=B8=20=EB=B0=98=EB=B3=B5=EB=AC=B8?= =?UTF-8?q?=EA=B3=BC=20=EC=97=85=EB=8D=B0=EC=9D=B4=ED=8A=B8=20=EC=A0=88?= =?UTF-8?q?=EC=9D=84=20=EC=9D=B4=20=EB=AC=B6=EC=9D=8C=EC=97=90=20=EB=A7=9E?= =?UTF-8?q?=EC=B6=98=EB=8B=A4?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 문제 - "CI and evidence"의 로컬 merge 게이트 반복문이 13개이고 FE-GATE-012가 없다. f41e3d5가 번들 예산 게이트를 merge 단계로 옮겨 gates.json의 merge 단계는 14개다. "Updating a copied project"가 이 반복문을 가리키므로, 동기화한 제품은 번들 예산을 건너뛴다. - 배포 슬롯을 채우는 곳이 config/ci/product-gates.json으로 바뀌었고(12-07), FE-GATE-019는 HTTP/2·entry 압축이 없는 호스트도 실패시킨다(13-02). README는 둘 다 말하지 않는다. - CHANGELOG 미출시 절이 동기화 단위 순 요약이 됐는데(14-01 D5 (b)), 업데이트 절은 그 절을 어떻게 받는지 말하지 않는다. 고른 방법 문장 셋만 고친다. 반복문에 012를 넣고 개수를 14로, 제품 merge 검사 (PRODUCT-GATE-NNN)는 workflow의 product_merge_gate job이 돈다고 적었다. 업데이트 절에는 미출시 절을 범위째 받고 "먼저 할 일"부터 하라는 한 문장을 더했다. cherry-pick 절차는 그대로 둔다(한 수정을 받을 때는 여전히 맞다). 위험·한계 - README의 다른 절(0929/14-02의 범위 동기화 절차 전체)은 다시 쓰지 않았다. 검증 - verify:documentation PASS_SCOPED, documentation-readiness 테스트 통과. - config/ci/gates.json merge 단계 gateIds 14개와 반복문을 대조했다. Refs: docs/reviews/2026-11-03-maturity-review/14-template-product-docs.md 14-01 Refs: docs/reviews/2026-11-03-maturity-review/12-guardrails-ci.md 12-07 --- README.md | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 70b7b423..f3571916 100644 --- a/README.md +++ b/README.md @@ -306,10 +306,11 @@ Two gates intentionally need external evidence: Live hosting verification (FE-GATE-019, production stage) requires `HOSTING_BASE_URL` and the promoted release deployed by the workflow's -`deployment` job. That job is an empty slot until the project fills it +`deployment` job. That job is an empty slot until the project fills it in +`config/ci/product-gates.json` ([`docs/operations/ci-quality-gates.md`](docs/operations/ci-quality-gates.md)); until then the result is `UNVERIFIED`, not `PASS`. A host serving another -release fails. +release fails, and so does one without HTTP/2 or entry compression. ## CI and evidence @@ -325,12 +326,14 @@ MERGE_READY -> RELEASE_READY -> PROD_PROMOTION_READY -> FIELD_SLO_READY The workflow runs on pull requests, pushes to `main` and `develop`, and `v*` tags. The Git host of this repository may not have Actions enabled, so a pull request can show no gate status at all; no status is not a pass. Until the -host runs the workflow and marks the merge gates as required checks, run the 13 +host runs the workflow and marks the merge gates as required checks, run the 14 merge gates locally before merging (FE-GATE-008 and 009 need Playwright -browsers): +browsers; FE-GATE-012 builds the app first). Product checks listed in +`config/ci/product-gates.json` (`PRODUCT-GATE-NNN`) run in the workflow's own +`product_merge_gate` job: ```bash -for gate in 001 002 003 004 005 006 007 008 009 010 011 013 020; do +for gate in 001 002 003 004 005 006 007 008 009 010 011 012 013 020; do corepack pnpm ci:gate -- "FE-GATE-$gate" || break done ``` @@ -345,7 +348,9 @@ Operational details are in `docs/operations/`, with incident procedures in Template versions are Git tags `vX.Y.Z`. [`CHANGELOG.md`](CHANGELOG.md) lists the changes between tags, marks security fixes **[보안]** and contract changes **[계약]** (backend, deployment, CI or feature code must change too), and names -the affected paths. +the affected paths. Its unreleased section summarizes one sync range (the +section head names the base commit and the branch); take that range as a whole +and do its "먼저 할 일" (BREAKING) steps in order before running the gates. Record where you started. Right after copying, commit a one-line `.template-origin` file at the root of your project with the template tag (or