Summary

enableFragmentRefs is enabled in every channel, so this inlines the enabled branch and removes the flag from ReactFeatureFlags and all of its forks.

Most of the diff is mechanical, but a few spots needed care:

• Several case Fragment: blocks in ReactFiberCommitWork had a // Fallthrough that was only reachable with the flag off. Where a preceding case falls into Fragment (the ViewTransitionComponent cases), I verified the resulting behavior is unchanged for every remaining flag combination.


• 
  commitAttachRef in ReactFiberCommitEffects becomes a plain case Fragment: { ... break; } instead of a conditional fallthrough into default.


• The React.Fragment invalid-prop warning no longer has two variants; it always mentions key, ref, and children.

The three related flags — enableFragmentRefsScrollIntoView, enableFragmentRefsInstanceHandles, and enableFragmentRefsTextNodes — are not on everywhere yet and are left in place.

In tests, enableFragmentRefs was stripped from 101 @gate pragmas. Combined gates such as @gate enableFragmentRefs && enableFragmentRefsTextNodes were reduced rather than removed. One test asserted the absence of a warning under the flag, so it was renamed from warns for fragments with refs to does not warn for fragments with refs.

How did you test this change?

yarn lint, yarn prettier-check, and yarn flow for dom-node, dom-browser, and fabric all pass.

Full test suite run across experimental, stable, www-modern, www-classic, and xplat, with both --variant settings, plus --persistent. The remaining failures (Fizz / Flight / FrameScheduling / ClassEquivalence) are pre-existing: I diffed the individual failing test names against the base commit and they are identical.