Greptile Summary

This PR fixes a vague server error (#8785) that occurred when null was explicitly supplied for the name parameter on any CreateUser endpoint. The fix replaces new Text(128) with new Nullable(new Text(128)) and changes the default value from '' to null across all eight hashed-password create-user routes, making name consistent with the pattern already used for email and phone.

Key observations:

• The action handlers for all affected endpoints already declare ?string $name in their signatures, so no callback signature changes were needed.
• The shared createUser helper (line 78) normalizes the value immediately with $name = $name ?? '';, so downstream database writes always receive a string — null propagation ends at the controller boundary.
• The PR description lists 7 endpoints but the diff correctly includes 8 (the scrypt-modified route is also updated), which is the right behavior.
• No API spec or example docs updates were included; if this project enforces keeping specs in sync with parameter changes, those may need to be updated separately.

Confidence Score: 5/5

• Safe to merge — the change is minimal, consistent with existing nullable-param patterns, and has no risk of regression given the null-coalescing guard in createUser.
• All P2 or lower. The fix is correct: validators now accept null, action handlers already accept ?string, and the helper normalizes null to empty string before any storage operation. No logic errors or breaking changes identified.
• No files require special attention.

Important Files Changed

_{Reviews (2): Last reviewed commit: "fix: add nullable validator to user name..." | Re-trigger Greptile}