Question about image repository content summary

When I look at the content summary for the latest version of one of my push repositories, container.manifest shows a large number of manifests for a relatively small number of tags (as shown in container.tag).

$ pulp show --href $(pulp container repository -t push show --repository myimage/external-dev | jq -r '.latest_version_href') | jq -r '.content_summary.present'
{
  "container.blob": {
    "count": 8836,
    "href": "/pulp/api/v3/content/container/blobs/?repository_version=/pulp/api/v3/repositories/container/container-push/01901276-89b9-74c8-b90b-9fd7c8ea5b8a/versions/6515/"
  },
  "container.manifest": {
    "count": 4175,
    "href": "/pulp/api/v3/content/container/manifests/?repository_version=/pulp/api/v3/repositories/container/container-push/01901276-89b9-74c8-b90b-9fd7c8ea5b8a/versions/6515/"
  },
  "container.tag": {
    "count": 39,
    "href": "/pulp/api/v3/content/container/tags/?repository_version=/pulp/api/v3/repositories/container/container-push/01901276-89b9-74c8-b90b-9fd7c8ea5b8a/versions/6515/"
  }
}

Furthermore, if I recursively go through each tag in container.tag and gather tagged_manifest and listed_manifests for that manifest and all related manifests, that list is completely different from the list in container.manifest. So what exactly does container.manifest show if not manifests that are associated with tags associated with the repository?

Start with the reported pulp show command and compare the container.manifest, container.tag, tagged_manifest, and listed_manifests content summaries for the same repository version. Trace how the repository-version summary is assembled and document or correct the definition of container.manifest so its contents can be reconciled with the related tags and manifests.