Integration coverage for the convention features

[ipjohnson]

Thirty-five integration tests for convention registration, compiled by the analyzer through MSBuild rather than driven in memory — plus three defects they surfaced.

The generator unit tests cannot show that the analyzer loads from an ordinary ProjectReference, that both analyzer packages contribute to one partial module without colliding, or — for InAssemblyOf — that a genuine compile-time assembly reference is what gets scanned.

Three defects, none reachable from the unit tests

A decorator file declared a record module a class, and so did an interceptor file. Four writers contribute to a module's partial. Two carried their own copy of the record rewrite and two did not, so a compilation with a record module and a [Decorator] failed with CS0261 — and separately with an [Intercept]. Each missing copy only breaks a compilation that has both a record module and whatever makes that writer emit, which is why finding two instances took two separate discoveries. Now EntryModelUtil.ApplyRecordDeclaration, called by all four, so the next writer cannot get it wrong. That one-line public API addition is the whole API snapshot diff.

A metadata scan re-registered a package's own services. MetadataCandidateUtility checked only that a type was a constructible public class, where the syntax path also excludes types carrying a service attribute. An assembly whose types carry those attributes has its own module and registers them itself, so scanning it as well registers everything twice, possibly under a different lifetime — and composing that module is what the developer should be doing instead. [Decorator] is excluded for the same reason it is in the compilation being built.

What is covered

Features — AsSelf · AsSelfWithInterfaces including the System.* exclusion · AlsoAsSelf · WithAttribute · WithName · RegisterAll() selecting a type that implements nothing · AsMatchingInterface · As<T> · WithKey · Using(Try) · a type filling two roles with a lifetime each · one convention registering every closing · an open generic decorator over every convention-registered handler · InAssemblyOf against a real referenced assembly.

Combinations — a convention-registered service that is also intercepted · two decorators nesting by Order · a keyed registration decorated in place · records, nested types and primary constructors as candidates · an OnlyRealm module · module composition carrying its conventions · environment conditions on candidates in both environments · registrations not leaking between modules.

Corners — module-level [Decorate] · two modules scanning one interface, composed together · namespace filters reaching nested namespaces, the exact form refusing to, and the negative form · an open generic resolved at two closings · scoped actually scoping · disposal with the provider · an internal implementation as a candidate, which it is in this compilation and is not across an assembly boundary · a decorator resolving its own convention-registered dependencies · a filtered metadata scan reshaped with AsSelf.

The referenced-assembly tests

SecondarySutProject gains three policy types and no attributes. It does not reference the conventions analyzer, so they are inert until something scans them — which is what a third-party package looks like. One is internal, pinning the visibility difference.

Verification

• dotnet build -c Release --no-incremental — 0 warnings
• ./scripts/coverage.sh 85 — 633 tests pass, 87.5% coverage
• ./scripts/verify-packages.sh — clean

🤖 Generated with Claude Code

https://claude.ai/code/session_01C56x6Vv6HJ6ArfqwKsuSb9