So... your preference is noted, but consider the following.

1. People's first access to this code (in a stack trace) is going to be this generated adapter
2. Inheritance loses some context which you have to follow, which means you can't "just see" what's going on.
3. This definitely is balanced in favour of the newbie who doesn't know the infrastructure - you are not your customer. 

The documentation is repeated so it's as local to a reader's context as possible - as such it has to be duplicated.  You may not appreciate it's aesthetics, but you can skip over it - someone who is reading the code would have to go elsewhere to understand it then return.  I'm trying to avoid that.

That said, the javadocs are the weakest part of this change, and in some cases, I am happy to replace with.
```
// internal infrastructure
// Provider<T> implementation
// MembersInjector<T> implementation
```

But I still think a full Javadoc is valid.  Most people reading dagger code (if Guice is any example) won't be people who know the DI framework, it'll be people who inherited it and need docs as close as they can to the proximal cause of error so they can understand things well enough to determine the root cause.