docs: record compatibility audits of 115 GitPython dependents

The five automated downstream profiles do not describe GitPython's wider
runtime, development and documentation consumers. Record four completed audit
batches of 31, 30, 39 and 15 distinct projects selected from September 2026
PyPI downloads plus known Git-focused users. The inventory covers every
identified current declared consumer within the top-15,000 snapshot and
348,530,835 monthly distribution requests, including extras. Downloads are
neither unique users nor attributable GitPython installations; the additions
and metadata limits also prevent a strict popularity top-115 claim.

Retain all four reports and JSON manifests under `test/downstream/`, linked
from its README. Preserve release and archive provenance, commands, import
proofs, backend results, baseline comparisons and coverage limits at their
original tested revisions. Sources, environments, logs, JUnit XML and
supplemental runners remain in ignored audit caches; a fresh environment must
reconstruct the disclosed harness. The five-profile CI runner remains the
maintained automation. Upstream tests, mocks and expectations are unchanged;
selected helpers, unused declarations and omitted application stacks are
identified explicitly. Gix selections retain documented Git CLI fallbacks.

Twelve separate fixes restore immutable index readers, global `-C` selection,
separate-Git-directory context, the `GitDB` selector, local tracking branches,
revision tree/path diagnostics, explicit literal-path construction, editable
version reporting, built-wheel version isolation, historical `Union` and
`Optional` imports, and nonempty configuration-section assignment.

Keep the remaining compatibility work visible. Kas 5.5 has three SSH setup
failures because `add_section()` cannot create an empty section through the
supported native APIs; downstream can use `set_value()` directly, while full
compatibility requires a native section-edit API. sbxloop 2.1.36 has five
constructor-subclass failures because native discovery validates metadata
before its overridden `config_reader()` runs; restoring that view requires
supported discovery/include controls without bypassing Git format validation.
Index mapping mutation and automatic environment expansion remain unsupported.
Airflow's ambiguous bare/mirror fetch results expose a separate GitPython
adapter gap: Git `fetch --porcelain` supplies full destination identities for
a future CLI adapter fix; Gix fetch remains a fallback until per-ref outcomes
are exposed. Other retained failures are downstream defects, baseline behavior
or explicitly recorded harness/coverage limits, not passing results.

Historical final full suites after the last production fix recorded 1,832
CLI passes and 1,934 Gix passes, with 162/60 skips, one xfail and 59 passed
subtests each. The last batch adds 117 upstream and 187 supplemental passes,
one baseline-inherited Dstack failure and two Jira skips per backend; its
separate MkNotebooks Binder build passes with both backends and the release.
Those historical results are not reruns on this rewritten stack.

Consolidate the four `docs:` record commits at the stack tip while retaining
the feature commit and twelve fixes in their original order. Resolve only
changelog context conflicts, keeping implementation entries with their fixes
and the subclass record here. Verify an identical final tree, unchanged
non-documentation patches, fourteen final commits with one top `docs:` commit,
115 distinct manifest projects, recorded CLI/Gix parity, local report links
and `git diff --check`. No new tests or hosted CI were run and no push occurred.

Author: codex

doc/gix-backend.md

@@ -51,6 +51,24 @@ variables literal; `expand_vars=True` is unsupported. Callers wanting expansion
 must perform it before passing the path. Discovery still uses Gix/Git after
 ordinary input-path canonicalization.
 
+Repository construction validates storage and configuration through Gix/Git;
+overriding `Repo.config_reader()` does not replace that native discovery parser.
+sbxloop 2.1.36's `_MetadataRepo` subclass relied on the released constructor's
+permissive Python discovery and overridden no-includes reader. Five upstream
+tests still differ: malformed includes prevent opening, malformed local config
+is rejected before its custom `ProvisionError`, and version-0 repositories
+with version-1 storage extensions are rejected before its format check. Released
+GitPython 3.2.1 passes those five tests. This is a breaking subclass contract,
+not a demonstrated Gix-versus-Git mismatch: both backends reject the metadata.
+GixPython `OpenOptions` has strict/lossy configuration controls and overrides,
+but no supported option to open a repository while omitting its local include
+graph. A replacement must expose separately controlled metadata discovery and
+literal local configuration access with Git-compatible format validation.
+Do not bypass validation or reconstruct discovery/storage in Python to restore
+the old constructor. Downstream must construct its trusted metadata view before
+opening it with `Repo`, and handle native discovery errors explicitly; its
+original tests remain failed in the audit.
+
 `git.GitDB` and `git.db.GitDB` remain compatibility aliases for
 `GitCmdObjectDB`, so legacy `Repo(..., odbt=GitDB)` selectors use the same
 managed backend. Aider 0.86.2 uses that selector for every repository open.

doc/source/changes.rst

