Floot Request Body Single-Read Guard

• 01Infers a body mode from normalized Content-Type or accepts an explicit JSON, text, FormData, or ArrayBuffer mode.
• 02Creates one lazy reader that caches a single in-flight or completed promise so concurrent callers cannot consume the stream twice.
• 03Rejects an already-used body with a typed public error and wraps parse failures without returning payload values.
• 04Exposes immutable reader snapshots and an explicit handoff only after a successful read.
• 05Audits multiple readers, mixed modes, middleware-plus-handler reads, handoff conflicts, prior consumption, clone review, and raw-signature ordering.
• 06Returns deterministic frozen results, TypeScript declarations, zero runtime dependencies, and a non-mutating preservation-first integration plan.

• 01Floot and Node endpoints where middleware and handlers can compete for the same Fetch Request stream
• 02Serverless adapters that need one clear owner for JSON, form, text, or raw-byte parsing
• 03AI-generated endpoint code that retries body parsing after the stream has already been consumed

This listing is a downloadable Genesis code package. The ZIP includes reusable code and START-HERE directions.

1. 01

   Checkpoint and map body ownership

   Record the exact source and deploy revision, identify every middleware and handler consumer, raw-signature requirement, byte ceiling, and current parsed-value contract.

2. 02

   Integrate one owned reader

   Replace only the selected body-consumption call, pass the parsed handoff downstream, preserve endpoint responses and validation, and stop on a middleware or signature-order conflict.

3. 03

   Verify the real endpoint

   Run package, framework, auth, validation, raw-signature, payload-limit, error-path, regression, production-smoke, monitoring, and rollback checks before deployment.