Broken frontmatter errors now tell you what will actually happen to that component at load time.
What's wrong with this entry?
When a component's YAML frontmatter fails to parse, the validator tells you the runtime consequence for that specific component type rather than a generic parse error.
- A project agent does not load at all and is treated as a co-located reference document.
- A plugin agent loads with its name taken from the filename and every other field dropped.
- Other component types load with empty metadata.
- A frontmatter block that parses to null is now accepted as an empty mapping instead of reported as a type error.
At runtime this agent loads with its name taken from the filename and every other frontmatter field silently dropped.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.