refactor: 프론트엔드 리펙토링

docs/operations/adapter-remediation-ledger.md

@@ -337,7 +337,14 @@ Run on the landed tree. Only what actually passed is claimed as passing.
 | --- | --- | --- |
 | `tests/unit/ci-workflow-generation.test.ts` | 82 failed / 325 passed | Identical on the pre-change baseline (`git stash` comparison). The subprocess gates it spawns cannot run in this sandbox. |
 | `tests/unit/ci-artifact-contract.test.ts` | fails | Unchanged pre-existing sandbox, cgroup and `/tmp` permission behaviour. |
-| `tests/unit/security-followup.test.ts`, `tests/unit/provider-guardian-transaction.test.ts`, `tests/unit/risk-coverage.test.ts` | flaky under full-suite load | All three pass in a fresh process (78 passed together). They spawn and reap process groups, so their timing assertions are load sensitive. |
+| `tests/unit/security-followup.test.ts`, `tests/unit/provider-guardian-transaction.test.ts`, `tests/unit/risk-coverage.test.ts` | flaky under full-suite load | Historical baseline result. All three passed in a fresh process (78 passed together). |
+
+> Current classification update (2026-09-18): the provider guardian transaction
+> suite moved to `tests/integration/provider-guardian-transaction.test.ts`.
+> It spawns child processes and exercises filesystem/IPC/process lifecycle, so it
+> is not part of the pure unit pool. Its READY/PUBLISHED wait uses a dedicated
+> test watchdog rather than treating a 1-second scheduler delay as a production
+> protocol deadline.
 
 ### Destructive fixture hazard — fixed
 
@@ -375,7 +382,7 @@ files above plus the two flaky-under-load ones:
 | `tests/unit/ci-workflow-generation.test.ts` | 82 | Identical on the pre-change baseline (`git stash` comparison). Its subprocess gates cannot run in this sandbox. |
 | `tests/unit/ci-artifact-contract.test.ts` | 19 | Unchanged pre-existing sandbox, cgroup and `/tmp` permission behaviour. |
 | `tests/unit/security-followup.test.ts` | 2 | Passes in isolation. |
-| `tests/unit/provider-guardian-transaction.test.ts` | 1 | Passes in isolation. |
+| `tests/unit/provider-guardian-transaction.test.ts` (historical path; now `tests/integration/provider-guardian-transaction.test.ts`) | 1 | Historical baseline: passed in isolation; current suite is classified as process integration. |
 
 1619 passed / 1723 total, and `tests/unit/removal-fixture.test.ts`,
 `tests/unit/supply-chain.test.ts` and

docs/operations/browser-file-storage-recovery.md

@@ -148,6 +148,9 @@ read-only나 online-only가 사용자 작성 내용을 잃게 한다면 먼저 e
 ### 신호
 
 - `BLOCKED`, `UPGRADE_BLOCKED` 또는 blocked duration bucket 증가
+  - live attempt가 기다리는 동안 status는 `BLOCKED`
+  - blocked deadline settle 뒤에는 open result가 `BLOCKED` failure여도
+    runtime status는 `CLOSED / NOT_OPENED`
 - `versionchange` 뒤 connection이 남음
 - repeated reload/update loop
 - open/maintenance의 `POLICY_REJECTED`: immutable dataset binding missing/mismatch
@@ -500,16 +503,13 @@ browser engine/version, fixture ID, fault phase, bounded counts/buckets와 PASS/
 
 promotion 직전에는 다음 repository evidence도 함께 보존한다.
 
-- `test:browser-capabilities`가 만든 JUnit에서 Chromium, Firefox, WebKit이 동일
-  14개 testcase set(File 2, IndexedDB 4, OPFS/Cache/StorageManager 각 1,
-  cross-context invalidation 2, presigned streaming download/multipart
-  upload/Image CDN 각 1)을 실제 실행해 총 42개이며 failure/error/skipped가 모두
-  0이어야 한다.
-  `verify:browser-capability-evidence`가 engine 집합과 testcase 동일성을
-  기계적으로 검증한다. 현재 artifact는 Chromium/Firefox 14개씩 총 28개가
-  통과했지만 WebKit 실행에 필요한 native libraries(예:
-  `libbacktrace.so.0`, `libevent-2.1.so.7`, `libjxl.so.0.8`,
-  `libavif.so.16`과 WPE 계열)가 이 host에 없으므로 아직 promotion 가능 상태가
+- `test:browser-capabilities`가 만든 JUnit에서 Chromium, Firefox, WebKit이
+  source suite의 동일 testcase set을 실제 실행하고 failure/error/skipped가 모두
+  0이어야 한다. 구체적인 case 수는 이 runbook에 복제하지 않는다.
+  `verify:browser-capability-evidence`가 Chromium을 baseline으로 testcase set과
+  engine 집합을 동적으로 검증한다. native capability가 없는 engine도 testcase를
+  skip하지 않고 adapter의 명시적 `UNSUPPORTED`/degraded 결과를 검증해야 한다.
+  세 engine 중 하나라도 실행되지 않은 artifact는 promotion 가능 상태가
   아니다.
 - `artifacts/quality/vite-module-inventory.json`에서 optional runtime source root가
   production chunk에 없음을 `check:optional-recipes`로 검증한다.