STM32WB09KEV6TR custom PCB: STLINK-V3PWR SWD fails with "Unable to get core ID"

[MuradV]

MCU: STM32WB09KEV6TR [User manual attached: "um3345..."]. Custom PCB based partly on NUCLEO-WB09KE / MB2032.

Debugger: STLINK-V3PWR [Datasheet attached: "dm009..."].

Software: STM32CubeProgrammer version 2.22.0

STLINK firmware: V4J7B3P6

Voltage Supply: CR2450. Multimeter states consistent 3.19V among several VDD pins. Yes, we did test using an bench supply of 3.3V.   

Interface / Port: SWD

Error: "Unable to get core ID" / "No STM32 target found! If your product embeds Debug Authentication, please perform a discovery using Debug Authentication"

STLINK-V3PWR DEBUG (controlled by page 22-23 in "dm009..."):
T_VCC -> board 3.19V / MCU VDD
GND -> board GND
SWDIO -> MCU PA2 / DB_SWDIO
SWCLK -> MCU PA3 / DB_SWCLK
T_NRST -> MCU RSTN via soldered wire on reset button net.

Screenshots:

Due to this ongoing bug, I am unable to add screenshots directly into the body of this post. I will redirect you to a third party, Imgur, to share the following screenshots: https://imgur.com/a/xruBJgr

• STM32CubeProgrammer Screenshot:
• Overview of debug pins on the STLINK:
• PCB Screenshot on Altium:
• PCB Schematics: 
• Logic Analyser on STM32CubeProgrammer Connect press. CH0 = SWDIO, CH1 = SWCLK, CH2 = NRST:
• Line Break: 54-55 bits (whatever this means):
• Channel 2 is the Reset pin, pressed once after -|-Programmer Connect press:

This project is based on a modified version of ST's "BLE_DirectionFinding_Peripheral_Tag" example project, provided by ST's .zip file here (this link is to a webpage). This will be a small BLE device that will be tracked by another BLE device. 

After soldering the components, the STLINK fails to find the target. We used a Logic Analyser to measure the voltage/signals at SWDIO and SWCLK. The STLINK is confirmed not dead. However, it doesn't appear as though the MCU is responding to these signals. 

We checked that there are no obvious VDD/GND short with a multimeter.

A double female connector is used to connect either UF to PA10 or BL (bootloader) to PA10 (PA10 is the unnamed header next to BL and UF). 

Same error persists in every Connect press and I don't understand why. I'm tempted to vaguely ask "why does it not work?". 

But instead I'll ask these:

• Is this the correct minimum SWD wiring for STM32WB09KE with STLINK-V3PWR? 
• Should STM32WB09KEV6TR be detectable over SWD on a blank/custom board without using PA10 bootloader mode?
• Any other measurements or tests to be conducted to isolate or narrow the problem?