Fix repository comic generation and release readiness

[thotashashank302]

Summary

Replace pull-request mode with repository explanations and fix generation failures caused by persisted exclusion limits, GitHub anonymous rate limits, failed-row reuse, and Cloudflare structured-output handling.

Generation now uses the immutable commit displayed during inspection even if the branch moves. Both clients preserve slash-containing branch refs; inspection resolves tree-directory suffixes without changing exact refs during generation. Failed dispatches become retryable, and interrupted rows with saved analysis can resume through Trigger idempotency.

Update vulnerable runtime dependencies and native image tracing, add regression and PostgreSQL migration tests, and run tests/builds/audit in GitHub Actions. Update deployment documentation to separate local validation from hosted acceptance.

Validation

• 44 tests passed locally, including captured-commit, dispatch recovery, ref resolution, and fresh/legacy migration coverage.
• Six-workspace typecheck, lint with zero warnings, formatting, and diff checks passed.
• Next.js 16.3.3 production build and Chrome extension ZIP passed locally. The ZIP used a test HTTPS origin and is not a production release artifact.
• Production dependency audit: zero known vulnerabilities after the updates.
• GitHub CI passed every step on commit 1777c2e, including Linux build, migration tests, extension packaging, and audit. Vercel and Vercel Preview Comments also passed.
• Migration SQL ran verbatim against embedded PostgreSQL with Supabase-role and storage-catalog fixtures. Hosted Supabase and Storage API behavior remain unverified.

Remaining release gates

Keep this PR draft until hosted acceptance succeeds and an independent reviewer approves it.

• Identify/restore the current ComicCode Supabase project and verify applied migrations, RLS/grants, private Storage, and legacy records. Both ComicCode projects were reported inactive by the connector.
• Extend the Vercel connection to the current project/team, deploy the matching Trigger worker, and rebuild the extension against the final HTTPS origin. Git integration built the new preview successfully, but /api/health redirects to Vercel SSO and the connector cannot access this deployment. Trigger CLI was signed out.
• Verify public/private generation, branch movement, failed retry, Cloudflare BYOK, download, share/revoke, and deletion with real credentials. These live flows were not run.
• Require green CI and request an independent GitHub review before merging.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
comic-code	Ready	Preview	Sep 30, 2026 3:48pm UTC