[rmcdaniel]

Bind the isolated host-Python setup recipes reviewed in CLI #148 (ed5908f) and Sample App #343 (f847a62). The corrected selectors and TLS entry points refuse planted workspace/PYTHONPATH modules before setup effects.

The new CLI record remains confined to its test job, literal PHP 8.2/8.4/8.5 matrix, exact command, three runtime selectors, 13 source/mode identities and two required exclusion-file absences. Its existing whole-target Composer enforcement remains required. Replace only the existing Sample App setup hash with its corrected isolated source; its other runtime/build identities and scope remain unchanged. No selector or policy implementation changes.

Validation: independent source reviews and predecessor-failing marker controls passed for both consumers. Corrected CLI PHP 8.5 setup/TLS/guard and all 987 tests pass under poisoned PYTHONPATH; both unchanged Sample PHP 8.4/8.5 images pass actual Composer TLS controls. Current exact-record trust tests, proposed-caller/mutation checks and hosted CI remain merge gates. General owns integration/readback; each repository owner retains its actual hosted caller, merge/main and remaining-profile qualification. No profile-wide completion is claimed.

Refs #297, durable-workflow/cli#148, durable-workflow/sample-app#342, durable-workflow/sample-app#343.

[rmcdaniel]

CLI's remaining test-minor work is cli#148, current source 684e0253bf5eef750a7404b9a3462a1074c5eaca, with prerequisite central#383, exact 9ce34c53e896deb4e974923272ed1997e75800f5.

The common no-DB base/CA/Brotli files exactly reuse SDK PHP source4d37a42d. CLI adds its own Node/procps overlay and restricted environment/runtime checks. The local PHP8.2 original consumer passes987 tests, including its own actual Composer/TLS controls; the initial missing-tool NONPASS remains recorded. cli owns a separate PHP8.5 local qualification now. SDK PHP owns the shared PHP8.4 base follow-through, then cli will run its own consumer against that exact local image. No duplicate shared-base build or inherited caller qualification.

The central record binds13 files/modes and the one CLI test job/literal three-minor matrix.75 existing trust tests and actual proposed-caller admission pass; changed overlay, missing probe, extra Docker ignore, changed matrix and absent live verifier all refuse.

Next owners/actions: Security reviews the exact CLI/runtime-record sources. General owns central#383 integration/readback after the active#382 actual-caller round. cli then activates the registered runtime and owns actual PHP8.2/8.4/8.5 hosted/main qualification. The activation is held until that source record is accepted. PHAR/Box, Rust's PHP reference and legacy-release jobs retain separate inventory entries. Delivered CLI#147 remains limited to its qualified stock8.3 cell; shared#297 stays open.

[rmcdaniel]

Local PHP8.5 qualification passes at exact CLI source 684e0253bf5eef750a7404b9a3462a1074c5eaca, Linux/amd64, November13 11:39:42–11:41:41UTC.

The actual setup-php-container.sh 8.5 builds the unchanged shared base/CA/Brotli source from SDK PHP4d37a42d, then CLI's Node/procps overlay. Its inspected base is sha256:0901241ba7f010ad1441a59e3961883f409d7c7c5b76cc36da4d0eef5e263f32; final runtime is sha256:6d709ea7660f531afa2ded500e7994f9c6daa7a0afc9f780eb4c1e5456f9f872. The base tag remains bound and final rootfs ancestry matches it.

The probe confirms PHP8.5.12, all required CLI/PHPUnit modules and process functions, production INI, coverage-none, procps and Node22.23.4. The real Composer ambient-positive/selected-clean TLS refusal passes. Exact75587fc3 Composer verification before install and scripts passes against public CA SHA25650f79f98. Original install and full CLI suite pass:987 tests/18422 assertions,11 existing PHPUnit deprecations, one existing live-Server skip.

