First of all, I would like to say that you have explained the individual components in the architecture very well and have been able to create a good overview. However, I have to criticise the placement of services. In the hexagonal architecture, we want to abstract the individual components from each other in order to minimise the coupling. The domain should be at the core (aka the business logic). However, in your design, services (I assume Spring Services here) are in the core, which makes the entire architecture of the domain dependent on the framework you use and thus introduces coupling. Which is what you want to prevent, because the domain should not depend on anyone.
Can someone share the project? Is it in github? During the video he said is really close to the production code but maybe he had the chance to publish the example code somewhere
Before i knew port adapter pattern with tdd, i confused when i use unit,integreation test. Your presentation is best of port adapter pattern explain in tdd.
