📝 docs: the architecture page describes the SDK as it is, and the wiki reads in order The Architecture Overview is rewritten for the two-target SDK — the layers, both pipelines, what a build actually writes, Server Actions on the wire, routing through the context, the real commands — with every example true to the tree (the static/logic split, the pages/ folder, the manifest, the [Parameter] attribute and the page/component templates never existed in this form). The sidebar and the Home navigation put Architecture before the write-once feature pages so a linear reader meets the map first, and point at the repository's docs/ index. Six live mentions of the dissolved eQuantic.UI.Core, the removed Tailwind package, the EnableDefaultCss option that never existed and the word the project does not use for a component are corrected; the Image page's diagram names where the optimizer state really lives and says that no component reads it yet. English and Portuguese in the same commit.
📝 docs: ExternalTypeResolution speaks pt-BR
docs: a hovered link arrives warm, and where a link leaves the reader ServerIntegration — the navigation payload does not draw, and pointing at a link warms both halves of the navigation it suggests (172ms → 28ms, no request on the click). Names the two things that were quietly false: nothing ever marked a link for the prefetch seam, and the warmed answer was stored under one key and looked up with another. Components — Link.KeepsPosition, and why chrome with its own scrolling never needed it.
docs: present the product as a single, settled design The wiki now describes what eQuantic.UI is — never what it used to be. Removed every legacy banner, migration log, slice label, internal date, baseline progression and discarded-decision story across 18 pages; changelog pages fold into their product pages and remain as pointers; the roadmap lists only what is ahead. Facts were verified against the source tree while rewriting (golden count, Vulkan backend, theme bridge, Tailwind property names).
📝 docs(wiki): add External Type Resolution documentation Add comprehensive guide for resolving external types in component compilation. Features documented: - SemanticModelProvider with project compilation support - ProjectCompilationHelper for loading full project context - ComponentCompiler.SetProjectCompilation() API - Before/after examples with User model - Architecture diagrams and usage examples - 5 new tests validating external type resolution