Problems with `package-list`

1. package-list is in a root folder for a milti-module project, e.g. here. Although in a single module project package-list is in a non-root folder, e.g. here. I agree with Marcin: javadoc places element-list near index.html, like dokka does for multimodule. It can make sense to unify the single module.
2. You can compare old package-list of stdlib and https://vmishenev.github.io/kotlin-dokka-stdlib/prefinal/stdlib/package-list. The latter has a huge size. I think there are too many redundant $dokka.location commands.
3. We do not specify cases of using $dokka.location directives explicitly. It would be great to have a doc (e.g. KDoc) describing a package-list format.

[hfhbd]

Another problem: the list is flat: https://github.com/Kotlin/dokka/issues/2444#issuecomment-1100117274

[vmishenev]

Feature to consider, related to package lists: help users understand which package lists are missing.

It was in old Dokka #1470

Use case is the following: build agents don’t have access to the internet, so package lists are cached locally and supplied as plain files (as opposed to providing internet URLs). The problem is that it’s difficult to understand when external package lists have been updated and thus should be pulled and cached locally.

Is this a practical case? What type of cache do you mean? Can a timestamp help?