Constant SOLVE_JSON_EFFECT_NAMES_V1 

pub const SOLVE_JSON_EFFECT_NAMES_V1: &[&str];

Every member name effects accepts on the v1 wire, in declaration order.

One list, because there are two readers: validate_effects rejects anything outside it, and the MCP solve tool publishes an inputSchema with additionalProperties: false over the same vocabulary. Those drifted apart once already — wind_shear_model reached the JSON wire in 0.36.0 and never reached the MCP schema, so an MCP caller could not ask for shear that the bridge underneath was perfectly willing to apply. mcp_effect_schema_matches_the_wire in src/mcp_command.rs pins them together.