refactor: 프론트엔드 리펙토링

docs/testing/taxonomy.md

@@ -11,7 +11,7 @@ Each gate is blocking in its declared scope. Failures are not downgraded with
 | unit | `pnpm test:unit` | Node-only domain/application/pure policy/runtime units; no systemd/bwrap/cgroup prerequisite | `artifacts/tests/unit.xml` |
 | capability contract | `pnpm test:contract` | reusable capability consumer contracts | `artifacts/tests/contract.xml` |
 | component | `pnpm test:component` | React/hook/UI behavior | `artifacts/tests/component.xml` |
-| integration | `pnpm test:integration` | HTTP/MSW, IndexedDB and composed browser-runtime boundaries | `artifacts/tests/integration.xml` |
+| integration | `pnpm test:integration` | HTTP/MSW, IndexedDB, composed browser-runtime boundaries, child-process/filesystem/IPC integration | `artifacts/tests/integration.xml` |
 | system / CI runner | `pnpm test:system` | compatible Linux host with systemd, bubblewrap, cgroup v2 and CI-provider process controls | `artifacts/tests/system.xml` |
 | end-to-end | `pnpm test:e2e` | pinned browser engines | `artifacts/tests/e2e/` |
 | accessibility | `pnpm test:a11y` | pinned browser engines | `artifacts/tests/a11y.json` |
@@ -64,7 +64,11 @@ CI / release assurance:
 
 A host-level process/sandbox test must not be placed in `tests/unit` merely
 because it uses Vitest. The classification follows the system boundary and
-prerequisites, not the test framework.
+prerequisites, not the test framework. Process-heavy tests that spawn child
+processes but do not require privileged host facilities belong in
+`tests/integration`; for example the provider guardian transaction protocol
+lives at `tests/integration/provider-guardian-transaction.test.ts`. Its
+handshake timeout is a test watchdog, not a production protocol deadline.
 
 End-to-end and automated accessibility scenarios run on the pinned Chromium,
 Firefox, and WebKit engines. The responsive contract explicitly exercises