As reported in https://github.com/vercel/next.js/issues/56919 it is possible for the ReadableStream controller to be written to after it is already closed. This is because inside an async context a Float method such as `ReactDOM.preload()` can attempt to flush newly created Resources even after the stream has completed.

React version: 

The underlying bug has been in React since Float landed. The expression of the Bug as reported in the Next.js repo was landed in: https://github.com/facebook/react/commit/701ac2e57290f913502c6012c15e815f412f84b7
The first Canary release to have this new expression was: [18.3.0-canary-f81c0f1ed-20230927](https://www.npmjs.com/package/react-dom/v/18.3.0-canary-f81c0f1ed-20230927)


## Steps To Reproduce

1. use `react-dom/server.edge`
2. Ensure the environment supports AsyncLocalStorage
3. Call Float method like `ReactDOM.preload(...)` after an await after the stream has closed

## The current behavior
If the conditions are right the Float call will initiate a write after the stream has closed and there will be a thrown exception

## The expected behavior
The Float call is ignored after the stream has closed. There are no errors
return request.formState;
}
export function getResumableState(request: Request): ResumableState {
  return request.resumableState;
}
export function getRenderState(request: Request): RenderState {
  return request.renderState;
}
function addToReplayParent(
  node: ReplayNode,
  parentKeyPath: Root | KeyNode,
  trackedPostpones: PostponedHoles,
): void {
  if (parentKeyPath === null) {
    trackedPostpones.rootNodes.push(node);
  } else {
    const workingMap = trackedPostpones.workingMap;
    let parentNode = workingMap.get(parentKeyPath);
    if (parentNode === undefined) {
      parentNode = ([
        parentKeyPath[1],
        parentKeyPath[2],
        ([]: Array<ReplayNode>),
        null,
      ]: ReplayNode);
      workingMap.set(parentKeyPath, parentNode);
      addToReplayParent(parentNode, parentKeyPath[0], trackedPostpones);
    }
    parentNode[2].push(node);
  }