[ASDAlexander77]

#569 looked a qualified name up in the namespace first, then fell back to the general lookup. That lookup searched the calling function's locals and the outer namespaces too, so these compiled and used the wrong thing:

namespace ns { export function value(): int { return 42; } }
function outer(): int { return 1; }
function main() {
    const missing = 5;
    print(ns.missing);   // printed 5, now: error: Can't resolve property 'missing' of type ns
    print(ns.outer());   // printed 1, now: error: Can't resolve property 'outer' of type ns
}

• The namespace case of a property access now takes only what resolveIdentifierInNamespace finds; a miss goes on to the usual "Can't resolve property" error (partial-resolve runs keep their non-fatal path).
• import * as M makes M an empty namespace whose names are declared at the top level; the fallback was how M.add found them. Such a namespace is now marked isModuleImport, and its access looks in the root namespace, still never in locals.

Tests:

• namespace-member/missing_member.ts, namespace-member/outer_member.ts: error text and position.
• 00ns_member_shadowed.ts: a member used before its declaration, and one from a second namespace ns2 {} block.
• import-bindings/import_namespace.ts: M.ANSWER with a local ANSWER in scope.

Full Release suite: 4091/4091 passed. The first run without the import * as M handling failed only the three import-bindings-namespace tests.

🤖 Generated with Claude Code