Define wrapper Response(Response, init) semantics

[medz]

Parent: #36

Problem

IO/JS wrapper Response(Response, init) currently aliases the wrapped response host and ignores init. This is not a standard Response() constructor shape, so the package should explicitly decide whether this extension should be removed, rejected, or defined as clone/copy semantics.

Investigation scope

• Identify why wrapper Response(Response, init) support exists and whether callers rely on it.
• Compare with standard Response() body semantics, where arbitrary objects are stringified rather than treated as response copies.
• Decide behavior for init overrides if the extension is retained.
• Add tests so IO/JS wrapper behavior cannot silently alias mutable state.

References

• https://developer.mozilla.org/en-US/docs/Web/API/Response/Response
• https://fetch.spec.whatwg.org/

[coderabbitai]

🔗 Related PRs

#11 - refactor(fetch): align request and response semantics with web [merged]
#35 - fix(fetch): copy IO Headers constructor input [closed]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!