Should @phpstan-sealed validate that all listed types are subtypes of the annotated type? #15193

Consider the following example:

https://phpstan.org/r/15a71033-265f-47e3-83d6-6a88f1c7d7b3

/**
 * @phpstan-sealed (X | Y | Z)
 */
interface XYZ {}

enum X implements XYZ
  { case Value; }

enum Y implements XYZ
  { case Value; }

enum Z
  { case Value; }

PHPStan accepts this even though Z does not implement XYZ.
I would expect @phpstan-sealed to describe the complete set of allowed subtypes of XYZ. Under that interpretation, every type listed in @phpstan-sealed should itself be a subtype of XYZ.

In other words, this:

/**
 * @phpstan-sealed (X | Y | Z)
 */
interface XYZ {}

would imply that PHPStan should validate:

X <: XYZ
Y <: XYZ
Z <: XYZ

and report an error for Z in the example above.

Is the current behavior intentional?
If so, what is the intended semantic meaning of the types listed in @phpstan-sealed? Are they only treated as a whitelist for inheritance/implementation checks, without requiring them to actually be subtypes of the sealed type?