"""H5P → Sphinx packaging utilities.

Four-stage pipeline that mirrors the upstream H5P ecosystem into
Bitbucket and scaffolds a Python Sphinx extension package for each
content type.  The stages are:

``h5porg.repository.mirror``
    Clones every content-type repository from GitHub into the
    hosting Bitbucket workspace.

``h5porg.repository.index``
    Walks the mirror set and emits ``data/package-index.json``
    keyed by H5P machine name.

``bootstrap``
    Scaffolds the Python package skeleton for a content type,
    recursively pulling in every library reached via
    ``preloadedDependencies``.

``build``
    Runs inside a scaffolded package; reads ``library.json`` and
    ``semantics.json`` and emits ``_generated/`` (directive, node
    classes, asset registration) plus vendored ``_static/`` assets.

Top-level runtime constants and the :class:`IndexCommand` CLI wiring
live in :mod:`~byteb4rb1e.sphinxcontrib.h5p.utils.pkg.index`; the
name taxonomy (``dir_name``, ``pip_name``, ``import_name``, etc.)
is documented alongside.
"""
