docs: 로컬 merge 게이트 실행 안내에 workflow의 CI env를 적는다

문제
README의 로컬 merge 게이트 반복문과 매뉴얼 01, 생성 명령 출력은 CI=true와
CI 빌드 식별값 없이 돌리는 법만 적는다. 그렇게 통과해도 workflow(CI=true)에서
떨어지는 결함 두 건(1103/11-07, 11-08)이 이 차이로 숨었다.

고른 방법
- README 반복문 아래에 workflow와 같은 env 블록(CI=true, VITE_COMMIT_SHA,
  VITE_BUILD_ID, RELEASE_ID, CI_RUNNER_IMAGE digest)과 깨끗한 clone에서 돌리라는
  말을 더한다. 테스트가 만드는 로컬 빌드는 이 값과 무관하게 로컬 빌드로
  돈다는 것도 적는다.
- 매뉴얼 01 "merge 전에 돌릴 것"과 생성 명령 Next 2번이 그 블록을
  가리킨다.

검증
- verify:documentation PASS_SCOPED, tests/unit/create-feature.test.ts 43건.

Refs: docs/reviews/2026-11-03-maturity-review/README.md 13절 11-08
This commit is contained in:
DongHyeonka
2026-11-05 04:27:29 +09:00
parent b693600103
commit cd7e784242
3 changed files with 14 additions and 1 deletions
+1 -1
View File
@@ -1749,7 +1749,7 @@ function report(plan: FeaturePlan): string {
.join(", ")} (FE-GATE-028). The merge gates check only their format.`,
" 2. Run the merge gates: corepack pnpm ci:gate -- FE-GATE-<NNN> for each gate of the merge stage in config/ci/gates.json (README lists the loop). test:feature-scaffold runs them on a generated feature except the browser gates FE-GATE-008/009 and test:system.",
` The feature's own tests: node scripts/run-vitest.ts run tests/features/${plan.id} (test:coverage runs them in CI)`,
" A failing gate's log is artifacts/quality/gates/FE-GATE-<NNN>.txt. Locally FE-GATE-013 needs VITE_COMMIT_SHA=$(git rev-parse HEAD).",
" A failing gate's log is artifacts/quality/gates/FE-GATE-<NNN>.txt. Locally FE-GATE-013 needs VITE_COMMIT_SHA=$(git rev-parse HEAD); to run them as CI does, set CI=true and the CI build identity (README).",
" 3. The initial JavaScript changes. While config/scale/feature-shape-ceilings.json exists (the sample is installed), rewrite it with node scripts/scale/measure-feature-shape-growth.ts --initial-baseline --write and commit it with the feature; test:unit compares it with a build. corepack pnpm check:bundle checks the budget.",
" public/release-manifest.json (the dev server's manifest) now names the feature's contract package; commit it with the feature.",
" The registry baseline does not change: new routes, operations, schemas and invalidation topics are additive.",