master red: specs/analog/sar_adc.t27 adds a second type named Range (types ratchet 107 -> 108) #10887

Master is red on Corpus ratchet (expected-failure ledger) since #10854 (57aa3bc):

ledger 107 name(s), observed 108
  + Range  NEW conflict

specs/analog/sar_adc.t27 declares pub struct Range { lo: f64, hi: f64 }. specs/lsp/schema.t27 already uses a type named Range, so a second definition gives the name no computable domain (#2774). Every PR built on master inherits the red check, #10862 included.

Boundary

• Rename the struct in specs/analog/sar_adc.t27 only (5 uses, all in that file; no other spec imports the name) to SarErrRange.
• Re-save .trinity/seals/analog_AnalogSarAdc.json with master's t27c on the Railway lab.
• Not in scope: blessing Range into the type-conflict ledger (that hides the next conflict), or touching specs/lsp/schema.t27.

Scenarios

1. Today: tri types ratchet on master reports observed 108 against a ledger of 107, and fails.
2. After the fix: it reports 107 against 107, with no NEW conflict.

Requirements

• The spec's tests still pass with the new name.
• t27c seal --verify specs/analog/sar_adc.t27 reports MATCH.

Criteria

• Corpus ratchet (expected-failure ledger) is green on the PR, or red only for reasons master also has.
• No other spec or ledger changes.

Requirements

FR-001: The spec specs/analog/sar_adc.t27 MUST pass its tests after renaming the struct Range to SarErrRange.
FR-002: The command t27c seal --verify specs/analog/sar_adc.t27 MUST report MATCH.

Success Criteria

• tri types ratchet exits 0 and reports observed 107 against ledger 107 with no NEW conflict
• t27c seal --verify specs/analog/sar_adc.t27 exits 0 and prints MATCH
• The file .trinity/seals/analog_AnalogSarAdc.json is updated and matches the rebuilt seal
• No other spec or ledger files are modified