Fix JSDoc @param qualified name error: produce TS2749 instead of TS2503

[Copilot]

In JS files, JSDoc type references using qualified names (e.g. @param {map.foo}) where the left side is a value produced TS2503 "Cannot find namespace 'map'" instead of the more accurate TS2749 "'map.foo' refers to a value, but is being used as a type here. Did you mean 'typeof map.foo'?"

export const map = /** @type {const} */ ({
    foo: 'foo',
    bar: 'bar',
});

/**
 * @param {map.foo} foo  // tsgo: TS2503, tsc: TS2749
 */
export function buzz(foo) {}

Changes

• resolveEntityName: Compute namespaceMeaning = Namespace | (isInJSFile ? meaning & Value : 0) matching TypeScript's behavior, and pass it to resolveQualifiedName
• resolveQualifiedName: Two-step left-side resolution — first try Namespace-only silently, then fall back to namespaceMeaning (including Value for JS files). If both fail, re-resolve with Namespace to emit the original error
• getTypeFromTypeReference: For JSDoc qualified type references, add two-pass resolution (first Type with ignoreErrors, then Type|Value) to enable the canSuggestTypeof error path in resolveQualifiedName
• isJSDocTypeReference / hasQualifiedTypeName: Helper methods to scope the two-pass to only qualified names, avoiding interference with simple identifier resolution (which lacks getTypeFromJSDocValueReference support)

Baseline improvements

~20 existing tests improved from unhelpful TS2503 "Cannot find namespace" to accurate TS2749/TS2694 errors. One test (typeLookupInIIFE) now matches tsc exactly (diff file removed). One test (typeFromPropertyAssignment5) now produces no errors, matching tsc.

[DanielRosenwasser]

@copilot maybe there is a misunderstanding. We do not want to go back to understanding obj.foo in type position as typeof obj.foo. But we do want to issue the error message that TypeScript 6 reports;

'obj.foo' refers to a value, but is being used as a type here. Did you mean 'typeof obj.foo'?

[DanielRosenwasser]

Do we ever actually parse as a property access? Seems like an unnecessary check.

[Copilot]

You're right — JSDoc TypeReference nodes always have a TypeName that's either an Identifier or QualifiedName, never a PropertyAccessExpression. Removed in 40a196a.

[Copilot]

@copilot maybe there is a misunderstanding. We do not want to go back to understanding obj.foo in type position as typeof obj.foo. But we do want to issue the error message that TypeScript 6 repor...

Understood — this PR only changes the error message from TS2503 to TS2749. It does not resolve obj.foo as typeof obj.foo in type position. The parameter type remains error (shown as map.foo in baselines), not the resolved value type.