Fix custom command creator POST validation (v2.3.1)

Changed CustomCommandCreatorModel.id from required `int` to `Optional[int] = None`
to allow POST requests to create new creators without specifying an ID (database
auto-generates it).

Bug: Users couldn't create custom commands with /new-cc - API returned 422 error
"Field required" for missing id field.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

CLAUDE.md

@@ -72,6 +72,7 @@ app/
 - **Models**: Pydantic models for request/response validation
 - **Database Access**: Direct Peewee ORM queries with automatic connection pooling
 - **Response Format**: Consistent JSON with proper HTTP status codes
+- **POST Requests**: Pydantic models for POST (create) endpoints should use `Optional[int] = None` for `id` fields since the database auto-generates IDs
 
 ### Environment Variables
 **Required**:

VERSION

@@ -1 +1 @@
-2.3.0
+2.3.1

app/routers_v3/custom_commands.py

@@ -20,7 +20,7 @@ router = APIRouter(
 
 # Pydantic Models for API
 class CustomCommandCreatorModel(BaseModel):
-    id: int
+    id: Optional[int] = None  # Optional for POST (auto-generated), required on response
     discord_id: int
     username: str
     display_name: Optional[str] = None