문제
scripts/scale/run-scale-profile.ts는 단계 출력을
artifacts/scale/<tier>/<step>.log에 쓴다. 이 로그와
verify:extreme-scale·phase5 로그 63개가 git에 추적되고, .gitignore는
artifacts의 json·xml·txt·sarif만 무시한다. 그래서 merge 게이트
check:scale:pr(FE-GATE-005)를 로컬에서 한 번 돌리면 추적 로그 3개가
바뀌고 새 로그 1개가 생겨 작업 트리가 더러워진다. 커밋된 판은 다른
기계의 경로와 ANSI 색 코드를 담고, 읽는 코드·테스트·설정은 없다.
고른 방법
- .gitignore에 artifacts/**/*.log를 넣고 63개 추적을 끊는다. scale
로그(12-08) 35개만이 아니라 같은 원인의 extreme-scale·phase5 로그도
같이 뺀다(0929/11-09 남은 항목).
- 기준 측정은 이미 config/scale/benchmark-baseline.json 같은 정해진
JSON이 맡는다. 로그를 증거로 쓰는 곳은 없다(git grep).
위험·한계
- 동기화 때 다운스트림에서 이 파일들이 지워진다. 두 다운스트림은 이미
지웠다(지난 리뷰 기록).
검증
- check:scale:pr PASSED 뒤 git status에 로그 변경이 없다.
Refs: docs/reviews/2026-11-03-maturity-review/12-guardrails-ci.md 12-08
Refs: docs/reviews/2026-11-03-maturity-review/11-tests-browser-release-scale.md 0929/11-09
The provider sandbox never ran. bubblewrap 0.9.0 stops parsing an `--args`
file at the first non-option and never hands the remainder back, so the
command written into that file was silently dropped: bwrap printed its usage
text, exited 1, and the provider produced no evidence at all. The options
still travel in the args file — that is what keeps host paths and credentials
out of `/proc/<pid>/cmdline` — but the command now rides on real argv, and
`encodeProviderBwrapInput` refuses a `--` so the drop cannot come back.
The scope wrapper then could not exit. It read the supervisor's liveness pipe
through `fs`, which runs a blocking `read(2)` on a threadpool thread; the
supervisor holds that pipe open for the scope's whole life, so the read never
returned and closing the descriptor did not interrupt it. Once bubblewrap
finished the wrapper deadlocked in `process.exit`, the scope outlived the
provider, and a completed run was reported as a timeout kill. The channel is
now read through the event loop, so teardown is observable and terminal.
Creation modes were left to the ambient umask. `mkdir(mode)` and `open(mode)`
are requests the kernel subtracts the umask from, so a runner exporting a
restrictive umask produced directories it could not enter and handed `tar` a
file it could not re-open. Private modes are pinned instead of inherited.
Promotion cleanup deleted before it checked. Removals run through a pinned
descriptor, so a leaf substituted after validation had this promotion's exact
five destroyed first and the substitution reported afterwards, leaving a
half-emptied directory a retry could not tell from a completed one. The name
is re-bound to the inode before anything is removed, so the failure is total.
Separately, release coherence proved the artifacts agreed with each other but
never that they belonged where they were going: a build whose runtime document
said `APP_ENV: local`, `AUTH_MODE: demo` and a loopback API is coherent with
itself and passed every gate. `public/` is copied verbatim into `dist/`, so
that local document shipped with every build regardless of what the build was
for. Runtime configuration now comes from a declared profile, and FE-GATE-027
refuses to admit an artifact to an environment it does not match — including
refusing an undeclared destination, so nothing is admitted by omission.
`REQUEST_TIMEOUT_MS` and `VITE_ROUTER_BASE_PATH` were validated and then
dropped: the V3 executor ran every operation on its contract's own deadline,
and Vite emitted root-absolute assets for a sub-path deployment. The timeout is
now a ceiling that may tighten a contract but never loosen one, and one base
path feeds the router, the Service Worker scope and the asset base together.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>