Repository navigation
Summary
Production build for published sites, pre-rendered pages, and generation with each user's own RodiumAi token.
Changes
- Publish (#139):
- esbuild production bundle and one minified stylesheet;
- every route pre-rendered, with per-page SEO,
sitemap.xml,robots.txtand a real404.html; - published sites stay static: forms, newsletters, bookings and analytics go through the integrations catalog with the user's own ids.
- Generation (#139):
- complete outputs, with automatic continuation of cut answers;
<forge-edit>SEARCH/REPLACE for existing files;- the brand charter (
DESIGN.md) is locked after the first build.
- Per-user gateway token (#140): chat and images use the user's own RodiumAi access token. The internal lane stays as a fallback and for shared projects billed to their owner.
- Sites gateway:
<page>/index.html, then404.htmlwith a 404 status, then the SPA shell for older publishes. Responses use zstd/gzip. - Faster agent turns: listing project files skips
node_modulesand build folders. Before, this cost about 2 minutes per turn on a bind-mounted project. - Fixes:
- linear scans for history blocks and image sentences (#142);
- projects still on the old
@forge/formsAI rules are upgraded; - the draft thumbnail cache is keyed per viewer.
Deployed: forge-api:94, forge-sites-gateway:10, Amplify main job 133. PR #141.