Studio: new field's API name doesn't follow the label before first save (permanent field_N columns) #2260

Mirror of framework#2615 (P1), found by the Studio package-create UX dogfood (framework#2609). Reproduced against the pinned console build 7782698.

What happens

"Add field" creates a field with API name field_2 / label "New field". Relabeling to Status leaves the API name field_2, and after publish the data column is field_2 forever — verified: the saved record stores "field_2": "in_progress".

Why it's a trap

Object and app identifiers do auto-suggest from the display name (Repair Ticket → repair_ticket, Repair Center → repair_center), so authors expect the same for fields and never look at the API-name input. The result is data models full of meaningless field_N columns that leak into the REST API, formulas, and exports.

Expected

Sync the API name from the label while the field is new/unsaved (exactly the object-identifier behavior), lock it after first save. If the label is CJK-only and no suggestion can be derived, keep field_N but visually flag the API-name input so the author notices.

🤖 Generated with Claude Code

https://claude.ai/code/session_01DHQc5BdGhTzPfazex3vWdt