Current state on master is that all tests that can run without a container (EE or servlet) are running and passing.
Most modules are re-enabled save for servlet implementations (since those implement javax based interfaces which don't have their jakarta counterparts yet) and one JSF example (pastecode).

CI for Weld 3 is swapped to correct branch and passing and for Weld 4 we have two separate views:

• Weld 4 CI
  • Most jobs are now disabled since we still need working EE server to execute tests
  • I'm also working on the log-mgs checking job so that it now checks log messages between Weld 3 and 4 so we avoid using the same msg codes for different errors.
  • Weld 4 Release
  • This view is for release related jobs, as of now it is just a copy of Weld 3 state and will require changes as, again, many tests won't pass and the job is designed to also work with WFLY patch which we cannot ship right now.
  • I will adjust this as needed once I kick off Alpha2 release.

About GF - I've been told they will let us know once there is a buildable version of GF that operates on EE 9.
At that point I plan to get nightly builds of GF and start TCK testing PRs and in CI. We still won't be able to execute all our tests (core/tests-arquillian for instance) as they are built for WFLY and I don't think it is worth the effort to re-do that but I am open to discussions.
And recently I spotted an email on their mailing list about gradual swapping to EE 9 using shading which would speed up things.