Description

Per the Fetch spec, the Response constructor should validate:

1. Status range: Throw RangeError if status is not in 200-599
2. Null body status: Throw TypeError if body is provided with a null-body status (204, 304)
3. Status text: Validate for invalid characters

Changes

src/response.js

• Added NULL_BODY_STATUSES set ([101, 204, 304])
• Status range validation throws RangeError for status outside [200, 599]
• Status text validation rejects CR, LF, and NUL characters
• Null body status check throws TypeError when body is non-null with status 204/304/101
• Response.error() now uses Reflect.construct to bypass constructor validation since it uses status 0

src/index.js

• Internal HTTP response handling for 204/304 now passes null body instead of the response stream, since these statuses must not have a body per spec

test/response.js

• 5 new test cases for status range and null body validation

Verification

• All 392 tests pass (5 new), only 3 pre-existing unrelated failures remain
• All existing 204/304 response handling continues to work correctly
• Git commit signed and verified