The fork’s 1.9 release, evaluated properly this time

A fork that was six weeks old in 2023 and has a stable release, a governance model and two years of commits in 2025.

what was checked, against the same list as last time:

  governance    a foundation, named members, a public
                technical steering committee
  compatibility our configuration applies unchanged;
                state files are interoperable in the
                direction that matters
  packaging     distribution packages, an official
                container image, and a registry for
                providers
  tooling       the two providers we use are published
                to both registries

verdict: a genuine option. still not migrating, because
there is no problem to solve.

Re-running the same checklist two years later is what makes the answer meaningful — the 2023 verdict was “too new” and repeating the evaluation is the only way to know whether that stopped being true. Not migrating for lack of a reason is a defensible position and is different from not migrating out of inertia, and writing down which one it is is the whole value of the exercise.