ci: add generated code staleness check

[bdougie]

Summary

• Found this while working on feat: add project context to sessions #96, CI doesn't generate a new build.
• Adds a check-generate CI job that runs go generate for ent schemas and diffs the output against committed files
• Catches stale codegen early in the pipeline instead of surfacing as a runtime panic in smoke tests
• New CheckGenerate Dagger function copies ent dir, regenerates, and diffs to detect drift

Test plan

• Verify check-generate job passes on a clean branch
• Verify it fails when ent schema is modified without running make generate

---

Continue Tasks: ✅ 3 no changes — View all

[continue]

No docs update needed. This PR adds an internal CI check that verifies generated code (ent schemas) stays in sync with committed files. It's a developer workflow improvement that:

• Adds a check-generate CI job to catch stale codegen
• Adds a CheckGenerate Dagger function for the check

This doesn't change any user-facing behavior, configuration options, or CLI commands. Contributors who need to run go generate already know the workflow from the AGENTS.md file in the repo.

PR #97 was merged: ci: add generated code staleness check
PR URL: #97
Merged by: bdougie