@@ -61,6 +61,12 @@ API changes
 * Editable/source imports expose the release version in ``git.__version__``,
   matching built distributions. Salt's GitPython provider checks can parse the
   version instead of rejecting the unstamped ``"git"`` build placeholder.
+* ``Repo`` construction validates repository configuration through Git/Gix.
+  A subclass override of ``config_reader()`` no longer controls discovery or
+  suppresses its include graph. Malformed configuration and invalid repository
+  extensions can fail before downstream custom validation runs. sbxloop's
+  metadata-reader subclass exposes this remaining compatibility break; callers
+  must prepare their trusted metadata view before opening it with ``Repo``.
 * Revision root trees such as ``Repo.rev_parse("HEAD:")`` retain their empty
   path and can be iterated. Missing paths within a valid tree revision retain
   ``Tree.join()``'s ``KeyError`` and missing-component message, restoring MCP

test/downstream/README.md

@@ -1,5 +1,31 @@
 # Downstream compatibility
 
+The [2026-10-22 audit](audit-2026-10-22.md) covers 31 projects, including major
+runtime, development and documentation users. Its [manifest](audit-2026-10-22.json)
+records releases, source hashes, commands, results and coverage limits. The runner
+below automates five CI profiles; it is not the complete audit inventory.
+
+The [second 30-project batch](audit-2026-10-22-batch-2.md) brings the total to
+61 processed projects, with four further local fixes and explicitly retained
+compatibility, downstream and harness failures. Its
+[manifest](audit-2026-10-22-batch-2.json) records the next popularity-ranked
+selection and results on both backends.
+
+The [third 39-project batch](audit-2026-10-22-batch-3.md) brings the audit to
+100 distinct projects. It records further local compatibility fixes, three
+remaining Kas configuration API failures, and failures inherited from released
+GitPython. Its [manifest](audit-2026-10-22-batch-3.json) includes verified release
+archives, commands, import proofs and coverage limits. Additional selections are
+popularity-ranked; the original known-user additions mean this is a 100-project
+audit rather than a strict mathematical top 100.
+
+The [remaining 15-project batch](audit-2026-10-23-batch-4.md) brings the audit to
+115 distinct projects and completes every identified current declared consumer
+in the September snapshot of the top 15,000 distributions. Its
+[manifest](audit-2026-10-23-batch-4.json) records released callers, tests, baseline
+comparisons and limits. This covers the identified distribution download weight;
+it does not attribute GitPython installs or imply complete application coverage.
+
 Run released projects' GitPython-related tests against this checkout with
 [uv](https://docs.astral.sh/uv/) and Git 2.52 or newer:
 
@@ -35,19 +61,22 @@ settings, pytest options/plugins, and Python import paths are cleared before
 setup and testing. Select a different Git executable by putting its directory
 first on `PATH`.
 
-## Selection and coverage
+## Automated CI profiles
 
-The selection uses current runtime users, including optional end-user features,
+These five profiles use current runtime users, including optional end-user features,
 ranked by September 2026 PyPI distribution downloads. Development, documentation,
 and test-only dependencies are excluded. Downloads are not unique installations.
 
 | Project | Distribution downloads | Last tested release | Selected coverage |
 | --- | ---: | --- | --- |
 | LangChain Community | 27,882,881 | 0.4.2 | 2 upstream GitLoader tests: real clones, commits, checkout, tree traversal, ignored paths, and remote validation |
-| MLflow (`mlflow-skinny`) | 25,850,354 | 3.17.0 | 47 upstream tests: 31 repository/project/model-versioning cases plus 16 Git context and credential-redaction contract cases |
+| MLflow (`mlflow-skinny`) | 25,850,354 | 3.17.2 | 53 unique upstream repository/project/model-versioning, Git context and credential-redaction cases in the expanded audit |
 | Bandit | 24,935,372 | 1.9.4 | 12 upstream baseline CLI tests: real repository creation, commits, branches, resets, discovery, and dirty state |
 | SWE-bench | 22,942,741 | 5.0.2 | 4 supplemental integration cases for `AutoContextManager`; no upstream tests cover its GitPython callers |
-| DataHub (`acryl-datahub`) | 5,019,402 | 1.7.0.14 | 7 upstream tests passed, 1 credential-dependent skip: public clone/checkout, SSH timeout, exception/redaction contracts, and configuration |
+| DataHub (`acryl-datahub`) | 5,019,402 | 1.7.0.16 | 8 upstream tests passed, 1 credential-dependent skip: clone/checkout, SSH timeout, exception/redaction contracts, configuration and ODCS sourcing |
+
+The runner automates the original selections. The linked audit broadens MLflow
+with `tests/projects/test_utils.py` and DataHub with its ODCS Git sourcing test.
 
 Source: [top-pypi-packages](https://hugovk.github.io/top-pypi-packages/top-pypi-packages.min.json),
 snapshot updated **2026-10-01 12:40:51 UTC**. Its