Quarkus platform BOM revert leaves unresolved extension version mismatch

The goal is to determine whether reverting quarkus.platform.version after an attempted Quarkus platform upgrade reliably realigns all Quarkus extensions with the reverted platform BOM. A failed or partial upgrade can leave extension versions from the newer release mixed with the reverted platform, but it is unclear whether the build tool regenerates a fully consistent resolution from the build configuration alone.

This is a design question for Quarkus 3.x, where the platform BOM governs extension alignment and no automatic rollback command is documented. Application code that depends on internal Quarkus or extension APIs may behave differently even if the BOM version appears correct.

Questions:

• Does reverting quarkus.platform.version force every Quarkus extension back to the versions pinned by the reverted BOM?
• Can stale dependency metadata preserve newer extension versions after the platform version is reverted and the project is rebuilt?
• What check confirms that the resolved extension set matches the reverted Quarkus platform release?