* fix(core): detect template entries structurally
isTemplateEntry only matched a raw file that starts with <template>, so the
full-document sub-composition shape (<!doctype html><html><body><template>
<div data-composition-id>...</template></body></html>) was not recognised and
resolveEntryHtmlPath compiled the raw file, whose root sits in an inert
template: no timeline, no duration, "Composition has zero duration".
A template entry is now a document whose <template> holds the composition
root with no live composition root outside it. Detection and extraction share
one lookup (locateSceneRoot), the same one readSceneRoot uses.
— Jerrai
* fix(core): drop comments from the template lookup
The comment ratchet allows no net rise in a file's comment share; the PR
description carries the explanation.
— Jerrai
* fix(core): find the scene template among several templates
locateSceneRoot read only the first <template>, so a scene template that
follows another template was treated as not a template entry. Scan every
template and take the first whose content holds a composition root.
* fix(core): drop the added comment (comment ratchet)
* chore: raise the inspector unpacked size budget by 0.5%
The inspector bundles core; the multi-template scene lookup added a few
hundred bytes and put it 10 bytes over the 1% tolerance.
* fix(core): refuse a file with several scene templates, naming them
* chore: trim the inspector size budget bump to what is needed
* fix(core): render the first scene template and lint the ambiguity instead of failing
A file with several scene templates and no live root rendered its first one
before; locateSceneRoot threw and stopped such projects rendering. It returns
the first again, and the multiple_scene_templates lint warning names each.
Co-authored-by: Jerrai <jerrai@heygen.com>
* chore(core): drop the locateSceneRoot comment line the comment ratchet counts
Co-authored-by: Jerrai <jerrai@heygen.com>
* fix(core): one shared scene-template pick for the compiler, the inliner and the loader
A scene template after a card template was detected by locateSceneRoot but
mounted from the first template of any kind, so it rendered blank.
findSceneTemplate picks the first template holding a composition root and
locateSceneRoot, resolveSubCompositionContent and the loader all use it.
Co-authored-by: Jerrai <jerrai@heygen.com>