fix: bound browser transfer leases and effect reporting
BT-X-01: add the shared abortable-operation utility with golden tests for first terminal owner, idempotent close, listener and timer cleanup under a throwing scheduler, observed late rejection and late-handle compensation. It carries no subsystem result taxonomy. BT-PRE-01: make the presigned download lease lazy and single-start. open() now validates, claims and consumes the capability without any network I/O; the fetch, the transfer deadline and the expiry recheck happen at first stream consumption. The source gained close(), which discards an unused lease with no I/O and otherwise cancels the body and releases the scope exactly once. BT-UP-01: require removeEventListener in the AbortSignal structural guard and isolate release cleanup so a hostile facade cannot replace a typed terminal result with a rejection. BT-UP-03: deleteDatabase cannot be cancelled after dispatch, so a blocked deadline now returns PENDING with effect UNKNOWN instead of a failure that reads as NOT_APPLIED. A realm-scoped (factory, databaseName) registry prevents recreating the partition until the native request settles. BT-UP-04: reject non-finite and negative upload clocks as a dependency failure instead of letting them bypass every capability expiry comparison. BT-IMG-02: replace the naive Cache-Control quote stripping with a quote- and escape-aware tokenizer, so max-age="60 or 60" is no longer read as 60 and a comma inside a quoted extension is not a directive boundary. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5
parent
8f67974f68
commit
cc4e875c2d
@@ -113,6 +113,13 @@ export type PresignedDownloadByteSource = FileByteSource &
|
||||
byteLength: number;
|
||||
capability: PresignedDownloadCapability;
|
||||
integrity: "VERIFIED_ON_SUCCESSFUL_EXHAUSTION";
|
||||
/**
|
||||
* BT-PRE-01. Discards the lease. Before the first `stream()` this performs
|
||||
* no network I/O at all; during streaming it cancels the body and releases
|
||||
* the timer and listeners exactly once. Every consumer must call it in a
|
||||
* `finally`, including on a pre-stream failure.
|
||||
*/
|
||||
close(): void;
|
||||
}>;
|
||||
|
||||
export interface PresignedDownloadSourcePort {
|
||||
|
||||
@@ -40,6 +40,14 @@ export type UploadPartReceipt = UploadPartDescriptor &
|
||||
receiptToken: string;
|
||||
}>;
|
||||
|
||||
export type PartitionDeleteOutcome =
|
||||
| Readonly<{ state: "DELETED"; effect: "APPLIED" }>
|
||||
| Readonly<{
|
||||
state: "PENDING";
|
||||
effect: "UNKNOWN";
|
||||
reason: "BLOCKED_DEADLINE";
|
||||
}>;
|
||||
|
||||
export interface UploadRangeReader {
|
||||
readonly byteLength: number;
|
||||
readRange(input: Readonly<{
|
||||
@@ -273,7 +281,13 @@ export interface ResumableUploadCheckpointAdmin {
|
||||
* Account/logout lifecycle operation for this already-bound opaque partition.
|
||||
* The adapter closes its connection before deletion and bounds blocked waits.
|
||||
*/
|
||||
/**
|
||||
* BT-UP-03. An IndexedDB `deleteDatabase()` request cannot be cancelled once
|
||||
* dispatched, so a blocked deadline is not evidence that nothing happened.
|
||||
* `PENDING` reports the effect honestly as `UNKNOWN`; only pre-dispatch
|
||||
* problems are ordinary failures.
|
||||
*/
|
||||
deletePartition(
|
||||
signal?: AbortSignal,
|
||||
): Promise<BrowserDataResult<Readonly<{ state: "DELETED" }>>>;
|
||||
): Promise<BrowserDataResult<PartitionDeleteOutcome>>;
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user