bindings.gen.ts and bindings.consts.ts have no CI check for staleness, so a Rust table edit that skips the regen step ships silently; the local dev loop regenerates them automatically but CI never verifies they're up to date. CI already does this for other generated files (the manual image dims and the plugin types), so it's the same pattern extended to the bindings.
bindings.gen.ts and bindings.consts.ts have no CI check for staleness, so a Rust table edit that skips the regen step ships silently; the local dev loop regenerates them automatically but CI never verifies they're up to date. CI already does this for other generated files (the manual image dims and the plugin types), so it's the same pattern extended to the bindings.