chore(review): 1105 성능·구조 조치 브랜치를 합친다

합치며 고친 것: 두 브랜치가 따로는 맞고 합치면 어긋나는 곳 둘.
- 1105/12-04(실행 격리 브랜치)는 `vite.config.ts`가
  `scripts/lib/run-isolation.ts`를 가져오게 해, 저장소를 임시 루트에 복사해
  빌드하는 두 목록(`scripts/scale/measure-feature-shape-growth.ts`,
  `tests/unit/product-feature-selection-build.test.ts`)에 그 파일을 더했다.
  1105/15-03(이 브랜치)은 두 목록을 `scripts/lib/vite-build-inputs.ts` 하나로
  옮겼다. 두 파일의 충돌은 15-03 쪽으로 풀고, 옮긴 목록에
  `scripts/lib/run-isolation.ts`를 더한다. 더하지 않으면
  `tests/unit/vite-build-inputs.test.ts`가 그 파일 이름을 대며 실패하고,
  임시 루트 빌드 두 곳이 "Could not resolve './scripts/lib/run-isolation.ts'"로
  실패한다.
- `scripts/lib/removal-fixture.ts`의 문서 테스트 목록에 03-01(HTTP 판정
  브랜치)과 16-01(이 브랜치)이 각자 한 줄씩 더했다. 두 줄을 모두 둔다.

검증: desktop batch에서 확인.
node scripts/run-vitest.ts run tests/unit/vite-build-inputs.test.ts tests/unit/feature-shape-growth.test.ts tests/unit/product-feature-selection-build.test.ts

Refs: 1105/12-04, 1105/15-03, 1105/03-01, 1105/16-01
This commit is contained in:
DongHyeonka
2026-11-06 02:59:02 +09:00
43 changed files with 1151 additions and 110 deletions
@@ -60,6 +60,23 @@ function Metric({
);
}
/**
* 1105/15-01. The release metrics before the summary resolves, or after it
* failed: the resolved metrics' labels and hint lines, so the grid keeps its
* height. The status takes the first card's value and stays short enough for
* one line in the narrowest card (13rem), as a build id does.
*/
function ReleaseMetricsPlaceholder({ status }: Readonly<{ status: string }>) {
return (
<>
<Metric label="빌드" value={status} />
<Metric label="릴리스" value="—" />
<Metric label="설정 스키마" value="—" hint="—" />
<Metric label="계약 집합 다이제스트" value="—" hint="—" />
</>
);
}
type RouteRow = (typeof ROUTE_REGISTRY)[keyof typeof ROUTE_REGISTRY];
const ROUTE_COLUMNS: readonly DataTableColumn<RouteRow>[] = Object.freeze([
@@ -419,10 +436,18 @@ export function PlatformOverviewPage({
부팅 시 경계 검사를 통과한 런타임 설정과 릴리스 매니페스트에서 옵니다.
</p>
</header>
<dl className="platform-metric-grid" aria-live="polite">
{release === "failed" ? (
<Metric label="상태" value="런타임 정보를 확인하지 못했습니다." />
) : release ? (
{/* 1105/15-01. The same four metrics, with the same hint lines, in
every state: the grid used to grow from one card to four with
hints once the summary resolved, about 30-100 ms after the title,
and pushed everything below it 21 px (CLS 0.0046 on a direct
visit). Only the values change; `aria-busy` says when they are
not there yet (the visual test waits on it). */}
<dl
className="platform-metric-grid"
aria-live="polite"
aria-busy={release === null}
>
{release !== null && release !== "failed" ? (
<>
<Metric label="빌드" value={release.buildId} />
<Metric label="릴리스" value={release.releaseId} />
@@ -450,7 +475,11 @@ export function PlatformOverviewPage({
/>
</>
) : (
<Metric label="상태" value="런타임 정보를 확인하고 있습니다." />
<ReleaseMetricsPlaceholder
status={
release === "failed" ? "확인하지 못했습니다." : "확인하고 있습니다."
}
/>
)}
</dl>
</section>
+6
View File
@@ -3,6 +3,12 @@
color: var(--color-content);
background: var(--color-surface);
font-family: var(--font-sans);
/* 1105/15-05. The route loading surface fits a 720 px window and the
home page does not, so the first render added a classic (non-overlay)
scrollbar and pushed the header's right side 15 px left (CLS 0.0002 at
1280x720 and 1366x657). The gutter is reserved from the first frame;
overlay scrollbars take no space either way. */
scrollbar-gutter: stable;
}
body {