Three stable boundaries
The site separates the shared UI system, the Astro integration, and the content owned by the generated website.
Keep framework-specific behavior at the edge. The content model and route helpers should remain usable by generators and other documentation surfaces.
The Astro application owns routes, content collections, metadata, and build-time search indexing. The shared UI package owns the visual language that can also be used by other generated surfaces.