vercel.com observed a bug where a stylesheet hoisted using a `precedence` was reordered after an update. This is not correct semantics (once a hoisted stylesheet is inserted it should remain in place until removed)

Investigating the React implementation I observed that if you insert a hoisted stylesheet during a synchronous render and later render a new reference to that stylesheet in a transition React incorrectly considers the stylesheet not loaded and tries to coordinate it's loading the the commit. This is erroneous as once a stylesheet is in the DOM it should never be re-inserted (moved).
return null;
}
export function commitHydratedContainer(container: Container): void {
  
  retryIfBlockedOn(container);
}
export function commitHydratedSuspenseInstance(
  suspenseInstance: SuspenseInstance,
): void {
  
  retryIfBlockedOn(suspenseInstance);
}
export function shouldDeleteUnhydratedTailInstances(
  parentType: string,
): boolean {
  return (
    (enableHostSingletons ||
      (parentType !== 'head' && parentType !== 'body')) &&
    (!enableFormActions || (parentType !== 'form' && parentType !== 'button'))
  );
}
export function didNotMatchHydratedContainerTextInstance(
  parentContainer: Container,
  textInstance: TextInstance,
  text: string,
  isConcurrentMode: boolean,
  shouldWarnDev: boolean,
) {
  checkForUnmatchedText(
    textInstance.nodeValue,