The properties panel now puts required fields first, with real property names beside the friendly ones

We got lost in our own properties panel. Building a stack for a test run, we could not find where to set a DynamoDB partition key — it sat mid-list under a friendly label, looking exactly like every optional field around it. If the people who wrote the panel can lose a required field, you were losing them too. So the panel now knows what is required: every field whose absence produces a deploy-blocking error carries a Required badge and sorts to the top of its section, where you actually look first. And every field now shows its internal property key in small monospace next to the friendly label. Error messages and findings say hashKey; the panel used to say only Partition Key. Both names are now visible on the same row, so the message you read and the field you need to fix finally point at each other.

Try it: drop a DynamoDB table on the canvas and open its properties panel.

Fixes & improvements

• •The Advanced settings grouping now exists in Advanced mode too, expanded by default — it was previously one flat, undifferentiated list
• •New DynamoDB tables flag a missing partition key instead of silently pre-filling one; an unedited table still exports with a working default