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