Discontinue rebundling commons reference documentation in implementation projects

I hate this, I kind of get why it's done but what's happening is confusion of what's actually supported in these projects, has a lot of this documentation says it's dependent on the implementation. Then the implementation doesn't actually mention what supported. I think it would be better to have some way that their documentation can either bundle only the parts they support or link back to only the parts they support.

For example I raised the question, And have asked for further documentation in neo4j of whether the Geo types are actually supported. I really couldn't tell from the reference documentation. Source diving shouldn't be required. Back in the day I had similar problem with neo4j and support for Optional. It could have course be argued that some of this is simply a problem with spring data in neo4j, I'm not sure, but I could see how it would easily be ignored to document that stuff since it's bundled in a sense.

The issue does not name files, tests, or an entry point. Start by tracing how Spring Data Commons reference documentation is rebundled into implementation projects, then compare the Neo4j documentation with the support it actually provides. Done means defining and documenting a clear way for each implementation to expose only supported reference content or link to it explicitly.