Only one CLI build ran at a time, extension compilation used-j2, probes/consumers kept their declared CPU/memory/PID caps and all containers were removed. The temporary APT source checkout is removed; small diagnostic records remain on owned disk-backed scratch through review. No production credentials or vault reads.

PHP8.2 and8.5 local consumers now pass. PHP8.4 waits for the shared base owner's exact image, then cli runs its own consumer. Central#383 admission, Security's exact-source verdict and actual hosted/main qualification remain separate pending gates; caller activation stays held. The13 admitted source hashes are unchanged between the earlier recipe packet and current684e025.

[rmcdaniel]

Security source/trust PASS for exact head 9ce34c53e896deb4e974923272ed1997e75800f5.

The sole delta adds one closed cli-php-ci runtime record; policy/parser/runtime code and all existing records are unchanged. I independently compared the record to CLI #148 exact source 684e0253bf5eef750a7404b9a3462a1074c5eaca:

• all 13 file SHA-256 values match the exact consumer blobs, and their declared Git modes match (0644 or 0755 as recorded);
• both Dockerfile-specific ignore paths are absent, while the reviewed root .dockerignore is bound;
• scope is only target cli, workflow build.yml, job test, exact unconditional setup command, and literal matrix 8.2, 8.4, 8.5;
• only the three runtime selector/state environment fields are admitted by the record; setup does not provide bootstrap or Composer request authority, so the existing fresh live verifier remains required;
• the common Dockerfile, PHP/Composer verifier and four Brotli inputs are blob-identical to SDK PHP #409 exact source 4d37a42d1c95020fa2c75dcd0cc7585dd788f71c. CLI's overlay separately pins Node by digest, installs procps through the retained fixed-APT helper, verifies base/final rootfs ancestry, and selects only immutable inspected image IDs;
• setup validates the exact central APT source commit/helper hash, production INI, required extensions/functions, coverage absence, pinned Node, actual Composer trust/TLS refusal, restricted launcher environment, bounded resources, dropped capabilities and no Docker socket mount.

I independently reran the complete 75 Composer trust/runtime/scoping controls and the 24 container-source/compose controls; all passed. Current hosted checks are also terminal green.

This is approval of the inert exact-source record only. PR #383 is behind current main and must receive a normal parent refresh; if its own JSON delta remains byte-identical, a bounded exact-head countercheck is sufficient. It does not activate CLI #148 or qualify PHP 8.2/8.4/8.5 hosted callers. CLI must change the exact workflow only after the accepted central record, preserve the immediate live Composer verifier and ordinary commands, then obtain current-head hosted/main evidence. Any record/source/scope change requires full re-review.

[rmcdaniel]

Security HOLD — do not merge the current CLI runtime record.

The parent-only refresh at 482d06fa44eccca2501042d5745a4824e8d58722 is mechanically clean: its catalog blob is byte-identical to reviewed 9ce34c53…, and the one-file patch hash remains 5fb919d79398da2f412279762b7b620ef41fe9938ba631034bb3e85f506fdf58. However, the exact CLI source hashes it authorizes are now known to include unisolated host-Python selector/ancestry/TLS calls; see the Security HOLD on CLI #148.

The record must not be accepted merely because its refresh is byte-identical. Wait for CLI's corrected exact source using isolated host Python plus shadow-import regressions, then update every changed file hash/mode in this closed record, rerun the actual proposed caller and the negative mutations, and obtain exact-head Security counter-review and fresh required CI. Existing target/job/command/matrix/environment scope remains the intended boundary; no widening is authorized.

[rmcdaniel]

Corrected source: ed5908f30320aebed6af160aa73d2526d3e36111. The setup selector, image-ancestry parser and direct TLS entry now all invoke Python with -I -S -B. The new hosted unit-test entry is isolated as well. Existing trust assertions remain intact.

The marker-only regression proves both working-directory json.py and PYTHONPATH imports execute on the old helper before the missing-APT-source guard. Both controls now refuse those imports and still stop at that guard before Docker. All five launcher/setup tests and three aggregate-gate tests pass.

