Process completed with exit code 1.

Class has high complexity. >Class has a cyclomatic complexity of 16, which exceeds the threshold of 15.

Process completed with exit code 1.

Class has high complexity. >Class has a cyclomatic complexity of 16, which exceeds the threshold of 15.

Process completed with exit code 1.

Class has high complexity. >Class has a cyclomatic complexity of 16, which exceeds the threshold of 15.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/upload-artifact@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Assigning `mixed` type to a variable may lead to unexpected behavior. >This expression has type `mixed`. >Assigning `mixed` type here. Using `mixed` can lead to runtime errors if the variable is used in a way that assumes a specific type. Help: Consider using a more specific type to avoid potential issues.

Assigning `nonnull` type to a variable may lead to unexpected behavior. >This expression has type `nonnull`. >Assigning `nonnull` type here. Using `nonnull` can lead to runtime errors if the variable is used in a way that assumes a specific type. Help: Consider using a more specific type to avoid potential issues.

Assigning `mixed` type to a variable may lead to unexpected behavior. >Assigning `mixed` type here. Using `mixed` can lead to runtime errors if the variable is used in a way that assumes a specific type. Help: Consider using a more specific type to avoid potential issues.

Assigning `mixed` type to a variable may lead to unexpected behavior. >This expression has type `mixed`. >Assigning `mixed` type here. Using `mixed` can lead to runtime errors if the variable is used in a way that assumes a specific type. Help: Consider using a more specific type to avoid potential issues.

TODO should be tagged with (@username) or (#issue). >TODO comment is untagged Help: Add a user tag or issue reference to the TODO comment, e.g. TODO(@azjezz), TODO(azjezz), TODO(#123).

Assigning `mixed` type to a variable may lead to unexpected behavior. >This expression has type `mixed`. >Assigning `mixed` type here. Using `mixed` can lead to runtime errors if the variable is used in a way that assumes a specific type. Help: Consider using a more specific type to avoid potential issues.

Assigning `nonnull` type to a variable may lead to unexpected behavior. >This expression has type `nonnull`. >Assigning `nonnull` type here. Using `nonnull` can lead to runtime errors if the variable is used in a way that assumes a specific type. Help: Consider using a more specific type to avoid potential issues.

Assigning `mixed` type to a variable may lead to unexpected behavior. >Assigning `mixed` type here. Using `mixed` can lead to runtime errors if the variable is used in a way that assumes a specific type. Help: Consider using a more specific type to avoid potential issues.

Assigning `mixed` type to a variable may lead to unexpected behavior. >This expression has type `mixed`. >Assigning `mixed` type here. Using `mixed` can lead to runtime errors if the variable is used in a way that assumes a specific type. Help: Consider using a more specific type to avoid potential issues.

TODO should be tagged with (@username) or (#issue). >TODO comment is untagged Help: Add a user tag or issue reference to the TODO comment, e.g. TODO(@azjezz), TODO(azjezz), TODO(#123).

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/download-artifact@v4, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Assigning `mixed` type to a variable may lead to unexpected behavior. >This expression has type `mixed`. >Assigning `mixed` type here. Using `mixed` can lead to runtime errors if the variable is used in a way that assumes a specific type. Help: Consider using a more specific type to avoid potential issues.

Assigning `nonnull` type to a variable may lead to unexpected behavior. >This expression has type `nonnull`. >Assigning `nonnull` type here. Using `nonnull` can lead to runtime errors if the variable is used in a way that assumes a specific type. Help: Consider using a more specific type to avoid potential issues.

Assigning `mixed` type to a variable may lead to unexpected behavior. >Assigning `mixed` type here. Using `mixed` can lead to runtime errors if the variable is used in a way that assumes a specific type. Help: Consider using a more specific type to avoid potential issues.

Assigning `mixed` type to a variable may lead to unexpected behavior. >This expression has type `mixed`. >Assigning `mixed` type here. Using `mixed` can lead to runtime errors if the variable is used in a way that assumes a specific type. Help: Consider using a more specific type to avoid potential issues.

TODO should be tagged with (@username) or (#issue). >TODO comment is untagged Help: Add a user tag or issue reference to the TODO comment, e.g. TODO(@azjezz), TODO(azjezz), TODO(#123).

Property `$magicSpecifications` is never used. >Property `$magicSpecifications` is declared here. This property is declared but never read or written within the class. Help: Consider prefixing the property with an underscore (`$_`) to indicate that it is intentionally unused, or remove it if it is not needed.

Property `$magicSpecifications` is never used. >Property `$magicSpecifications` is declared here. This property is declared but never read or written within the class. Help: Consider prefixing the property with an underscore (`$_`) to indicate that it is intentionally unused, or remove it if it is not needed.