Add make check target to verify generated code is up to date

[leo-notte]

Summary

• Adds a make check target that runs ./scripts/generate.sh and fails with exit 1 if it produces a diff in the generated files (internal/api/client.gen.go, internal/api/property_names.gen.go, internal/cmd/*_flags.gen.go).
• Pre-checks the working tree first: if those generated files already have uncommitted local changes, it exits 2 with a distinct message so a dirty tree isn't misreported as generator drift.

Not a true dry run — generate.sh writes to disk, so make check will overwrite the files and rely on git diff to detect drift. A pure dry-run would require refactoring the script to write to a temp dir.

Test plan

• On a clean tree with up-to-date generated files, make check exits 0.
• After manually editing internal/api/client.gen.go, make check exits 2 with the "uncommitted local changes" message.
• After a spec change that would regenerate output, make check exits 1 with the "out of date" message.

🤖 Generated with Claude Code

Greptile Summary

Adds a check Make target that pre-checks for uncommitted local changes in generated files (exiting 2), runs generate.sh, then checks git status --porcelain to detect drift (exiting 1). The use of git status --porcelain correctly captures both staged and working-tree changes relative to HEAD, resolving the previous concern about git diff --quiet comparing against the index.

Confidence Score: 5/5

Safe to merge — only a minor UX nit in an error message remains.

The implementation is logically sound: git status --porcelain correctly detects staged, unstaged, and untracked changes relative to HEAD. The only remaining finding is a P2 wording improvement in the post-drift error message.

No files require special attention.

Important Files Changed

Filename	Overview
Makefile	Adds a check target using git status --porcelain to pre-check for dirty generated files and post-check for generator drift; logic is correct, one minor UX nit in the post-drift error message.

Prompt To Fix All With AI

This is a comment left during a code review.
Path: Makefile
Line: 83

Comment:
**Misleading post-drift message**

By the time this line is reached, `./scripts/generate.sh` has already run (line 80) and the files have already been updated on disk. Telling the user to "Run 'make generate'" is redundant and potentially confusing — they only need to commit the files that were just regenerated.

```suggestion
		(echo "Generated code is out of date. Run 'git add' and commit the regenerated files above." && git status --short -- internal/api/client.gen.go internal/api/property_names.gen.go 'internal/cmd/*_flags.gen.go' && exit 1)
```

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (4): Last reviewed commit: "Address PR review: detect staged changes..." | Re-trigger Greptile}

[leo-notte]

@greptileai review