`tuple[*Ts]` subtype with extra type parameter not gradually assignable to itself

This demonstrates the issue:

from typing import Any

class Array[DataT, *ShapeTs](tuple[*ShapeTs]): ...

type Float2D = Array[float, *tuple[int, int]]  # or Array[float, int, int]
type FloatND = Array[float, *tuple[Any, ...]]

def from_2d(a: Float2D) -> FloatND:
    return a  # mypy: ✅, pyright: ✅

def into_2d(a: FloatND) -> Float2D:
    return a  # mypy: ❌, pyright: ✅

https://mypy-play.net/?mypy=latest&python=3.13&flags=strict&gist=1b95c702df6de35fa3f61aa7b5dfef16

from typing import Any

class Array[*ShapeTs](tuple[*ShapeTs]): ...

type Float2D = Array[*tuple[int, int]]  # or Array[int, int]
type FloatND = Array[*tuple[Any, ...]]

def from_2d(a: Float2D) -> FloatND:
    return a  # mypy: ✅, pyright: ✅

def into_2d(a: FloatND) -> Float2D:
    return a  # mypy: ✅, pyright: ✅

from typing import Any

class Array[float, *ShapeTs]: ...

type Float2D = Array[float, *tuple[int, int]]  # or Array[float, int, int]
type FloatND = Array[float, *tuple[Any, ...]]

def from_2d(a: Float2D) -> FloatND:
    return a  # mypy: ✅, pyright: ✅

def into_2d(a: FloatND) -> Float2D:
    return a  # mypy: ✅, pyright: ✅

Potentially related issues:

• #18665
• #19106
• #19109
• #19110
• #19860
• #19858

Start by running the two Python reproductions in the linked mypy-play examples with mypy 3.13 strict settings, comparing the from_2d and into_2d assignments and the variants without DataT or the tuple base class. Review related issues #18665, #19106, #19109, #19110, #19860, and #19858; done means the problematic assignment is handled consistently without breaking the cases that already pass.