This page collects current user-visible boundaries that affect adoption, authoring, MCP, export, or shipping. A limitation stays here until current code and runtime verification show it is resolved.
Account-menu Settings reports Not implemented yet.
Font Weights exists as a compatibility file but is not in the default scaffold, lacks the normal Props path, and has no dedicated add/update MCP family.
Image collections below images/ have no complete dedicated production MCP mutation family.
Video tokens can be registered, but no native canvas Video node renders them.
Mockups have no runtime Preview or generated React output.
General/unrecognized files preserve raw rows but have no specialized renderer or content-authoring family.
Legacy CMS Model/Data files load old projects but are hidden from current creation; use typed Content for new work.
Preview currently treats conditions within one logic branch as all-AND while generated logic honors stored OR; use separate branches when agreement matters.
True anchored node.data.popup and listener expressions are editor-only.
Authentication actions can be authored/Previewed, but Component export emits a TODO rather than a complete client auth implementation.
The public backend boilerplate's SQL action executor is not production-ready.
Complete exclusion of Users/password hashes from frontend export remains unfinished; use only fake/editor data.
Some rich Document block presentation controls lack full MCP coverage, and complete Document/Document Page output still needs runtime verification.
Separate per-screen timeline mode is stored, but exported element animation targets are not scoped to the matching container-query breakpoint.
Shader parameters can animate in editor/Preview, while current generated shader output is static.
A Code Component's own timeline has no UI Animate panel and is MCP-only; a parent visual file can animate its instance.
One screenshot/measurement/computed-style read does not prove every responsive/runtime state and can be stale if Preview has not refreshed.
The packaged desktop app must run for the production endpoint and host-assisted operations.
The endpoint has no separate current auth token; do not expose it beyond trusted local clients.
App-selected and MCP-selected projects are independent; every session must select explicitly.
UI tabs/history/expansion/zoom/panel layout are not MCP project content.
Generic run-operation currently executes Component-target operations; other declared targets return unsupported.
Unknown top-level fields can be warned and ignored while recognized fields apply; handler failure does not guarantee rollback.
Activity marks are bounded volatile review aids, not an audit log.
Diagnostics are lossy; an empty result does not prove a consumer build.
Production MCP does not expose the complete project sync/history UI, Git export push, or whole-project hosted Website publish action.
Local export writes every configured local target and can partially succeed across targets.
Export replaces generated content and does not merge arbitrary hand edits.
Stale destination files from renamed/deleted project files may require separate reviewed cleanup.
Current Git target reads can expose the configured token; request redacted output.
The stored Git branch label is not passed through the current clone/push implementation.
Existing public boilerplates have different readiness; website/npm starters require dependency/setup review and backend is not production-ready.
Publishing/deployment is external and cannot be rolled back with project file Undo.
The rewritten pages are source-verified drafts. Procedural claims remain blocked from website synchronization until they are exercised in current runtime environments, screenshots are captured where useful, and the maintainer approves the Markdown.