Edge App settings appear in the order you declared them

The settings you write in screenly.yml now appear to whoever installs your app in the order you wrote them. screenly edge-app deploy works out each setting’s position from where it sits in the manifest and sends that along.

This matters because a settings form is a form. An address above a postcode, a start time above an end time, credentials grouped together: you already put them in a sensible order when you wrote them, and until now that order was not carried anywhere.

Set display_order on a setting to override the position it would get. An order you write by hand is never overwritten, and deploy sends the computed order without rewriting your manifest, so nothing appears in your working tree after a deploy.

Secrets are left out of the automatic ordering unless you give them a descriptor of their own, which keeps the password field behaving the way it does today.