[rmcdaniel]

Package/application code previously ran with write access to the repository and host-wrapper state, so it could replace the launcher or the next nominal host verifier. This change mounts both read-only and permits writes only to declared dependency, temporary, Composer and PHPUnit-cache paths. Setup runs replacement-refusal controls before exporting host wrappers, and the PHP matrix waits for the central policy preflight.

The disposable regression proves launcher overwrite, wrapper unlink/replacement and wrapper rename are refused, required data writes still work, and the next actual PHP call uses the original wrapper. Source/trust review and exact central #390 admission passed before normal merge.

Delivered at main 174cd115fa9c1b2a28bc00ebfa9b307572ab35ed, whose complete tree matches reviewed 674e960. Fresh hosted PHP 8.2/8.4/8.5 each passed 987 tests / 18,422 assertions with actual TLS, module/config, Composer and replacement controls. All four actual-main workflows and the terminal aggregate passed. Final source/caller/main receipt.

Remaining PHAR/Box and PHP-reference caller profiles under shared #297 are separate.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud

[rmcdaniel]

Exact corrected source 674e960cea4db99e65f6b1a1701ced4380e21e6f is ready for source/trust counter-review. Activation and merge remain held on the updated central record and fresh hosted/main evidence.

Actual local proof uses unchanged immutable PHP 8.4 CLI image sha256:747afb163fc37bffdf92b327da725e606a0695ba984398d09dd4b7e5f2fcb8d5, credential-free private source/state and the existing selected public CA/Composer verifier. The original launcher from main 847f291 lets all three disposable attacks replace the subsequent host PHP entry with the harmless marker. The corrected source refuses launcher overwrite, wrapper unlink/replacement and wrapper rename, preserves the launcher hash/symlink, still permits required data writes and executes actual container PHP on the following host call. All six offline launcher/isolation controls and four build-gate controls pass.

At 2026-11-13 13:41:04–13:42:21 UTC, runtime/module/INI probe, real Composer ambient-positive/selected-clean TLS-before-HTTP control, actual Composer guard, original composer install --prefer-dist --no-interaction, immediate guard recheck and original composer test pass: 987 tests / 18,422 assertions, 11 existing deprecations / one existing live-server skip. The first guard attempt failed because the hand-built local environment omitted GIT_SSL_CAPATH; after configuring all required clean-store variables, both actual guards passed. No source or trust check was bypassed. All owned containers were removed and no base build was repeated.

The exact runtime record retains target/job/command/matrix/environment/required absences and ten unchanged input identities. Only these three hashes change and one new runtime-test source is added (14 bound inputs total):

Source	SHA256	Mode
scripts/ci/setup-php-container.sh	a7007c0fbef886b7e29b62d20b76404839746620361a9dd9e6024f1ff546d49b	755
scripts/ci/run-php-container.sh	baef1e07ac53ce31fed01eac37ced2f98e363fa677e129952f6e15e47213db0e	755
scripts/ci/test-php-container-tls.py	da11950ff46810ba425fea6bb6a453869995204388570d1f764a160154f3e7b0	644
scripts/ci/test-php-container-boundary.py	8d4db79b20598e5e9f1fc64f6a730b574d6f2161cc42a01442ac0095dc8684e9	644

The protected repository and whole state mounts are read-only; writable overlays contain vendor data, private home/Composer/tmp and a newly created private PHPUnit cache file. Writable mount roots and both cache paths must be real, nonsymlink paths. Test source and state/bin are never writable. The full workflow change only adds the action-policy dependency; original commands/versions/aggregate coverage remain. Hosted preflight has failed and the container matrix was skipped, proving the new source cannot activate under the old exact record. Other existing jobs continue normally; their outcomes cannot qualify this corrected container caller.

General owns the central exact-record integration and current gates; Security owns the independent source/trust verdict. cli owns any corrections, the actual hosted 8.2/8.4/8.5 callers and main follow-through. Shared #297 remains open; #148's earlier trust acceptance is historical for this newly found boundary.

Record correction: the first generated table/JSON used private checkout permissions for regular files (0600). The exact record now uses committed Git modes 0644/0755, as a fresh hosted checkout does. Source hashes and head are unchanged; precisely three existing entries change and one is added.

[rmcdaniel]

Local proposed-record countercheck at central policy 3cc290d4585797bebda57f2cd2ab4dbafc4a02ca, exact CLI 674e960cea4db99e65f6b1a1701ced4380e21e6f: PASS for the proposed record, without changing a central integration branch.

A clean Git archive of the actual caller fails under the accepted old record, specifically at the changed setup source hash. With only the corrected 14-file runtime entry substituted in an isolated policy checkout, the exact caller passes. Negative controls reject reintroduced writable repository/state mounts, deleted boundary proof, deleted setup invocation, either Docker-specific ignore override, wrong PHP matrix and fixed-minor substitution for the approved matrix command. Comment-preserving deletion of the first, second, both test verifiers and all eight target verifier entries fails for the required Composer bootstrap/live-verifier reason. The restored exact caller passes again.

An earlier mutation attempt serialized YAML and lost required action-version comments, so those four failures were unrelated to Composer trust and are explicitly excluded. The meaningful verifier-deletion controls preserve source comments and reach the intended trust rule. Proposed validation is not accepted-main authority: Security review, General's exact record integration/current gates and actual hosted/main caller qualification remain required. No runtime/build was run by these policy checks.

[rmcdaniel]

