As long as Kladde.UI is a project in the solution, all consumers see every change immediately. When two applications live in two repositories or teams, the project is too tight: the library becomes a package with a version number, and the question is no longer whether something compiles but what a new version promises the consumers. This lesson packs Kladde.UI, includes it in two applications and lets package validation stand guard, so that a break is noticed when packing instead of at the consumer.
Where the Kladde stands
The lesson presupposes W8.2.3: Kladde.UI as a Razor class library with the --kui-* tokens, isolated styles and building blocks such as KButton; W8 builds the library and the design system, none of that is repeated here. From W11.2 the following applies: Kladde.UI has no row in the context map, it is a tool and not a context. New are two applications that use it as a package, Kladde.Web and Kladde.Admin (a second Blazor application for administration). Keep your names and carry the steps over. The throwaway solution shrinks Kladde.UI to KButton, a stylesheet file with four tokens (finished CSS, without the Sass step from W8) and a README; that changes nothing about the procedure.