fix: make OPFS finalization and public cache repair failure-atomic

STO-RR-01. finalizePut re-acquired the origin mutation lease it was already
holding. A Web Lock is not reentrant, so an ordinary PUT stopped for good at
FINALIZE; it now calls the locked cleanup directly. A strict non-reentrant fake
lease manager pins one acquire and one release per finalization. The adapter no
longer reports a failed finalization as a plain write success either: the
journal row stays COMMITTED for reconciliation, but the caller is told the
write did not settle.

STO-RR-02. A failure raised while serving a validated request now carries that
request's kind. Defaulting every catch to CAPABILITIES made the client's own
expected-kind check reject genuine quota, integrity and abort failures as
protocol breaches and report them as UNSUPPORTED. Only an envelope the runtime
could not read still answers at protocol level.

STO-RR-03. The worker client decodes a response instead of adopting it: exact
own-data descriptors, the negotiated protocol version, the exact awaited kind,
a code inside the closed BrowserDataFailure set and a boolean retryable. An
accessor, a proxy trap, an inherited or extra field and an unknown code all
close the call as UNSUPPORTED rather than leaving it to time out.

STO-RR-04. A marker read that fails transiently is unknown, not damaged, so it
no longer deletes the candidate that may be serving traffic. Only a confirmed
corrupt or missing marker enters the repair path.

STO-RR-05. Staging never deletes a candidate it did not create. A repair
replaces exact entries in place, so a failed fetch leaves every healthy asset
and the active release usable; a candidate this call created is still removed
on failure.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

src/adapters/storage/opfs/opfs-byte-store-adapter.ts

@@ -312,12 +312,23 @@ export function createOpfsByteStoreAdapter(
         prepared.value,
         request.signal,
       );
-      if (finalized.ok) {
-        await dependencies.journal.complete(
-          transactionId,
-          begun.value.fencingToken,
+      if (!finalized.ok) {
+        // STO-RR-01. The commit fence already passed, so the payload is durable
+        // and the journal keeps its COMMITTED record for reconciliation to
+        // settle. What did not happen is finalization: the previous generation
+        // and the staging directory are still present. Reporting a plain
+        // success here would claim a settled state nobody observed, so the
+        // worker's own failure is surfaced and the record is left recoverable.
+        return observeFailure(
+          rebaseFailure(finalized.error, "OBJECT_WRITE"),
+          dependencies.observer,
+          request.source.byteLength!,
         );
       }
+      await dependencies.journal.complete(
+        transactionId,
+        begun.value.fencingToken,
+      );
       observeOpfsSafely(dependencies.observer, {
         operation: "OBJECT_WRITE",
         outcome: "SUCCEEDED",