[vincemolnar]

Since release 2026-09, some models that validated without issues get spurious warnings, and an unresolved proxy can end up in the model.

Problems fixed

1. A metadata value naming an element that is found only through a second import gets the warning "Bound features should have conforming types":

package P {
	private import VerificationCases::*;
	private import VerificationMethodKind::*;
	verification def MassTest;
	verification massTests : MassTest {
		@VerificationMethod { kind = test; }
	}
}

After transformAll(…, true), the model also contains an unresolved proxy (an AcceptActionUsage object) owned by the implied binding connector, which SysML2XMI -g writes out. The examples in sysml/src/examples/Metadata Examples get 10 such warnings.

2. After EcoreUtil.resolveAll, a feature redefined in a type whose supertype comes from semantic metadata is inherited both redefined and not redefined ("Duplicate of inherited member name …"), for example 70 times in sysml/src/examples/Arrowhead Framework Example.

3. (Also before 2026-09.) In kerml/src/examples/Association Examples/ProductSelection_OwnedEnds.kerml, after transformAll(…, true), an implied Subsetting owns an unresolved proxy.

Cause

A name lookup nested in the resolution of another reference can fail because the scope excludes the elements whose resolution is in progress. LazyLinkingResource then records the reference as unresolvable until the next change to the resource. Until #815/#821 and #818, the result parameters and default multiplicities created during name resolution changed the resource and so discarded these records. Now the records persist, and values computed and cached in the meantime (an implicit binding connector, a redefinition closure) keep the unresolved proxy.

Changes

• KerMLLazyLinkingResource: a failure of a lookup nested in the resolution of another reference stays recorded only until that resolution ends.
• FeatureAdapter.getAllRedefinedFeatures: a result that contains an unresolved proxy is not cached.
• ConnectorUtil.addConnectorEndTo, TypeUtil.insertImplicitSpecializations, FeatureUtil.insertImplicitTypeFeaturings: an unresolved proxy is not added as an owned related element.

Tests

NestedResolutionTest covers problems 1 and 2; both tests fail without these changes. The full build with all tests passes.

[seidewitz]

@vincemolnar
I have:

1. Revised the version on this branch to 0.63.1, so that it can be published in release 2026-09.1. The version will be restored to 0.64.0 before merging it into master.
2. Split your one commit into three (with no changes in the code).
3. Tested performance using SysMLInteractiveProfiler (no problems).

Let me know if you concur.

[vincemolnar]

@seidewitz I concur, thanks! I have also updated the PR description to make it self-contained. Let me know if you want it restored.

[seidewitz]

Further testing has shown that the original general solution proposed in this PR results in unacceptable performance when there are links that cannot be resolved, not just temporarily, but permanently during the processing of a model. While work continues on this general solution, a more specific solution is proposed in PR #825, which is adequate for a release update to eliminate user-visible symptoms.