agentos-content

To update Next.js lesson content and keep Supabase database blocks in sync, author a single Python source-of-truth file. This generates both the TypeScript mock for SSR fallback and the matching Supabase rows, preventing production content drift.

A Python source-of-truth workflow for shipping content updates means authoring lesson and bonus data once in Python. It automatically generates the TS mock and Supabase DB blocks from the same source to ensure the client-rendered experience matches the SSR fallback.

To safely patch Supabase production content during a Next.js deploy, apply updates to the database table via the Thrall pipeline. This ensures the staged tarball and PM2 restart deliver the exact intended content without diverging layers.

Yes, visual verification is mandatory after deploying Next.js standalone content updates. You must visually confirm the updated page on mobile to ensure the production server restart successfully delivered the intended lesson or bonus content.

Yes, you can use this content pipeline to change block types and add new bonuses to lessons. The workflow supports rewriting lesson structure and inserting new text bonuses by updating the Python source file and applying it to both layers.

The limitation of this source-of-truth content pipeline is strict scope: it only handles lesson and bonus content updates. Authentication, payments, backend logic, and infrastructure changes must be handled via separate workflows outside this Skill.