[mdempse1]

Two opt-in checks for libraries that have to load in tools other than Dymola, a setting that lets a library accept the built-ins of the tools it is written for, and a resolver fix those checks exposed.

MLQT.Reference.Undeclared (Error when on)

Reports a name used where nothing of that name is declared:

• variables in equations, algorithms, bindings, conditions and subscripts
• functions called, types, base classes and imports
• members after a dot (s.missing), enumeration literals included
• modification targets (Sub s(gian = 1), and Real x(fixd = true) against the predefined type's attributes)
• a non-constant of an enclosing class used from a nested one

It follows the roadmap's three-state rule. A miss is reported only when every scope searched is readable, with all bases loaded, and no unresolved import could bind the name. It also needs no unloaded library to be able to supply the name: either a plain variable, or a name the library's uses(...) rules out. Members reached through replaceable or an expandable connector are never judged.

Accepting a tool's built-ins. While the rule is on, the Static analysis section shows a Dymola and an OpenModelica checkbox, saved as AcceptedToolBuiltIns. The default, neither, reports every use and names the tool. Dymola covers its built-in functions, the Advanced/Hidden flags, Dymola_AST_* and its plot enumerations; OpenModelica covers its OpenModelica package. A tool's name counts even where an import binds part of it: import Modelica.Utilities.Strings.* brings in MSL's Strings.Advanced, and Dymola still reads Advanced.Translation.X as a flag. The CLI and the MCP style settings take the list too.

MLQT.Conformance.Grammar (Warning when on)

modelica.g4 accepts what Dymola accepts beyond the MLS 3.7 concrete syntax (Appendix A, keywords §2.3.3). This rule reports each place a class relies on one of the eight widenings:

• a leading class annotation
• a short-class prefix other than input/output
• := in a modification
• a der statement that is not der(x) := e
• a comprehension after several arguments
• an escape MLS does not define
• white space in a quoted identifier
• time or a predefined type's name used as an identifier

settings-reference.md §Strict Modelica 3.7 syntax lists them, and the places where the grammar is narrower than 3.7 (those are already syntax errors).

Complex is resolved, not predefined

TypeResolver.IsPredefined counted Complex as predefined, so every class built on it had no members: u.re resolved to nothing and the units on re/im were unseen. MLS 3.7 §4.9 does not list it; it is the operator record of Complex.mo. It now resolves like any class. Declaration ordering still treats a Complex declaration as a variable, so Format All moves nothing.

Also on this branch

• Each rule's modifiers (the tool checkboxes, the package.order "match Dymola" switch) sit directly under that rule.
• A scrollbar beside a splitter can be clicked: dividers grow their grab area into the second pane only (ResizablePanesJourney covers it).
• Settings dialog layout improvements.

Measured

• MSL 4.1.0, ModelicaTest, Buildings: neither new rule reports anything. 99% of MSL's ~200k name uses get a definite verdict, so the zero is a real result rather than silence.
• Planted errors: a test library with eight planted mistakes, four of each kind, gets all eight reported.
• A real application library (21,249 classes, Dymola accepted): no finding about a Dymola name. The rule's remaining findings there are protected members reached through a dot, and modifications naming elements that aren't there.
• Resolution corpus: all 125,158 component types resolve (181 more than before, the Complex ones); no package redeclaration changes a unit.
• Every rule on, before and after the Complex change: MSL and Buildings report the same findings, rule for rule, at the same speed.
• Cost: the undeclared-name analysis is about 2 s over Buildings, and the conformance rule about 1 ms per class.

Test plan

• CI=true dotnet build MLQT.slnx -c Release: no warnings
• build/run-all-tests.ps1 -CoreOnly: 9,546 tests pass
• build/check-coverage.ps1: gate passes
• Resolution corpus (MLQT_RESOLUTION_CORPUS)
• The Static analysis section's new checkboxes, by eye in the desktop app (covered by a bUnit test only)

🤖 Generated with Claude Code