Summary
- add the template-first
html authoring API to @effectify/loom
- introduce typed renderable composition (
View.use, View.match, boundary helpers)
- migrate
apps/loom-example-app to teach the new preferred Loom API and keep dev/test SSR behavior green
Motivation
The new Loom view direction was implemented in the package layer, but the example app and teaching path also needed to move to the same template-first API before opening a PR against dev. Tracking both the package implementation and the example-app adoption in one approved issue keeps the repository workflow satisfied and preserves one reviewable scope.
Acceptance Criteria
@effectify/loom exposes the new template-first authoring path with passing tests/typecheckapps/loom-example-app teaches the new path using imported html and View.use(...)- example app dev/test/typecheck remain green after the migration
- legacy helper deprecation is explicitly left for follow-up work
Summary
htmlauthoring API to@effectify/loomView.use,View.match, boundary helpers)apps/loom-example-appto teach the new preferred Loom API and keep dev/test SSR behavior greenMotivation
The new Loom view direction was implemented in the package layer, but the example app and teaching path also needed to move to the same template-first API before opening a PR against
dev. Tracking both the package implementation and the example-app adoption in one approved issue keeps the repository workflow satisfied and preserves one reviewable scope.Acceptance Criteria
@effectify/loomexposes the new template-first authoring path with passing tests/typecheckapps/loom-example-appteaches the new path using importedhtmlandView.use(...)