This was triggered by #16535 (comment)

Heads up for @UnexpectedMaker as well: no action required on your part after all.

It looks like "id" is not used by other ports, either. Can we also remove support from build-board.sh, so that it can't creep back in?

OK, I've now done that.

But note that you can still define "id", it'll just be overwritten (similar to "port" and "build" entries which are always populated/overwritten with defaults).

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.58%. Comparing base (0a9cc90) to head (d533c90).
Report is 2 commits behind head on master.

@@           Coverage Diff           @@
##           master   #16584   +/-   ##
=======================================
  Coverage   98.58%   98.58%           
=======================================
  Files         167      167           
  Lines       21596    21596           
=======================================
  Hits        21291    21291           
  Misses        305      305           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Code size report:

   bare-arm:    +0 +0.000% 
minimal x86:    +0 +0.000% 
   unix x64:    +0 +0.000% standard
      stm32:    +0 +0.000% PYBV10
     mimxrt:    +0 +0.000% TEENSY40
        rp2:    +0 +0.000% RPI_PICO_W
       samd:    +0 +0.000% ADAFRUIT_ITSYBITSY_M4_EXPRESS
  qemu rv32:    +0 +0.000% VIRT_RV32

Tangentially related to this; A long time ago I looked at using json-schema to enforce the build.json format...is that something that would be useful?

(Additional checks - size of images, valid urls etc - have already begun to be integrated into mpbuild too.)

Tangentially related to this; A long time ago I looked at using json-schema to enforce the build.json format...is that something that would be useful?

If a check can be added to the CI here with minimal overhead and maintenance effort, then yes that could be good to have.