Commit Graph
10 Commits
Author SHA1 Message Date
DongHyeonka 8d328c9cea test(indexeddb): 차단 업그레이드 테스트가 500 ms 전이 상태를 폴링하지 않는다
문제
tests/browser-capabilities/indexeddb-runtime.spec.ts의 차단 업그레이드
테스트는 v2 runtime을 blockedTimeoutMs 500으로 시작한 뒤
expect.poll(lifecycleStatus)로 BLOCKED 상태를 기다린다. 이 상태는
500 ms 뒤 CLOSED/NOT_OPENED로 바뀌고, 폴링 한 번은 page.evaluate
왕복이다. 그래서 바쁜 호스트에서는 첫 관찰 전에 창이 닫혀 FE-GATE-008이
코드와 무관하게 떨어진다(리뷰 전체 실행에서 chromium·webkit 실패).

고른 방법
- 전이 상태 폴링을 지우고, 바로 뒤 settleLifecycleRuntime 결과
  (opened.error.code BLOCKED, recovery RELOAD_OTHER_CONTEXTS, status
  CLOSED/NOT_OPENED)로 차단을 판정한다. 전이 상태 BLOCKED는 제어한
  scheduler로 tests/unit/indexeddb-runtime.test.ts가 이미 고정한다.
- 버린 대안: blockedTimeoutMs를 늘리기. 창이 넓어질 뿐 경쟁이 남는다.
  runtime이 상태 변화를 기록하게 하기. 운영 코드에 테스트용 기록이
  생긴다.

위험·한계
- 실제 브라우저에서 getStatus()가 BLOCKED를 돌려주는 순간은 이 spec이
  더는 보지 않는다(단위 테스트가 본다).

검증
- RED: 창을 20 ms로 줄이면 수정 전 테스트가 chromium·webkit에서
  CLOSED/NOT_OPENED를 받아 실패했다(리뷰 실패와 같은 모양). 수정 뒤 같은
  20 ms에서 세 엔진 통과. 값은 500으로 되돌렸다.
- test:browser-capabilities 전체 63 passed(load 15~20). 5회 반복은 하지
  않았다.

Refs: docs/reviews/2026-11-03-maturity-review/11-tests-browser-release-scale.md 11-05
2026-11-04 20:34:22 +09:00
DongHyeonkaandClaude Opus 5.5 7f45afac7d fix(storage): report a future IndexedDB schema as INCOMPATIBLE and online-only (05-06)
An older tab that met a schema a newer release had upgraded got
MIGRATION_FAILED / READ_ONLY, but could not even read, and operators were sent
to the migration runbook. The VersionError on open now yields UNSUPPORTED /
ONLINE_ONLY with status INCOMPATIBLE, reads and writes give the same answer,
and the OPFS journal answers the same way.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-25 22:37:40 +09:00
DongHyeonkaandClaude Opus 5.5 3e37fbf0ed fix(storage): delete a partition's IndexedDB dataset when an authorized purge cannot open it (05-03)
LOGOUT and ACCOUNT_DELETION purged row by row and so needed an open that a
corrupt budget or binding row always rejected, leaving personal rows on the
device. After authority approval, a purge that finds the dataset rejected by
admission now deletes that partition's own database and reports it; healthy
datasets and other partitions are untouched.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-25 22:24:55 +09:00
DongHyeonkaandClaude Opus 5.5 8fc816ee25 fix(storage): hold a per-transaction lock so reconcile skips a live OPFS put (05-01)
Reconcile cleaned up any incomplete journal row, including a put still
running in another tab, and the put then reported success for deleted files.
Put and delete now hold a Web Lock per transaction from begin to return;
reconcile takes those locks with ifAvailable, re-reads the page under them
and reports the rows it skipped (D-3).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-25 22:09:30 +09:00
DongHyeonkaandClaude Opus 5.5 d7fc464426 test(browser-capabilities): pin chunk-failure wording on all three engines (R3-7)
Run the app's isChunkLoadFailure (served by the dev server) against the real
error each engine raises for a missing dynamic-import chunk. Passes on
Chromium, Firefox and WebKit. Record the WebKit run (e2e 39, capabilities 17).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-24 15:48:57 +09:00
DongHyeonkaandClaude Opus 5.5 407046407a test(browser-capabilities): real unbound showOpenFilePicker call and Vary: Accept-Encoding cache lookup (R3-6)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-24 15:32:42 +09:00
donghyeon-ka ec7f20e2ee refactor: 프론트엔드 리펙토링 2026-09-18 22:05:42 +09:00
DongHyeonkaandClaude Opus 5 7485cd86e4 fix: let the browser, visual and performance evidence describe the product again
Four browser-capability specs never reached the code they were named for. The
`PRESIGNED_TRANSFER_V1` envelope gained a top-level `protocol` field, and the
fixtures kept answering without it, so every capability was refused before any
object request was made: the download and part-upload success paths were
asserting against an empty transcript rather than exercising a real GET or PUT.
The fixtures now speak the protocol they claim to, and the part-deletion
expectation carries the physical effect the adapter reports.

A refused capability document also answered `recovery: NONE`, telling the
caller there was nothing to be done. The design record fixes this class of
refusal as re-issuable and the vault already answers `REISSUE_CAPABILITY` for
it, so the HTTP decoder disagreed with both. It now agrees.

Lab performance produced no evidence at all. Playwright matches accessible
names by substring, so the navigation entry "플랫폼 구성" also matched the home
page's "플랫폼 구성 보기" call to action; the locator resolved to two links and
the run died on a strict-mode violation before the first measurement. With an
exact match the metrics are collected, and they show the named-interaction
budget is missed on this machine — a real signal that was previously invisible.

The platform overview baseline was captured before the reference routes moved
from `integration-defined` to `session-required` and was never regenerated, so
the only visual gate that could catch a regression on that page was failing for
its own staleness. Regenerated after confirming the diff is exactly that label.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-15 16:49:48 +09:00
DongHyeonka c6da03369c refactor: 리펙토링 2026-08-01 19:39:59 +09:00
donghyeon-ka 6c52cdb916 feat: 기능 추가 과정중 2026-07-30 15:58:20 +09:00