Found in the 0.28.0 pre-release review (2026-09-08). Line references are as of main after #926.
Evidence has products/evidence/scripts/check-config-key-paths.sh, which keeps every configuration reference in exact parity with the schema it explains. BReg has no analogue: no products/breg/contracts/*.yaml enumerates a configuration key, and since #927 stopped committing the generated breg-configuration.json, nothing outside the generator detects a silently dropped key. Add the same gate for the registry-project, module and runtime schemas, and wire it into CI next to the Evidence one.
Found in the 0.28.0 pre-release review (2026-09-08). Line references are as of main after #926.
Evidence has
products/evidence/scripts/check-config-key-paths.sh, which keeps every configuration reference in exact parity with the schema it explains. BReg has no analogue: noproducts/breg/contracts/*.yamlenumerates a configuration key, and since #927 stopped committing the generatedbreg-configuration.json, nothing outside the generator detects a silently dropped key. Add the same gate for the registry-project, module and runtime schemas, and wire it into CI next to the Evidence one.