I believe the difference is that chromedriver still spins up all the normal chrome interface, which wouldn't be needed for the headless chrome. I think the stated deliverables help discern the intention:

1. A library which headless applications can link to to. 2. A sample application which demonstrates the use of headless APIs.