max-width 8.5rem과 7rem 때문에 모든 언어에서 선택값이 잘렸다
("Light then", "Englisl", "라이트 테ㅁ"). 커밋된 시각 골든에도 잘린
머리글이 들어 있어, 시각 테스트가 결함을 정답으로 지키고 있었다.
고정 폭을 지웠다. 좁은 화면은 기존 메뉴 서랍 배치가 그대로 맡는다.
새 i18n e2e 테스트가 ko-KR, en-US, en-XA에서 선택 상자 폭을 브라우저가
옵션에 필요한 폭과 비교한다.
위험: 중간 폭에서 머리글이 넓어진다. responsive·app-shell·theme·compact
테스트가 통과했다.
검증: 새 테스트가 고치기 전 실패했고, 고친 뒤 chromium·firefox·webkit
모두 통과했다.
계약에 있는 컴포넌트 토큰 4개를 읽는 스타일이 없었다. 기본 버튼은
bg-action을 직접 썼고, 현재 메뉴는 --navigation-active-background의
계산식을 다시 적었다. 그래서 서비스가 이 토큰으로 브랜드를 바꿔도
화면이 바뀌지 않았다.
기본 버튼과 현재 메뉴가 토큰을 읽게 했다. 변형 버튼은 뒤에 오는 같은
우선순위 규칙이라 그대로 덮어쓴다. check:design-system이 계약의
컴포넌트 토큰을 읽는 스타일이 하나도 없으면 실패한다.
위험: 기본 버튼 배경 지정 방식이 utility에서 토큰으로 바뀐다.
보이는 색은 같다.
검증: 바꾸기 전 검사가 토큰 4개를 보고했고, 바꾼 뒤 통과했다.
라이트 테마에서 현재 메뉴 배경이 파랑이 아니라 분홍으로 그려졌다.
color-mix(in oklch, action 14%, panel)에서 panel이 oklch(1 0 0)으로
색상각 0을 명시해, 보간된 색상각이 255에서 345로 끌려갔다.
15곳의 혼합을 모두 in oklab으로 바꿨다. oklab에는 보간할 색상각이
없다. 흰색을 oklch(1 0 none)으로 바꾸는 방법은 버렸다. 앞으로 생길
무채색 토큰마다 같은 규칙을 기억해야 하기 때문이다.
check:design-system이 oklch·lch·hsl·hwb 혼합을 실패로 처리한다.
위험: 섞인 색이 미세하게 달라진다. 시각 골든을 갱신했다.
검증: 바꾸기 전 검사가 15곳을 보고했고, 바꾼 뒤 통과했다.
라이트 --color-focus가 흰 패널에서 2.33:1, surface-muted에서 1.95:1로
WCAG 1.4.11 기준(3:1)에 못 미쳤다. 포커스 링은 컨트롤에서 3px 떨어져
그려지므로, 대비를 따질 인접색은 컨트롤 뒤의 표면이다.
라이트 포커스를 oklch(0.52 0.15 230)으로 바꿨다. 가장 낮은 대비가
4.24:1이다. 다크는 그대로다. check:design-system이 두 테마에서 포커스
토큰과 표면 토큰 8종의 대비를 계산하고, 3:1 미만이면 실패한다.
안팎 이중 링은 버렸다. 한 색으로 충분하고 링 모양이 바뀌지 않는다.
위험: 포커스 링 색이 진해져 시각 골든이 바뀐다(별도 커밋에서 갱신).
검증: 토큰을 바꾸기 전 검사가 라이트 표면 8종 모두에서 실패했고,
바꾼 뒤 통과했다. 계산식은 브라우저 실측값 2.33:1과 일치한다
(tests/unit/oklch-contrast.test.ts).
impeccable이 읽을 제품 정보(사용자, 목적, 제약, 원칙)가 없었다.
화면 품질을 실제 브라우저에서 잰 기록도 없었다.
PRODUCT.md에는 사용자 답으로 확인한 제품 사실만 적었다. 감사 문서는
6개 화면을 라이트·다크, 1280·375·320 폭에서 잰 발견 8건(UI-01~08)을
가이드 36.3 양식으로 적었다. DESIGN.md는 만들지 않았다. 토큰 값을
문서 머리에 복사하는 형식이라 tokens/*.css와 갈라진 복사본이 생긴다.
위험: 문서만 추가한다. 동작 변경은 없다.
검증: verify:documentation PASS_SCOPED.
FOLLOW-UP.md lists, with priority and code locations, what this round
left as it is although practice would not: raised bundle budgets and
the near-full initial JS budget, the ungated remediation ledger check,
the readSubject breaking change, load-flaky tests, gaps outside the
completion criteria, and test-side workarounds. README section 11
links it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
WebKit reports the failed dynamic import as "TypeError: Importing a
module script failed." without the chunk URL, so the strict console
check rejected an expected failure. The recovery assertions already
passed on WebKit; the spec now passes on chromium, firefox and webkit.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-25 성숙도 리뷰 전 항목 반영 (v0.2.0).
- 레인 A~M과 검증 후 보완 레인 R·S·T, fix/session-subject-required 포함
- 발견 142건(중복 합쳐 138건) 해결. 01-06은 사용자 결정으로 상한만 반영
- 사용자 몫 U-1~U-5, F-11은 남음
- 상세: docs/reviews/2026-09-25-maturity-review/README.md 10·11절, CHANGELOG.md 0.2.0
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Both screens changed on purpose. 08-08 (dbe6b76) adds scroll-padding-top
for the sticky header, so the element screenshot of main no longer has
the header drawn over its top edge. 08-13 (d7b81c6) moves the reference
detail route under items/, and the longer path wraps one more line in
the overview's route table. The rest of both images is unchanged; at
4626b73 the old baselines still pass.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
"serves A's removed chunk from the previous cache" needs a route chunk of
A that B no longer ships. Route chunks used to differ only because they
embedded the build ID; since 09-02 (a8111f7) they do not, so A and B
emitted the same route chunks and the test failed in setup. Found by
running the whole e2e suite after integration and bisecting from
4626b73. Build B now appends an export to the not-found page, which a
dynamically imported module keeps.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The index notes now name the fixing commits, with user-owned remainders
and the 01-06 decision marked. Section 11 records the post-lane
verification, the gaps it found and closed, what could not be verified
on this host, and the user-owned items.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
FE-GATE-021..025 rebuilt from source and drilled that build, so the drilled
bytes were not the promoted release. production_gate now downloads the
promoted-release artifact, extracts it against immutable_build's digest and
runs each drill with --release-root; the CI contract rejects a rebuild.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
check-ci-contract only caught test files outside the gates; check:* scripts
such as check:request-fanout and check:remediation-ledger ran nowhere. The
new check reads config/ci/ungated-scripts.json; three checks are now wired
into FE-GATE-010 and FE-GATE-012 and the rest carry a reason.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Only the optional host was tested, so removing the composition line that hands
it the telemetry port kept every test green. The real composition with an
ACTIVE selection and a failing first install now must emit one event, and the
recipe doc names what the template still leaves unwired.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The growth test read docs/reviews/, which the removal fixtures do not copy and
README lets a project delete, so three removal checks failed with ENOENT. The
rationale now lives in config/scale/feature-shape-ceilings.json and a guard
test keeps code from reading the deletable history documents.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Resolving a policy only rejected predicates that admitted one of seven sample
ids, so a policy also allowing ':', '@' or letters passed BEGIN_PUT and failed
at FINISH_PUT. Writes now require the grammar alongside the policy, and the
samples cover those widenings so they are refused when the policy is resolved.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The budget is a size ratchet set about 100 bytes above the measured
reference bundle. file-transfer 55582 -> 55623 gzip bytes: 01-07 moves
the vault release into one finally around put() and open(). Same
rounding rule: 55700.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Early returns before resolve (invalid input, pre-aborted signal, byte-length
mismatch) left the capability registered, so maxActiveCapabilities: 1 refused
the next issuance. The public methods now release it once in a finally.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
d7b81c6 moved the detail route under items/ but this scan still opened
the old path, which now renders the not-found screen, so the @a11y run
would fail waiting for the detail heading. 38 @a11y tests pass on
chromium and firefox.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The in-progress section is folded into the contract table and the other
fixes list, and a known-limits section records what was not verified
(WebKit on this host) and what stays user-owned.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
package.json and public/release-manifest.json carry the version the
release manifest reports; the three tests that build a manifest for the
installed app use the same value. Test fixtures that pin 0.1.0 as an
arbitrary release stay as they are.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The gate count and the reference-feature LOC table were hand-typed and
drifted from the code, so they are removed; the LOC table now names the
files and the command that measures them. .env.example pointed to
layers.md for runtime profiles, which never described them; it now points
to the README section that does. ci-quality-gates.md lists the three
things DOCUMENTATION_READY checks, so the gate name is not read as a
general documentation-accuracy guarantee. The route list (③) and the
README config location (④) were already fixed by 14-03 and 13-15.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
VD-01 decision 3 hands unused diagnostics to tsc and turns off ESLint's
no-unused-vars for TS files, but tsconfig.base.json never enabled the
tsc check (D-19). The flag found 46 unused imports, types and helpers
across 22 files; none of them were read, so removing them changes no
behaviour.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The budget is a size ratchet set about 100 bytes above the measured
reference bundle. Measured after merging lanes B, D, F, G, H and J:
realtime 39903 -> 40886 gzip bytes (04-01..04-08 add reconnect rules and
SSE handling; 06-01, 06-02, 06-06, 06-09 add web-push fences and click
handling, and src/adapters/web-push is a realtime recipe source root).
Same rounding rule: 40900.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The save spec and the feature-shape growth test and script copy or drive the
reference feature. test:sample-removal left them behind as fixture-ID residue
and the growth test failed without the acceptance doc.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The freshness fixtures have a package.json but no node_modules. Started
outside pnpm, the gate's pnpm run began an install there and failed with
ERR_PNPM_IGNORED_BUILDS instead of testing the gate runner.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
pnpm verifies the install before a script, and a fixture running it with
CI=true against an install made without CI saw other settings and installed
through the linked .pnpm and .bin, rewriting the shared lock.yaml and shims.
Every fixture pnpm run now turns that check off; a test pins it for all.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
With the sample removed every route is public, so comparing access with
session-required no longer typechecked and test:sample-removal failed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Each run left 35 directories behind (repository-inventory, inventory-outside,
sw-assets, generator), and thousands piled up. They are now removed after
every test.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
09-03 moved the application graph behind a dynamic import, but only jsdom
checked it. A real production build whose installed messages collide now
opens in a browser and must show the boot error shell, not the loading shell.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
One run decided the release gate, the interaction included Playwright round
trips, and a server already on 4173 was measured instead of the build. Runs
now repeat with every sample kept, time the interaction in the page, use
--strictPort and check the served build, and stop the whole preview group.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Save failures outside sign-in, permission and retry still went into
ErrorSummary under "review the entered information". They now reach
FormFailureStatus with their own copy and action; the unused copy is gone.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Old-tab chunk recovery in the default configuration only had jsdom tests, and
the old-asset test checked its own hosting fixture. A spec now serves two real
builds: the old tab reloads once into the new one and not a second time. The
fixture test and the acceptance row now say what they cover.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The detail path /examples/reference-resources/:resourceId lost to the static
new and status routes, so an item with one of those ids opened the wrong
screen. The breaking route change carries registry evidence.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The scale evidence came from stub features, so the cost of one app growing
towards its declared ceiling was never measured. Copies of the reference
feature at 25 and 100 are now the baseline, and the acceptance matrix says
what the ceilings rest on and which axes stay unverified.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The page links prevented every click, so Ctrl/Cmd/Shift-click changed the page
in place instead of opening a new tab.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
AsyncSurface drew auth-required, forbidden and not-found query failures with
its own copy while the gallery used AccessSurface. Both now use one set, and
a state surface without a handler shows no dead button.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The route spec only checked that the protected screen opened, so a schema
violating 200 or a 503 still passed it. It now asserts the mocked row, and
a new spec saves once and retries after a 429 in a real browser.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
zod probed Function("") on its first object schema, which the production CSP
(no unsafe-eval) reported on every boot. Schema code now imports z from
src/contracts/zod.ts, enforced by a dependency-cruiser rule, and the CSP smoke
drops its init-script workaround.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>