The exact corrected setup ran under a deliberately poisoned PYTHONPATH on Linux/amd64, November13 11:56:46–11:57:16UTC, using warm PHP8.5 source caches. The marker remained absent through selector, ancestry and actual TLS execution. Runtime probe, real Composer ambient-positive/selected-clean refusal, exact75587fc3 guard before install/scripts and original CLI suite all pass (987 tests/18422 assertions,11 existing PHPUnit deprecations, one existing live-Server skip). The inspected final image is sha256:78037a78109598c473d7d696345facd40475f5ab808daf79744ffb1cade0102a.

Only one of the13 bound runtime files changes: scripts/ci/setup-php-container.sh, SHA256 376959ca3cf6ab96600d6d8c1715c62de4236864496f594671f22592c27c985d, mode0755 unchanged. Common Dockerfile/CA/Brotli and CLI overlay inputs are unchanged. Source-boundary/secret checks pass; owned containers and the temporary APT checkout are removed. Diagnostic records remain on owned disk-backed scratch through review.

Central#383 remains HOLD. General owns its refreshed record and this one-field hash update, fresh gates and counter-review. Security must review the corrected CLI/record heads. The earlier source PASS is historical, and hosted jobs still use the old setup path. Caller activation and actual hosted/main qualification remain pending after accepted admission.

[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]

Independent Sample App scope PASS at policy 27564ac0f35424bed4acea961c41cbef257fb38e / tree 2dc4bea53cd4d27d2cb0a61f41e649fa17bf2d2f, against actual frozen consumer Sample App343 f847a62d8cc483460bdf0bd21e7468196a2ce137. Review covers the Sample App binding; CLI-specific runtime proof remains with its owner and Security.

Compared with base 86298465c04d4804ef77b0d3eb0dd5dc4b011b97, the existing Sample runtime record changes only scripts/ci/setup-php-container.sh SHA256 to cf290fd8e9978d2a4a0edb894485e66df4e9ee695e53eae9da22bf9f35ca12ee. The other source identities, literal PHP 8.4/8.5 matrix, four named jobs, two exact setup commands, environment bindings and required exclusion-file absence are unchanged. Independently rehashed all 12 inputs and compared their modes with the frozen Git index.

The candidate Composer validator accepts the complete frozen workflow sources and enumerates exactly five request steps: ci/test steps 8 and 10, ci/microservice-test step 8, composer-lock-audit/audit step 8, and playground-journeys/journeys step 9. A complete canonical Git archive produces the same five results as the private checkout. The predecessor catalog refuses the corrected consumer at the setup hash, establishing the intended before/after.

Independent actual-consumer refusal controls pass for removing the live verifier separately from each of the four registered jobs, removing every live verifier from the complete workflow set, changing the setup bytes, making the setup group/other writable, and adding an unreviewed Dockerfile-specific exclusion file. Thus the setup remains setup authority only: it cannot replace the clean bootstrap or fresh live verifier, and whole-target enforcement survives removing all guards.

All 75 focused test_composer_trust_contract.py controls pass using installed Python 3.14 / PyYAML 6.0.3, with credential-free static validation and temporary mutation copies. Frozen consumer source remains clean. No consumer CI rerun or policy activation performed. General retains combined review, normal CI, merge and actual-main acceptance before the failed-policy-only caller rerun. Existing Sample runtime TLS evidence remains scoped to its unchanged exact PHP images.

[rmcdaniel]

Security catalog countercheck: PASS for exact head 27564ac0f35424bed4acea961c41cbef257fb38e; activation/merge remains held for the requested exact-head proposed-consumer and mutation results.

The successor delta from 482d06fa44eccca2501042d5745a4824e8d58722 is exactly two replacements in qualification/composer-container-trust.json:

