chore: sync the frontend template from 4dc033c to 8157ad4

The product was materialized from the template at `4dc033c` and has stayed
on it through 43 template commits, so it was missing all three rounds of
adapter remediation — including files it never had, such as the shared
`abortable-operation` primitive and the `exact-snapshot` decoder that
later fixes are written against. Taking only the newest round was not
possible for that reason: the delta is coherent only as a whole.

The product had not touched `src/adapters` at all since materialization,
so the 140-file delta applied with a three-way merge and no conflicts.
`package.json` was the single overlap and merged cleanly: the product owns
`name`, the template contributed `check:adapter-inventory`,
`check:remediation-ledger` and the image-resolve-signal type fixture.
All 24 product-owned files — README, index.html, CI workflow, i18n
catalog, home page, generated schemas, evidence scripts, component and
visual snapshots — are byte-identical to `main`.

`template.lock.json` now pins the synced revision and tree.

Verified in this repository, not inherited from the template: six type
projects, lint, nine gates (adapter inventory, remediation ledger,
registries, diagnostics, realtime boundaries, architecture, browser
file/storage boundaries, optional recipes, documentation), the production
build, and 2,054 of 2,073 tests. The 19 failures are all in
`tests/unit/ci-artifact-contract.test.ts` and are the same pre-existing
sandbox RLIMIT, EMFILE, umask and `/tmp` permission behaviour the template
records; four suites that failed once under parallel load pass in
isolation.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

docs/architecture/decisions/VD-23-api-transport-selection-and-rest-execution.md

@@ -262,6 +262,55 @@ auth-required operation은 session state가 `authenticated`가 아니면 fetch
 `integration-failed`, `unauthenticated`와 credential attach rejection을 anonymous
 request로 downgrade하지 않는다.
 
+#### 5-0. Logical effect certainty는 단조 증가한다
+
+`PhysicalAttemptState`는 현재 attempt만 설명한다. logical execution 전체에는
+별도의 monotonic accumulator를 두고 `joinMutationEffectCertainty`로 join한다.
+join 순서는 보수적이다.
+
+```text
+NOT_STARTED < NOT_APPLIED < MAYBE_APPLIED < APPLIED_CONFIRMED
+```
+
+`fetch()` dispatch 시점에 command는 즉시 `MAYBE_APPLIED`를 기록한다. 이후 retry
+loop entry, pre-dispatch final invariant, scope fence, cancellation, timeout
+return은 모두 accumulator를 읽는다. 아직 보내지 않은 새 retry가 있다는 이유로
+전체 logical operation을 `NOT_STARTED`로 되돌리지 않는다. query operation은
+`NOT_APPLICABLE`로 남고 이 lattice를 쓰지 않는다.
+
+#### 5-1. Installed auth profile registry (V3 집행)
+
+`installRestAuthProfileRegistry()`가 composition 시점에 profile을 한 번 설치하고
+`INSTALLED_REST_AUTH_PROFILES`가 유일한 authority다. contract composition
+(`assertExecutionPolicy`)은 등록되지 않은 `authProfileId`를 거절하므로 executor는
+runtime에 profile을 발명하지 않는다. profile은 다음을 exact하게 소유한다.
+
+- Fetch `credentials` (credential collaborator가 바꿀 수 없다)
+- `allowedCredentialHeaders`: 이 operation이 허용하는 정확한 proof header 집합
+- `requiredCredentialHeaders`: dispatch 전에 반드시 관찰되어야 하는 집합
+
+`CredentialPatchOutcome.READY`는 proof header만 담는다. `credentials` field는
+제거되었다. credential owner가 transport-owned header(`accept`, `content-type`,
+`idempotency-key`)나 forbidden header를 넣거나, profile이 허용하지 않는 header를
+넣거나, required header를 빠뜨리면 `AUTH_INTEGRATION_FAILURE`이고 fetch 0회이며
+command effect는 `NOT_STARTED`다. `idempotency-key`는 contract-owned이므로 더
+구체적인 `UNEXPECTED_IDEMPOTENCY_KEY` request violation으로 남는다.
+`UNAUTHENTICATED`는 user/session state이지 integration failure가 아니다.
+
+transport-owned header는 credential header 뒤에 기록되어 key ordering으로도
+shadow될 수 없고, final invariant가 `init.credentials`와 profile을 다시 대조하며
+allowed/required credential header 집합을 독립적으로 재검증한다.
+
+`AUTH_MODE=demo`는 profile을 약화시키지 않는다. `createDemoSessionAdapter`가
+고정된 비밀 아닌 `DEMO_AUTHORIZATION_MARKER` proof header를 제공하여 strict
+`REFERENCE_EXTERNAL_BEARER`를 그대로 만족시킨다. 진짜 anonymous backend는 별도
+anonymous contract/profile을 composition에서 선택해야 한다.
+
+credential collaborator는 `AuthOperationContext { signal, deadlineAtMonotonicMs }`를
+받는다. cooperative owner는 스스로 중단하고, non-cooperative owner도 executor가
+같은 lifetime signal과 race하므로 operation 수명을 넘기지 못하며 late completion은
+관찰되지 않는다.
+
 ### 6. Cookie auth, CSRF와 CORS
 
 same-origin BFF cookie session을 기본 권장한다.