[jeremydmiller]

Package bumps

• JasperFx (JasperFx, JasperFx.Events, JasperFx.Events.SourceGenerator, JasperFx.Events.InMemory, JasperFx.SourceGenerator): 2.100.1 to 2.101.0. JasperFx.RuntimeCompiler stays at 5.1.0, which is unchanged.
  • Native AOT command line: the command line now runs from a Native AOT binary (Minimal Hosted AOT will not run jasperfx#1141). JasperFx.SourceGenerator registers commands, inputs and [InjectService] injectors through a generated [ModuleInitializer] instead of reflection.
  • Generator warning: a new JFXEVT1138 build warning fires when a pinned JasperFx.Events.SourceGenerator loses to a bundled copy and no copy reaches the compiler. This was the wolverine#5394 failure mode.
  • Windows assembly scanning: the scan now skips runtimes/native folders on Windows too, and skips satellite resource assemblies (AssemblyFinder doesn't skip runtimes/native folders on Windows: the check looks for '/runtimes' with a forward slash jasperfx#1143).
• Weasel (all eight packages): 9.49.0 to 9.50.0. Weasel.Core and Weasel.EntityFrameworkCore are now built with the generator, so db-* is available from a native binary too.

Docs

• guide/command-line.md: a "Native AOT" tip under the existing pointer to the JasperFx command line docs.
  • What it says: commands are found, parsed and created without reflection, so they're available from the published binary.
  • Generator: Wolverine is built with the generator and flows it to the application.
  • Still dev-time: codegen write and wolverine-diagnostics codegen-preview stay under dotnet run.
  • Caveat: what each command then does is subject to the same AOT rules as the rest of the app.
• guide/aot.md: a new section, "The command line in an AOT binary".
  • Coverage: what is available natively, including Wolverine's storage, capabilities, clear-handled and wolverine-diagnostics.
  • Generator requirement: every assembly that contributes commands needs the generator. Wolverine references it with PrivateAssets="none", which covers the app and the transport/extension assemblies.
  • Weasel: db-* works natively from Weasel 9.50.0.
  • Example: an explicit Main that suppresses the trimming warnings for RunJasperFxCommands.
  • Links: a "Related" link to the JasperFx command line docs.

Verified locally

• Build: wolverine.slnx builds in Release against JasperFx 2.101.0 and Weasel 9.50.0.
• Generated manifests: the compiled Wolverine, Wolverine.Http, Wolverine.Kafka and Wolverine.Bobcat.EventModel assemblies each contain the generated DiscoveredCommands manifest. That confirms the generator does flow to the extension assemblies, as the docs say.
• CoreTests: 8,060 passed. The one failure was Tracking.ignoring_traffic_for_every_session_on_a_host.without_the_rule_the_same_traffic_holds_the_session_open (it expects a 1-second session to time out under continuous traffic, and it completed).
  • It's an existing timing flake. In four alternating full net10.0 runs, this branch passed 2/2 and unmodified main failed the same test once.
  • It also passes 3/3 when run alone.

🤖 Generated with Claude Code