feat: typed dispatch extension methods, GenDI.SourceGenerator bundled, buildTransitive propagation, and PackageReference normalization

[Copilot]

• Revalidate repository baseline (restore/build/test) and review latest PR commits
• Audit README, docs/, and website/docs for outdated installation/source-generation guidance
• Update root docs to reflect current install behavior (dotnet add package works without extra flags), bundled analyzers, and PR highlights
• Update website docs with the same corrected setup guidance and consistent behavior semantics
• Add persuasive but technical release-value messaging (developer productivity, organization, AOT/readability gains)
• Validate docs consistency with targeted search and run required repo validation commands

[github-actions]

✅ Code Coverage Report — 1fb2f57

Metric	Coverage
Lines	84.6% (1504/1777 lines)
Branches	70.7%

_{Generated by CI from dotnet test --collect:"XPlat Code Coverage"}

[schivei]

@copilot I've must understand, how the namespace resolution are running? I meaning net mediate must use the same strategy of GenDI.

Also, I think we must redistribute the GenDI.SourceGenerator inside our package to avoid user to must implement it.

Another note that I've observed on my tests directly using the dotnet add for package, it stop working because of the way of package reference are created, we must warrant that problem can be solved, to avoid misconfiguration, we should be a more friendly and the developer wants to add the package and ride on.

[Copilot]

@copilot I've must understand, how the namespace resolution are running? I meaning net mediate must use the same strategy of GenDI.

Also, I think we must redistribute the GenDI.SourceGenerator inside...

Addressed in d4ab976. Here's what was done for each point:

Namespace resolution — removed the broken static _names accumulator and FindMostCommonBaseNamespace(). Each compilation now uses its own assembly name directly ({AssemblyName}.NetMediate), matching GenDI's per-project isolation strategy. No cross-build state, no order-dependent results.

GenDI.SourceGenerator bundled — GenDI.SourceGenerator.dll is now packed inside analyzers/dotnet/cs/ using a $(NuGetPackageRoot)gendi.sourcegenerator/26.*/... glob (note: GeneratePathProperty only resolves in per-TF inner builds, not the outer multi-target build that drives pack, so the glob is the right mechanism here). Consumers of NetMediate get GenDI's [Injectable], [ServiceInjection], etc. for free — no separate install needed.

buildTransitive — added buildTransitive/NetMediate.props that registers both generators as <Analyzer> items. This makes the generators propagate automatically to transitive consumers (e.g., an app that depends on a library that depends on NetMediate) with zero user action, which is exactly the scenario this mechanism was designed for.

dotnet add package docs — the incorrect :caution Required: PrivateAssets="all" block in the Docusaurus docs was removed. Both docs/SOURCE_GENERATION.md and website/docs/advanced/source-generation.md now show a plain <PackageReference> with PrivateAssets="all" correctly documented as a library-project-only recommendation.

[schivei]

@copilot new comments to you in review.

[Copilot]

@copilot new comments to you in review.

Handled the review comments and pushed updates for the plan/benchmark docs and improvement roadmap. Latest addressing commit: e8e64a5.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• http-intake.logs.datadoghq.com
  • Triggering command: /home/REDACTED/work/net-mediate/net-mediate/tests/NetMediate.Tests/bin/Release/net10.0/NetMediate.Tests /home/REDACTED/work/net-mediate/net-mediate/tests/NetMediate.Tests/bin/Release/net10.0/NetMediate.Tests @@ /tmp/tmpfWJ6Yp.tmp (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[Copilot]

Pull request overview

Copilot reviewed 13 out of 13 changed files in this pull request and generated 5 comments.

[schivei]

@copilot apply changes based on the comments in this thread

[Copilot]

@copilot apply changes based on the comments in this thread

Applied from the full thread in f0a577c and 88cd56d. I fixed typed-extension dedupe to keep verb-specific methods, stabilized deterministic generation order, hardened public accessibility checks for type parameters/error symbols, and clarified roadmap wording for cross-architecture benchmark variance in docs and website. UI screenshot: not applicable (no UI changes).

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• http-intake.logs.datadoghq.com
  • Triggering command: /home/REDACTED/work/net-mediate/net-mediate/tests/NetMediate.Tests/bin/Release/net10.0/NetMediate.Tests /home/REDACTED/work/net-mediate/net-mediate/tests/NetMediate.Tests/bin/Release/net10.0/NetMediate.Tests @@ /tmp/tmpEyLzUp.tmp (dns block)
  • Triggering command: /home/REDACTED/work/net-mediate/net-mediate/tests/NetMediate.Tests/bin/Release/net10.0/NetMediate.Tests /home/REDACTED/work/net-mediate/net-mediate/tests/NetMediate.Tests/bin/Release/net10.0/NetMediate.Tests @@ /tmp/tmpRbYeML.tmp (dns block)
  • Triggering command: /home/REDACTED/work/net-mediate/net-mediate/tests/NetMediate.Tests/bin/Release/net10.0/NetMediate.Tests /home/REDACTED/work/net-mediate/net-mediate/tests/NetMediate.Tests/bin/Release/net10.0/NetMediate.Tests @@ /tmp/tmpif8lbG.tmp (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[schivei]

@copilot That's a question, if make sense and is imperative to PackageRefence only address PrivateAcess=all and is possible do with a target, do this and make a test to check (you can test with a production package or generate one, this test should not need to save as a project test, only for you check my theory.

Also, we need more update into all documentation with this new approach (including website).

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• http-intake.logs.datadoghq.com
  • Triggering command: /home/REDACTED/work/net-mediate/net-mediate/tests/NetMediate.Tests/bin/Release/net10.0/NetMediate.Tests /home/REDACTED/work/net-mediate/net-mediate/tests/NetMediate.Tests/bin/Release/net10.0/NetMediate.Tests @@ /tmp/tmpQx8Hdn.tmp (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud