Another thought that came up in responding to a Ladislav question on why I was creating a PR that was updating to use EE9 apis in CDI lite was that we could have a version of the spec that extends EE8 and another for EE9. That would be a more direct path to getting Quarkus to pass a CDI based TCK.

The minimal EE8 dependencies that would have to be updated in EE9 are the following 5:

[INFO] +- jakarta.enterprise:jakarta.enterprise.cdi-api:jar:3.0.0:compile
[INFO] | +- jakarta.el:jakarta.el-api:jar:4.0.0:compile
[INFO] | +- jakarta.interceptor:jakarta.interceptor-api:jar:2.0.0:compile
[INFO] | \- jakarta.inject:jakarta.inject-api:jar:2.0.0:compile
[INFO] +- jakarta.annotation:jakarta.annotation-api:jar:2.0.0:compile

Another question is whether to have explicit support for aliasing the corresponding EE8 apis in the EE9 version.