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).
<link rel="foo" href="foo" onLoad={() => {}} />
            </head>
            <body>
              {}
              <meta name="foo" content="foo" itemProp="a prop" />
              {}
              <meta name="foo" content="foo" />
              {}
              <title>title</title>
              <div itemScope={true}>
                <div>
                  <div>deep hello</div>
                  {}
                  <meta name="foo" content="foo" itemProp="a prop" />
                </div>
              </div>
            </body>
          </html>
          <link rel="foo" href="foo" />
        </>
      );
    }
    await act(() => {
      renderToPipeableStream(<App />).pipe(writable);
    });
    expect(getMeaningfulChildren(document)).toEqual(
      <html itemscope="">
        <head>
          {}
          <link rel="stylesheet" href="stylesheet" data-precedence="default" />