Retained final-link metadata for CPython 3.14.7 Android release artifacts

We are documenting the native linkage of python-3.14.7-aarch64-linux-android.tar.gz (SHA-256 6d50cc3aa66e414a439594089bcdfb5f1264358155c70c1f00471c24cfb477fb), produced by release run 30997736469, ARM64 job 92278883796, at release-tools commit f7f0f33700b3e1b4bc284042f10fccee0ab7f12b.

Are any original final-link maps, linker reproducer bundles, or matching object/archive input manifests retained for _bz2, _lzma, _zstd, _decimal, and pyexpat? We would also appreciate any producer-recorded checksums for the external static-dependency archives downloaded by this build.

We already recovered the release logs, generated Makefile/Setup/config, source revisions, and original dependency notices. The remaining question concerns exact archive-member/section contribution after final linking—not a missing-notice or security report. Production of the prerequisite dependency archives is a separate question for BeeWare; this request concerns the CPython final links and their recorded inputs.

If these records were not retained, confirmation would also help. Please distinguish original producing-build records from subsequently regenerated metadata, and let us know if another repository is the better place for this request. No credentials or private runner data are requested.

Thank you!

Überprüfe den Release-Run 30997736469, dessen ARM64-Job 92278883796 und den release-tools-Commit f7f0f33700b3e1b4bc284042f10fccee0ab7f12b. Ermittle, ob originale Final-Link-Maps, Reproducer-Bundles, Input-Manifeste oder vom Producer aufgezeichnete Dependency-Checksums für die fünf genannten Extensions vorhanden sind. Erledigt ist dies, wenn die aufbewahrten Datensätze mit Provenienz bereitgestellt werden oder bestätigt wird, dass sie nicht aufbewahrt wurden, und bei Bedarf das zuständige Repository identifiziert wird.