Release v4.66.0

A template reference to a blueprint that is known only by its manifest - a package approved for a render, whose bundle the engine does not load - could not be diagnosed: the resolver looked for the template bodies, found none, and so every reference to such a blueprint reported UnknownTemplate (or, for a caller that skipped the check, silently fell back to a screen with no template).

Added

• Four cases in the shared template-applicability-fixtures.json (a manifest-only blueprint resolves a screen template, a dialog template and a layout it lists, and diagnoses one it does not), asserted by both engines.

Changed

• resolveTemplateReference (TypeScript) and TemplateReferenceResolver.Resolve (C#) answer from the names the blueprint's manifest lists (screenTemplates, dialogTemplates, layouts) when its source carries no template bodies, with the same Resolved kind and the same Blueprint '<name>' has no template '<id>' diagnostic otherwise. A source that carries its templates is answered from them, as before.

Part of #110