docs(debt): record the untested interaction with the DualSense haptics path

docs/dev/debt/libSceVideoOut.md

@@ -36,6 +36,7 @@
 
 ### Functional
 
+- [ANYPS5_PAD_IDENTIFY and haptics reports](../../../core/libs/prx/libSceVideoOut/src/PadInput.cpp) (libSceVideoOut) - the pulse uses the SDL motor rumble path only; it is not checked against the Bluetooth DualSense haptics-report path of open PR #9154, and the two have not been run together.
 - [ANYPS5_PAD_IDENTIFY on request](../../../core/libs/prx/libSceVideoOut/src/PadInput.cpp) (libSceVideoOut) - no key or overlay entry sends the pattern on demand; `always` repeats it every 30 seconds instead.
 - [ANYPS5_PAD_IDENTIFY pulse pattern](../../../core/libs/prx/libSceVideoOut/src/PadInput.cpp) (libSceVideoOut) - the 150 ms full-strength pulses 400 ms apart and the 500 ms quiet window are AnyPS5 choices: no measurement shows how a real controller's motors feel them or whether players can count the pulses.
 - [sceVideoOutOpen](../../../core/libs/prx/libSceVideoOut/src/Output.cpp) (libSceVideoOut) - opening a bus that is already open returns `SCE_VIDEO_OUT_ERROR_RESOURCE_BUSY` (`0x80290009`), as [shadPS4's](https://github.com/shadps4-emu/shadPS4/blob/e0a466753a1aacbc8db8253be685bf7ab4d9daae/src/core/libraries/videoout/driver.cpp#L53-L60) PS4 driver does for its main port; the PS5 result is unverified. PPSA99764 opens the main bus twice and carries on, presenting through the first handle. [KytyPS5](https://github.com/KytyPS5/KytyPS5/blob/5e837a9beac82c031868eaad9348d6a48245fb99/src/graphics/presentation/videoOut.cpp#L651-L662) (PS5) returns the same error for an already open bus; [fpPS4](https://github.com/red-prig/fpPS4/blob/04cefd43e6fddd1ab033e7980cd356d14c964905/src/ps4_libscevideoout.pas#L656-L667) (PS4) opens another handle instead