docs: point at the playground, which nothing linked to
docs: authoring without `new`, including your own components
The factory surface had no page of its own: the README showed it, the template
used it, and anyone asking "why does this compile without a `new`?" had nowhere
to look. Worse, the answer everyone reaches for — "that must be a framework-only
trick" — is wrong, and nothing said so.
DeclarativeSurface covers the contract (named like the type, mirrors a
constructor, no overloads, `children` last), how an app's own components join it
through the generator, the widest-constructor rule and `[UiFactory]`, EQ3101 and
EQ3102, and the one sharp edge: a factory shadows its type, but only for types
that arrive through a `using` — so your own are never shadowed, and `Gap` and
`DotBadge` exist for the framework's two that are.
Also the `dotnet clean` note for a renamed generator, because eqc reads the
generated FILES and the compiler never removes what a generator stopped writing.
📝 docs: Getting Started — três comandos para um app write-once