Do not throw on unknown directives
Committed by cexbrayat
fix(runtime-core): do not throw on unknown directives (#6671)
fix #6340
This commit improves the case when a directive is not found in a template.
As `resolveDirective` returns `undefined`, some code was failing with the following error:
```
TypeError: Cannot read properties of undefined (reading 'deep')
```Editor assessment
This is what a thoughtful fix commit looks like. The subject states the user-facing guarantee — no throwing on unknown directives — imperatively and within length limits; the body then explains the failure chain, resolveDirective returning undefined and code reading 'deep' off it, and quotes the exact TypeError, which is gold for anyone grepping logs later. The 'fix #6340' footer and PR reference provide linkage. Blemishes are mechanical: Windows carriage returns thread through the text, and the ordering is unusual — the footer appears before the body paragraphs, whereas the convention is body first and footer tokens last, so some parsers may misattribute the structure. As a patch-level fix it will headline nicely in release notes, error message included.