# v211 GDR-8050L live iSCSI stateful SEEK bounds

Derived from known-good v206/v208/v210 behavior.

v211 fixes the lba_probe boundary behavior introduced by v210's unconditional `SEEK(10)` success.

## Behavior

- Locked/video state exposes max LBA `0x00001B4F`.
- Unlocked Xbox state exposes max LBA `0x00345B5F`.
- `SEEK(10)` now validates the requested host LBA against the current visible capacity.
- `READ(10)` / `READ(12)` also validate host LBA ranges against the current visible capacity before translating to ISO LBA.
- Boundary probe CDB `2B 00 00 20 20 00 00 00 00 00` targets host LBA `0x00202000`:
  - locked: CHECK CONDITION / ILLEGAL REQUEST / LBA out of range
  - unlocked: GOOD
  - after relock/eject keep-loaded: CHECK CONDITION again

This is still bridge-side stateful behavior. It is explicitly marked as firmware-media-window behavior in the handoff report so it can later move into the MN103S firmware-in-the-loop path.

## Start known-good keep-loaded mode

```powershell
.\gdr8050l_auth_v211_stateful_relock_keep_loaded_iscsi_start.cmd `
  .\gdr8050l_auth_v211_stateful_relock_keep_loaded_iscsi_config.json `
  "D:\vscode-workspace\xbox-dvd-tools-v2\disc_dumps\Red Faction II[TQ00501A].iso" `
  192.168.0.8 `
  3260
```

## Collect logs

```powershell
.\gdr8050l_auth_v211_dynamic_iscsi_collect_logs.ps1
```

The trace report now separates expected boundary failures from unexpected CHECK CONDITION rows:

```text
check_condition_count: total CHECK CONDITION rows
expected_boundary_check_condition_count: deliberate locked-state boundary failures
unexpected_check_condition_count: failures that still need investigation
```
