This turns test 0.9's finding into a real fix: the sails that come out of our pipeline broken (fewer than 3 stripes) can be automatically re-run through a backup detector and mostly recovered. It cuts the broken-scan rate from about 7.3% down to roughly 3% if we score it honestly (real stripes, not just a count). The catch: don't gate success on stripe COUNT alone, since 6 of the 20 count-based rescues were actually still wrong — gate on the rules-verified truth.
| Measure | Value |
|---|---|
| Flagged photos (fewer than 3 stripes after rules) | 24 |
| "Rescued" by raw count (≥3 lines after escalation) | 20 of 24 |
| Genuinely rescued (≥3 lines that are actually real) | 14 of 24 |
| Real stripes added across all 24 photos | 24 |
| Junk stripes added across all 24 photos | 16 |
Test 0.9 found that 24 of 332 photos (7.3%) end up with fewer than 3 stripes after our rules run. This test wires up the fix: automatically send exactly those 24 photos to solo SAM3, filtered by our sail rules, and checks whether that actually rescues them — not just hits a stripe-count target, but recovers REAL stripes.
Source: the 24 frozen-332 photos flagged by test 0.9. Offline measurement harness, no production wiring yet.