docs(mobile): state the on-settle reason that holds for pipelined bundle reads

Claude-Session: https://claude.ai/code/session_01JNnE9qzUZMMnqpZWCqM3nb
This commit is contained in:
Jinwoo-H
2026-09-22 22:46:32 -04:00
parent 5761e21a31
commit fe41226ef5
@@ -18,8 +18,8 @@ import { rpcResultVariant } from './rpc-operation-result-reader'
// The reads that hand a paired phone the desktop's mobile web bundle. All are
// `require-result-or-throw`: there is no partial success here, and a salvage policy would produce a
// half-bundle that fails a hash check much later, far from the cause. All settle at `on-settle`,
// because each reply is acted on before the next request is built — the manifest decides which
// windows to read, and a chunk or range reply decides whether its asset is whole.
// because each reply is interpreted as soon as it lands and waits on no sibling: the manifest before
// any window is planned, and each chunk or range while the other reads are still in flight.
/** The whole manifest plus the chunk size the host will serve it at. */
export const mobileWebBundleManifestRead = defineRpcOperation({