[rmcdaniel]

Problem

The bound Ubuntu 24.04/x64 PHP 8.3 archive asset 739209532 was deleted upstream. Current consumers fail with HTTP 404 before PHP or repository tests run.

Change

• pin current same-name asset 747287433 (43,826,053 bytes, SHA-256 c60a4af4c7806c8c123268305b35ba1f7250a8356b195997bd0860359b101784)
• regenerate the complete archive-header and normalization records from those independently verified bytes
• rebind the alternatives and configured-profile records to the new archive identity
• keep the setup profile, installer, tools, trust boundary, and refusal behavior unchanged

Verification

• release API metadata and downloaded bytes agree on ID, name, size, and digest
• python3 -m unittest tests.test_php_linux_bootstrap tests.test_php_linux_tools tests.test_php_linux_recipe tests.test_php_linux_archive tests.test_setup_php_linux tests.test_php_linux_normalize tests.test_php_linux_alternatives tests.test_php_linux_configuration tests.test_php_linux_qualification tests.test_php_linux_archive_metadata (153 tests)
• git diff --check

This is the clearing source change for the concrete blocker recorded on #297. Hosted exact-head qualification and consumer pin movement remain separate gates.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[rmcdaniel]

Superseded by #404, which contains the same independently reproduced Ubuntu 24 records plus the simultaneously replaced Ubuntu 26 archive. The exact-source workflow finding is tracked on #404; keeping a partial competing fix would slow the shared repair.