chore: Stop tracking generated OpenAPI code

- Add /pkg/api/openapi/ to .gitignore
- Remove 61 generated files from git tracking
- Developers must run 'make generate' after cloning/pulling
- Update README with code generation requirements

This reduces PR noise and follows best practices for
managing auto-generated code.

docs: Update README with code generation requirements

- Add 'make generate' step to Initial Setup section
- Add important note about generated code not being tracked in git
- Update code generation workflow documentation
- Clarify that developers must run 'make generate' after cloning/pulling

Author: yasun1

.gitignore

@@ -46,3 +46,6 @@ secrets
 
 # Ignore vendor directory
 /vendor/
+
+# Ignore generated OpenAPI code
+/pkg/api/openapi/

README.md

@@ -200,21 +200,26 @@ Before running hyperfleet-api, ensure these prerequisites are installed. See [PR
 go install gotest.tools/gotestsum@latest
 go mod download
 
-# 2. Build the binary
+# 2. Generate OpenAPI code
+make generate
+
+# 3. Build the binary
 make binary
 
-# 3. Setup PostgreSQL database
+# 4. Setup PostgreSQL database
 make db/setup
 
-# 4. Run database migrations
+# 5. Run database migrations
 ./hyperfleet-api migrate
 
-# 5. Verify database schema
+# 6. Verify database schema
 make db/login
 psql -h localhost -U hyperfleet hyperfleet
 \dt
 ```
 
+**Note**: The `pkg/api/openapi/` directory is not tracked in git. You must run `make generate` after cloning or pulling changes to the OpenAPI specification.
+
 ### Running the Service
 
 **Local development (no authentication):**
@@ -322,6 +327,8 @@ pkg/api/openapi/api/openapi.yaml (44KB, fully resolved spec)
 - Validation tags for required fields
 - Fully resolved OpenAPI specification
 
+**Important**: Generated files in `pkg/api/openapi/` are not tracked in git. Developers must run `make generate` after cloning or pulling changes to the OpenAPI specification.
+
 ### Runtime Embedding
 
 The fully resolved OpenAPI specification is embedded at compile time using Go 1.16+ `//go:embed`: