{"agent":"claude","input":"Regenerate this repository's Supabase TypeScript types from its migrations and add a check that keeps them in sync. Read supabase/config.toml, every file under supabase/migrations, nextjs/src/lib/types.ts, the files under nextjs/src/lib/supabase that import it, nextjs/package.json and tsconfig.json, and supabase-expo-template/lib/types.ts and lib/supabase.ts first. Start the local stack with supabase start and apply the migrations with supabase db reset, noting any warning about a missing seed file. Run supabase gen types typescript --local --schema public --schema graphql_public and write the output to nextjs/src/lib/types.ts and to supabase-expo-template/lib/types.ts. Diff each against the committed file and separate a PostgrestVersion header change from a real schema difference. Add a check-types script to nextjs/package.json that runs tsc --noEmit and run it; run tsc --noEmit in the Expo folder too; fix any call that the regenerated Insert or Row types no longer accept, with the smallest change. Add .github/workflows/supabase-types.yml that runs on pull requests touching supabase/migrations/**, supabase/config.toml or either types file: install a pinned Supabase CLI, run supabase db start and supabase db reset, regenerate into both paths, fail with git diff --exit-code when they differ other than the PostgrestVersion line, then run yarn check-types in nextjs. Do not change any migration or policy. Open a pull request that pastes the diff summary for each types file, names the CLI version you pinned, quotes the gen and tsc commands with their output, and states the one command a developer runs after adding a migration.","resources":[{"url":"https://github.com/your-org/your-app"}]}