The Artifact Registry section in CONTRIBUTING.md directs contributors only to the Python registry loader at cli/python/base_setup/registry.py. The actual registry data lives in lib/base/artifact-registry.yaml, which is the YAML source loaded by that Python file and documented in docs/artifact-adapter-registry.md. A contributor wanting to add or modify an artifact adapter definition will look in the wrong place — registry.py is the loader, not where adapter entries are declared.
Fix: Add a reference to lib/base/artifact-registry.yaml as the registry data file in the CONTRIBUTING.md Artifact Registry section, alongside the existing reference to the Python loader. Add a one-line description of each file's role.
File: CONTRIBUTING.md
The Artifact Registry section in
CONTRIBUTING.mddirects contributors only to the Python registry loader atcli/python/base_setup/registry.py. The actual registry data lives inlib/base/artifact-registry.yaml, which is the YAML source loaded by that Python file and documented indocs/artifact-adapter-registry.md. A contributor wanting to add or modify an artifact adapter definition will look in the wrong place —registry.pyis the loader, not where adapter entries are declared.Fix: Add a reference to
lib/base/artifact-registry.yamlas the registry data file in the CONTRIBUTING.md Artifact Registry section, alongside the existing reference to the Python loader. Add a one-line description of each file's role.File:
CONTRIBUTING.md