Spun off from the conjoined EF Core multi-tenancy epic (#3465) — API-friction finding 2 from the ConjoinedMultiTenantedEfCore sample app (see the 2026-07-20 findings comment on #3465).
Fresh 6.x apps following the conjoined tenancy docs hit the GH-2876 startup requirement for WolverineFx.RuntimeCompilation blind — the startup message explains it, but the docs path should not lead a new reader into a startup failure before mentioning the package.
As of 6.22.0-alpha.1, neither docs/guide/durability/efcore/multi-tenancy.md (including the conjoined sections added by #3532) nor src/Samples/ConjoinedMultiTenantedEfCore/README.md mentions RuntimeCompilation at all (verified by grep).
Acceptance criteria
- The conjoined tenancy docs section and the sample README both state the
WolverineFx.RuntimeCompilation requirement up front, with the package-reference snippet.
Related: #3465, #3532, GH-2876.
🤖 Generated with Claude Code
Spun off from the conjoined EF Core multi-tenancy epic (#3465) — API-friction finding 2 from the
ConjoinedMultiTenantedEfCoresample app (see the 2026-07-20 findings comment on #3465).Fresh 6.x apps following the conjoined tenancy docs hit the GH-2876 startup requirement for
WolverineFx.RuntimeCompilationblind — the startup message explains it, but the docs path should not lead a new reader into a startup failure before mentioning the package.As of 6.22.0-alpha.1, neither
docs/guide/durability/efcore/multi-tenancy.md(including the conjoined sections added by #3532) norsrc/Samples/ConjoinedMultiTenantedEfCore/README.mdmentionsRuntimeCompilationat all (verified by grep).Acceptance criteria
WolverineFx.RuntimeCompilationrequirement up front, with the package-reference snippet.Related: #3465, #3532, GH-2876.
🤖 Generated with Claude Code