I'm in a similar position. But as of Nov 27,2015 I don't think this is supported. I totally agree with you about the documentation issue. When I execute bluetoothctl and poke around this is what I found.....Here's why it doesn't work-

Bluetooth capability mismatch- Raspberry Pi bluetooth doesn't report a UUID for A2DP, I'm expecting that it should. Also /etc/Bluetooth doesn't have an audio.conf file like everyone on the web references. I think that has meaning.

[CHG] Device 20:13:07:17:AC:47 Connected: yes [JETech S2020]# info 20:13:07:17:AC:47 Device 20:13:07:17:AC:47 Name: JETech S2020 Alias: JETech S2020 Class: 0x240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Headset (00001108-0000-1000-8000-00805f9b34fb) UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb) UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb) [CHG] Controller 00:19:0E:15:62:FA Discoverable: no [JETech S2020]# info 00:19:0E:15:62:FA Device 00:19:0E:15:62:FA not available [JETech S2020]# show Controller 00:19:0E:15:62:FA Name: raspberrypi Alias: raspberrypi Class: 0x0c041c Powered: yes Discoverable: no Pairable: yes UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb) UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb) UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb) UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0517 Discovering: no [JETech S2020]#

I'm in a similar position. But as of Nov 27,2015 I don't think this is supported. I totally agree with you about the documentation issue. When I execute bluetoothctl and poke around this is what I found. Here's why it doesn't work:

Bluetooth capability mismatch- Raspberry Pi bluetooth doesn't report a UUID for A2DP, I'm expecting that it should. Also /etc/bluetooth doesn't have an audio.conf file like everyone on the web references. I think that has meaning.

[CHG] Device 20:13:07:17:AC:47 Connected: yes
[JETech S2020]# info 20:13:07:17:AC:47
Device 20:13:07:17:AC:47
        Name: JETech S2020
        Alias: JETech S2020
        Class: 0x240404
        Icon: audio-card
        Paired: yes
        Trusted: yes
        Blocked: no
        Connected: yes
        LegacyPairing: no
        UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
        UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
        UUID: Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)
[CHG] Controller 00:19:0E:15:62:FA Discoverable: no
[JETech S2020]# info 00:19:0E:15:62:FA
Device 00:19:0E:15:62:FA not available
[JETech S2020]# show
Controller 00:19:0E:15:62:FA
        Name: raspberrypi
        Alias: raspberrypi
        Class: 0x0c041c
        Powered: yes
        Discoverable: no
        Pairable: yes
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
        UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
        UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
        UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
        Modalias: usb:v1D6Bp0246d0517
        Discovering: no