v0.3.19

Product and template experience

• Added one shared account contract across the five web templates: Next.js, TanStack, SvelteKit, Astro, and Nuxt now expose guest login, account conversion, protected workspaces, profile and balance views, subscriptions, orders, credits, API keys, and support entry points against the same ZShip backend.
• Added workspace entry points for AI Playground/Studio and Image Agent. The adapters keep authentication, model discovery, streaming/chat requests, image-agent capabilities, conversations, turns, and turn-start operations on the existing backend services.
• Added consistent localized auth routes for login, registration, verification, password recovery/reset, guest conversion, and session refresh. Protected route redirects preserve the intended destination and pricing plan selection.
• Added the shared React workspace shell, account data views, mobile navigation, loading/error/empty states, theme and locale preferences, and the same account actions to the Astro and SvelteKit implementations through their native adapters.
• Added public blog discovery with search and topic filters, readable article layouts, starter guides when the remote blog is empty, and locale-preserving navigation.
• Added the latest Video Agent production workspace and editing flow in Nuxt, including projects, drafts, media, storyboard/timeline, captions, voice profiles, render/export, delivery, recovery, and version history.

Frontend and API contracts

• Frontends now use explicit BFF allowlists for workspace, AI, Image Agent, authentication, and project routes. Account cookies are required before forwarding protected requests to the shared backend.
• AI adapters expose model/config discovery and chat routes through the existing Node10 service bindings. Image Agent adapters expose capabilities, conversations, turns, and turn-start routes through the existing provider contract.
• Pricing login handoff retains locale, return path, and the selected plan without starting checkout automatically after login. One-time credit packs remain separate from recurring subscription plans.
• Account and blog views keep existing backend error responses visible, provide retry states, and avoid sending payments, emails, or support messages during client-side checks.

Backend changes and migrations

• Node1 auth/credit ledger: apply backend/node1-auth-service/migrations/0046_admin_magic_link_rate_limit.sql and 0047_credit_read_indexes.sql in order. The admin credit reads are bounded and use the new indexes.
• Provider1: apply 0040_provider_media_capabilities.sql, 0041_seed_video_production_models.sql, 0042_video_production_reference_input.sql, and 0043_correct_video_provider_contracts.sql in order.
• Node10 AI: apply 0027_video_production_pipeline.sql through 0037_video_production_voice_revisions.sql in numeric order. These add video projects, scene jobs, recovery, render attempts, selective reuse, reference assets, reconciliation, planning dispatch, delivery, verification, and voice revisions.
• The video path adds the Node12 media-egress service and the video-render service. Verify MEDIA_EGRESS, VIDEO_AGENT_WORKFLOW, VIDEO_PRODUCTION_WORKFLOW, and RENDER_JOB bindings before deployment.
• Preserve existing NODE1_AUTH, NOTIFY_SERVICE, SUPPORT_SERVICE, PROVIDER1_SERVICE, and video service bindings. Apply D1 migrations, verify schema and health, deploy owners before callers, then deploy the five frontends last.
• Keep secrets separate from plain vars and verify account-specific D1, KV, R2, service, workflow, and rate-limit resources before any production deployment.

Release state

This entry documents the committed platform update. The application workers were not redeployed as part of this data-only changelog operation. The migration inventory and owner-first deployment checks remain separate release work; verify guest login, workspace access, AI requests, Image Agent turns, and protected account routes on all five templates before promoting the corresponding workers.