fix(api): accept coin_flair_mint when creating a user

[rickyrombo]

The gap

update_user_request_body has carried coin_flair_mint since 0175. The create body never did.

Nothing about the field explains the difference. The column comment describes it as:

the coin which the user has selected as their preferred flair. NULL for auto, empty string for none.

That's a display preference — the same shape as spl_usdc_payout_wallet, which is accepted on create.

The ordering makes oversight the likelier reading than intent:

Migration	Field	In create body?
0141	profile_type	yes
0175	coin_flair_mint	no
0200	spl_usdc_payout_wallet	yes

The one in the middle is the only one missing.

Result

Create and update now differ by exactly the fields that should differ:

create-only : user_id, wallet
update-only : artist_pick_track_id, is_deactivated

Both update-only fields have reasons independent of any schema:

• artist_pick_track_id references a track the account cannot own at signup. Across 292,111 users never modified after creation, it appears zero times.
• is_deactivated — creating an already-deactivated account is meaningless.

Verification

Parsed the modified document with js-yaml:

YAML parses OK
create has coin_flair_mint: true
create fields: 21   update fields: 21
update-only: is_deactivated, artist_pick_track_id

Three lines, response schemas untouched.

Context

Found while auditing the indexer, which was dropping four fields the create body already accepted — profile_type, allow_ai_attribution, spl_usdc_payout_wallet, playlist_library. Fixed in OpenAudio/go-openaudio#466, which also adds a test pinning the indexer's create and update column sets together. This PR closes the same gap one layer up so all three layers — API contract, SDK schema, indexer — agree.

The SDK's Zod CreateUserSchema is a separate hand-written contract that's also missing coin_flair_mint (and profile_type); worth a follow-up there.

🤖 Generated with Claude Code

[rickyrombo]

Follow-up in ea4ade4: the swagger doc alone wasn't enough. The handler parses into CreateUserRequest and rebuilds the entity-manager metadata by re-marshaling that struct, so an unknown coin_flair_mint field was silently dropped at parse time and never reached the transaction. Added the field to the struct so create actually passes it through; UpdateUserRequest already had it.