Implementation Status

Release history lives in the repository CHANGELOG.md. This page records the architecture boundaries enforced by the current implementation.

Framework Core

• routing.mode, src/pages/**/page.*, and adjacent page.config.ts normalize into one Application/Page/Route/Document CoreGraph for SPA and MPA.
• application.routes is an explicit SPA-only input into that same graph.
• src/apis/**/api.* supplies request Routes with filesystem-scoped middleware.
• BuildPlan drives generated .ev entries, bundler adapters, dev routing, output ownership, and deployment linking.
• BuildOutput remains in memory; dist/deployment-metadata.json is the canonical serialized deployment projection.
• Plugins can own namespaced Application, Page, Route, and Document data and attach generated entry, wrapper, middleware, HTML, alias, and external contributions.
• Built-in Node, static, and edge deployment adapters consume the linked output model.

Bundler Capabilities

Capability	Utoopack	Webpack
Client build	Supported	Supported
Server rendering build	Unsupported	Supported
RSC build	Unsupported	Supported
PPR build	Unsupported	Supported
Generated/HTML-only dev plan update	Supported	Supported
Entry/Route/server/resolution dev plan update	Restart required	Restart required

Framework preflight reads these declarations from the selected adapter and fails before bundling when a BuildPlan requires an unsupported build capability.

Open Adapter Gaps

• Utoopack build facts and entry APIs for server rendering, PPR, and RSC.
• In-process structural dev-plan updates for entries, Routes, server topology, module resolution, and bundler configuration.

Track completed work in the changelog. Keep this page aligned with adapter capability declarations and focused tests.