[mmnavarr]

Problem

Alias resolution treats finite nested instantiations of the same generic alias as recursion, so unknown and object hidden behind them go unreported:

type Maybe<T> = T | undefined;
type Hidden = Maybe<Maybe<unknown>>; // not reported by no-unknown-type-aliases
function load(): Maybe<Maybe<unknown>> {} // not reported by no-unknown-returns
function save(value: Maybe<Maybe<object>>) {} // not reported by no-object-parameters

Type arguments were evaluated with the alias-expansion set active at the point where the parameter was used, not where the argument was written. When the outer Maybe body reaches T, the inner Maybe<unknown> argument was resolved with Maybe already marked as expanding, so resolution stopped.

Fix

Each substitution now stores the alias-expansion set from where its argument was written: the reference site for explicit arguments, and inside the alias for defaults. Evaluation picks up from that set. Genuinely recursive aliases still terminate, because an alias referenced inside its own body is still being expanded at that point.

Tests

New no-unknown-type-aliases RuleTester cases:

• Invalid: Maybe<Maybe<unknown>>, Identity<Identity<Identity<unknown>>>, Pair<string, Pair<number, unknown>>. The first fails before this change.
• Valid (terminate without a finding): Loop<T> = Loop<T>, Nested<T> = T | Nested<Nested<T>>, Tree<T> with recursive children, Maybe<Maybe<string>>.

pnpm check passes, and the skill assets are re-synced.