Retained final-link metadata for CPython 3.14.7 Android release artifacts

检查 release run 30997736469、其 ARM64 job 92278883796 以及 release-tools commit f7f0f33700b3e1b4bc284042f10fccee0ab7f12b。确定是否存在针对所述五个扩展的原始 final-link maps、reproducer bundles、input manifests 或 producer 记录的 dependency checksums。完成标准是提供带有 provenance 的留存记录，或确认这些记录未被留存，并在需要时确定适当的 repository。

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!