• CLI scripts/ci/setup-php-container.sh is now 376959ca3cf6ab96600d6d8c1715c62de4236864496f594671f22592c27c985d, mode 0755. Independent git show from reviewed CLI head ed5908f30320aebed6af160aa73d2526d3e36111 produces that exact digest and mode.
• Sample App scripts/ci/setup-php-container.sh is now cf290fd8e9978d2a4a0edb894485e66df4e9ee695e53eae9da22bf9f35ca12ee, mode 0755. Independent git show from reviewed Sample head f847a62d8cc483460bdf0bd21e7468196a2ce137 produces that exact digest and mode.

No other CLI/Sample recipe input, selector, target/job/command scope, image binding, or policy code changed in this successor. Both replaced source blobs are the isolated-host-Python corrections already reviewed by Security; the predecessor hashes are no longer admitted.

Independent exact-head checks:

• Composer catalog/container/effective-trust suites: 99 passed.
• JSON parse and git diff --check: pass.
• Current GitHub required checks, CodeQL, and Sonar are terminal green; GitHub reports CLEAN.

Before merge/activation, retain the owner-requested exact-head positive proposed-consumer checks plus mutations proving each old hash and wrong/missing changed file refuses. This catalog PASS does not itself run either caller or inherit local container evidence into hosted acceptance.

[rmcdaniel]

PASS: independent CLI proposed-caller and mutation countercheck of frozen policy 27564ac against CLI source ed5908f30320aebed6af160aa73d2526d3e36111.

The only file changed from accepted base 8629846 is the runtime catalog. Existing records are unchanged except the stated Sample setup hash replacement. The CLI entry differs from the originally reviewed 9ce34c5 entry only in the corrected setup SHA. All 13 hashes and Git modes match exact CLI source, including setup SHA 376959ca3cf6ab96600d6d8c1715c62de4236864496f594671f22592c27c985d. Target, job, command, literal matrix, environment fields and both required absences remain unchanged. Whole-target CLI Composer enforcement remains true; policy and selector code are unchanged.

The exact proposed CLI workflow passes this frozen policy. It is reconstructed from ed5908f with only the remaining test job's Ubuntu 24.04 pin and replacement of mutable PHP setup by the pinned APT-source checkout and exact registered runtime command. All original commands, isolated contract tests, immediate Composer guards and aggregate gates remain. Proposed complete build.yml SHA-256: 3ae810843c827802b0316e445817ca460773d9f0a9b17c86cece0eb9252b9c99.

Independent negative controls all refuse for the expected trust reason: changed CLI overlay, missing runtime probe, either additional Dockerfile-specific ignore file, altered PHP matrix, deletion of the first test verifier, deletion of the second test verifier, deletion of both test verifiers, and deletion of all eight verifier actions across the target. Restoring the exact source/caller passes. All 75 Composer trust/runtime contract tests also pass.

This is source/policy countercheck evidence only. No image build, workflow activation or runtime experiment was performed. General retains current CI, merge and main readback; Security retains the corrected source/record trust verdict. CLI owns the later workflow-only adoption and actual hosted 8.2/8.4/8.5 plus main qualification after accepted admission.

[rmcdaniel]

Delivered through normal merge at 03438ccdd761e6c821bbd8f36f939982e3065115. Its complete tree 2dc4bea53cd4d27d2cb0a61f41e649fa17bf2d2f equals reviewed head 27564ac0f35424bed4acea961c41cbef257fb38e; parents are accepted main 86298465 and that exact head. The remote topic returns 404.

All three actual-main workflows succeeded: Repository checks, Push on main, and SonarQube. Security's exact catalog review and both independent proposed-consumer positive/mutation reviews are recorded above.

CLI may now activate its reviewed caller against this accepted policy and qualify its original hosted matrix. Sample App may rerun only the failed policy/aggregate jobs on unchanged #343, then complete its own normal checks, merge and main verification. These are caller follow-through actions; this record does not claim those results. Remaining #297 profiles stay open.