Restore the approved PHP 8.3 inputs after both upstream assets return 404 #403

The approved no-overrides PHP 8.3 setup can no longer fetch either frozen upstream archive. Fresh GitHub API metadata reads return HTTP 404 for shivammathur/php-ubuntu release asset IDs 739209532 (Ubuntu 24.04, SHA256 b81626ab8a7d91c23f3b8dee7fc0860fbd3ef99c9f4b22c5321b0e0545771768) and 739711545 (Ubuntu 26.04, SHA256 11c1a56755ec5d90567265719b21bc08e7c5ac4a539866a56f55c0fe5b6d196a).

Actual callers fail before PHP installation or repository tests:

• Central Admit Rust 1.99 for the existing CLI reference caller #401: Shared contract tests, Bound PHP setup refused, HTTP 404.
• CLI Document Rust build drain and resume qualification #161: PHP 8.3, same pre-test refusal.

The source remains qualification/php-linux-bootstrap.json and scripts/setup_php_linux.py in accepted central main. These are runner-blocked/NONPASS observations, not repository test failures. No authentication cause, fallback or retry is inferred. The existing fail-closed guards remain necessary.

Required outcome: restore an acquirable, reviewed PHP 8.3 input tuple for both affected hosted profiles. Recover identical original bytes from an authenticated retained source if available, or qualify replacement upstream identities through the existing source/archive/configuration/installed gates before updating the affected subjects. Account for the upstream release's asset replacement/retention behavior so the next daily replacement does not repeat this failure. Do not add credentials, ambient installations, unreviewed mirrors or automatic fallback.

Completion requires fresh actual setup qualification and green affected original callers, with the source/archive/configuration identities bound to that evidence. Cross-repository owner coordination belongs with General; individual repositories retain their own implementation and acceptance decisions.