Release v4.240.4

Added

• The Acme Commerce sample frames five features with templates of the Cratis.Blueprint.Default blueprint, written template blueprint Cratis.Blueprint.Default <Template> version "^1": Catalog Publication (ListScreen, which also hosts the feature toolbar), Pricing (BoardScreen) and Reporting (DashboardScreen), and Purchasing PurchaseOrders (ListScreen) and Overview (DashboardScreen). The board's template header shows the template and its picker switches it; the domain's own templates (ProductGrid, SideSummary, StorefrontShell) stay, so both flavours are on the boards.
• The Acme walkthrough has a section, "Blueprint templates at the feature level", with the template of each feature and why the sample uses the foundation blueprint rather than a domain blueprint (crm, approvals, inventory): a domain blueprint's screens draw empty regions on a live Stage.

Fixed

• A module's or feature's template assignment is kept when a folder is merged, wherever its file sorts; before, only the assignment in the first file of the module or feature survived. The same reference written in two files counts once.