Security exact-head source/trust review: PASS for 674e960cea4db99e65f6b1a1701ced4380e21e6f (source boundary only).

I independently reviewed the eight-file delta and verified the material boundary:

• the repository root and whole launcher-state root are read-only container mounts;
• the only writable overlays are vendor, private home/tmp/Composer data, and the single PHPUnit result-cache data file;
• each writable directory and both cache paths must already be a real, nonsymlink path before Docker is called;
• the host-executed launcher, wrapper directory, tests, Git metadata, verifier action, and selected CA inputs remain outside those writable overlays and are mounted read-only where exposed;
• the read-only parents prevent application code from unlinking or renaming a writable mount root or replacing the wrapper/launcher between host invocations;
• environment forwarding, immutable-image selection, caller UID, resource caps, capability drop, no-new-privileges, Composer-PHAR substitution, and credential exclusion are preserved;
• the TLS fixture's disposable project moved under the approved private tmp overlay, without broadening trust or credential inputs; and
• the workflow now requires action-policy before the changed container cells can execute, while the aggregate gate still covers the skipped/failed result.

I independently replayed test-php-container-boundary.py against retained immutable image sha256:747afb163fc37bffdf92b327da725e606a0695ba984398d09dd4b7e5f2fcb8d5. All three disposable attacks (launcher overwrite, wrapper unlink/replacement, wrapper rename) were refused; every necessary data write succeeded; the launcher digest and wrapper symlink remained intact; and the following host wrapper invocation executed real container PHP. The test completed in 3.399s and left no owned container or scratch directory.

The four changed/new bound files independently hash to the values recorded in the PR (a7007c0f..., baef1e07..., da11950f..., 8d4db79b...) with canonical Git modes 0755/0755/0644/0644. git diff --check is clean. Hosted analysis, public-boundary, CodeQL, Sonar, PHAR and Rust jobs are green. The current central-policy failure and skipped changed-runtime matrix are the correct fail-closed result while the old record is active; they are not a qualification failure to bypass.

This PASS does not authorize merge or runtime activation. Those remain held until General lands and Security counter-reviews the exact corrected central record, the exact caller is admitted by accepted main, and fresh hosted PHP 8.2/8.4/8.5 plus required aggregate/main follow-through succeed. Earlier #148 runtime evidence remains historical for this newly corrected boundary.

[rmcdaniel]

Actual hosted correction qualification PASS at unchanged Security-reviewed CLI source 674e960cea4db99e65f6b1a1701ced4380e21e6f, after central #390 accepted main 8e3cceac and all three central main workflows passed.

Build 43435500373 attempt 2 passes central source policy, all three affected container callers, the separately qualified PHP 8.3 cell, PHAR/reproducibility, both Rust parity jobs and the required aggregate. All other exact-head analysis/boundary/Sonar checks are green. Attempt 1's source-hash refusal and skipped matrix remain expected NONPASS evidence before admission; they are not substituted for these actual callers.

PHP caller	Actual immutable CLI runtime image	Original test result
8.2	sha256:cfbe1e43eb7ab4ec983a04a5d0f6d715f59669ae3242335e45abd2d49e0a4aea	987 tests / 18,422 assertions
8.4	sha256:707ba66ee34f115f6d9160a3c0b425956f2f1f8e60b9221c54199d66a632e381	987 tests / 18,422 assertions
8.5	sha256:54f041a3dac6201d6e503ce8ae85471fb0c7ea0c4f3fd326623b00c7b150fe08	987 tests / 18,422 assertions

Each actual setup includes module/INI/image/ancestry probes, real TLS refusal and the disposable three-attack host-control replacement test before exporting launchers; each original consumer passes both actual Composer guards. I independently read all three terminal job logs and confirmed their runtime identities, replacement-control execution and original totals. Existing 11 PHPUnit deprecations and one live-server skip remain explicit.

cli now owns normal merge, complete-tree comparison, remote-branch deletion/absence and fresh main checks. No package release is required for this CI-only correction; other #297 profiles and all #216 product gates remain separate.

[rmcdaniel]

CLI #149 is delivered. Accepted main 174cd115fa9c1b2a28bc00ebfa9b307572ab35ed, complete tree cfb777bf043afdd764076f0bbed17915a1cd2a22, is byte-identical to Security-reviewed source 674e960cea4db99e65f6b1a1701ced4380e21e6f. The topic branch was deleted after matching its head; remote absence was verified.

The source/control and exact central admission gates passed before normal merge: source Security verdict, accepted central record and main verification, and actual hosted PHP 8.2/8.4/8.5 caller receipt. Each exact PR matrix cell passed the original 987 tests / 18,422 assertions, actual TLS and filesystem replacement controls, module/config probes and Composer guards. The earlier old-record refusal remains recorded; it supplied no caller qualification.

All four actual-main workflows are now successful at that merge: Build 43444128559, Public Boundary 43444128562, Sonar 43444128646, CodeQL 43444128149. Build includes fresh PHP 8.2/8.4/8.5 cells and the terminal aggregate; all jobs succeeded.

Repository and host control state stay read-only inside package/application execution; only declared dependency/cache/data paths are writable. This closes the CLI test-matrix boundary correction. Remaining PHAR/Box and PHP-reference caller profiles under shared #297 are still owned by cli; this does not qualify those profiles, another repository, or #216. Current CLI inventory: zero open issues, zero open PRs. Next cli work is shared #387 transport-fixture gates, then remaining distinct #297 caller profiles; downstream docs #536 counter-review is in progress.