fix(storage): match the OPFS runbook to the adapter and drop the dead EFFECT_UNKNOWN branch (05-09)

The runbook named failure codes the adapter stopped using and promised a
resume and a quarantine reconcile never does. It now states the put's own
code with RECONCILE, the skipped and failed row counts, and what reconcile
really does per phase. The worker never sent EFFECT_UNKNOWN and the client
refused it, so the cleanup effect type and its two adapter branches go.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
DongHyeonka
2026-09-25 22:44:51 +09:00
co-authored by Claude Opus 5.5
parent 2b24f6d8f0
commit 4d8ceade21
5 changed files with 38 additions and 27 deletions
@@ -233,11 +233,12 @@ export type OpfsPreparedObject = OpfsPreparedObjectV1 | OpfsPreparedObjectV2;
/**
* STO-01. Compensation is only allowed to release journal and budget state
* after the physical effect is confirmed. `EFFECT_UNKNOWN` is never a success.
* after the physical effect is confirmed. An effect the worker cannot confirm
* comes back as a failure, never as a success value (05-09).
*/
export type OpfsCleanupEffect =
| Readonly<{ kind: "CLEANED" | "ALREADY_CLEAN" }>
| Readonly<{ kind: "EFFECT_UNKNOWN" }>;
export type OpfsCleanupEffect = Readonly<{
kind: "CLEANED" | "ALREADY_CLEAN";
}>;
export type OpfsJournalMutation = "PUT" | "DELETE";
export type OpfsJournalPhase =