uv(parity): ADVSL multi-leg exit added to crawl scope (operator)

prod/docs/uv_cert/UV_EXIT_DOCTRINE_PARITY_PASS_20260712.md

@@ -114,3 +114,16 @@ The matrix above UNDERSTATED both mechanisms. Live-verified inventory
 - Tie order: adopt BLUE's TP_FLOOR→TP→SL→MAX_HOLD exactly.
 - Tests: per-mechanism suites, mutation-RED each branch, curve property
   tests (monotonic in lev, floor/cap clamps, poison inputs).
+
+### ADDENDUM (operator, mid-crawl): ADVSL MULTI-LEG EXIT
+AdvancedSL is not exit-or-hold — it does **multi-leg partial exits**
+(retraction legs). Evidence already in hand: trader ~:895 event fields
+`retraction_legs`, `retraction_realized_total`, `pnl_leg`,
+`pnl_realized_total`, `exit_notional`, `remaining_notional`,
+`remaining_qty`; UV brain_tpsl reserves `ExitPriority.ADVSL` (marked
+future). The parse of advanced_sl.py MUST cover the leg engine: leg
+sizing/trigger schedule, realized-PnL accounting per leg, remaining-
+position re-watch, interaction with TP/SL/MAX_HOLD on the residual leg,
+and kernel-side partial-exit support (DITAv2 exit_leg_ratios exists on
+KernelIntent — the transport is already shaped for it). UV transcription
+must carry the FULL leg lifecycle, not a scalar exit.