Place OCO stop brackets for the catalog's obfuscation options

When an account type opts in, legs are placed as an OCO pair via
order/placeoco - the usual limit plus a stop: the first cycle day's stop
keeps the day's net floor at -$1,000, min-day trades stop at 2x their
target, and the day after any red day rides stopless to make it back. A
stop-out books the day: eligibility refuses the account once realized
P&L falls short of the legs fired (or is simply negative on an opted-in
account, which survives restarts). If placeoco is rejected the leg falls
back to the classic lone limit with a loud log rather than leave a
position without an exit.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

lib/firm-catalog.ts

@@ -163,6 +163,9 @@ function validatePayload(raw: unknown): FirmCatalogPayload {
                 combineCmeHolidays: type.combineCmeHolidays === true,
                 // Lenient: a master from before the min-legs field means "no minimum".
                 minLegs: typeof type.minLegs === 'number' ? type.minLegs : 0,
+                // Lenient: the obfuscation stops are opt-in, so absent means off.
+                firstDayStop: type.firstDayStop === true,
+                minDayStop: type.minDayStop === true,
             } as unknown as CatalogAccountType;
         });