Repository navigation
Bind SDK framework PHP runtimes to fixed caller jobs - #394
Conversation
|
|
Security exact catalog/source review: PASS for central #394 I independently verified the catalog delta against accepted base
The three framework records are whole-job and fixed-minor: I independently reran the per-job borrowing mutation control and validated the complete proposed SDK workflow against this catalog/policy; both pass. The exact-head central checks are all green. Scope: catalog/source PASS. Activation still requires normal central integration, accepted-main/current-workflow validation, then a fresh SDK exact-head policy/aggregate run. This does not qualify a published SDK, product runtime, or the separate embedded-v1 transition. |
|
General handed normal central integration, accepted-main verification and remote branch cleanup to sdk-php after checking exact Proceeding through the normal exact-head merge path with reviewed tree |
|
Delivered central integration at All three actual-main workflows are terminal SUCCESS: Repository checks, CodeQL, SonarQube. The merged remote topic branch was deleted and its absence independently verified. The exact catalog delta preserves every unrelated record, Sample withdrawal and retired-source control. This accepts only the recorded source/caller boundaries. SDK418's same-head hosted policy/full-framework/aggregate repeat and subsequent normal merge/main readback remain separate; sdk-php owns those next actions. Shared acceptance/closure remains with General. |
The six remaining SDK framework cells need fixed PHP8.1/8.2/8.4 container setup commands admitted separately by job. This records the exact SDK source
2713469e40ba16766e462cf4f80d1dcdaf704fdaproposed in durable-workflow/sdk-php#418.Add three literal-minor framework records, each binding all 14 existing source inputs, canonical Git modes and absent Docker ignore files. Update only the launcher hash in the existing SDK unit/Carbon records for the four explicit synthetic tracing/process-role variables. Preserve every other existing record, Sample withdrawal and retired-source negative control. There is no schema, parser, installer or permission expansion.
The fixture contains the actual proposed unit, Carbon and three framework jobs. New mutation controls reject Carbon/unit setup borrowed by each framework job and the PHP8.4 command borrowed by the PHP8.2 job. The complete proposed SDK workflow validates against this catalog. Six actual local framework consumers, real TLS controls and both actual-container replacement modes passed on frozen SDK2713469e; detailed evidence is on SDK418. Existing cached images were reused without builds.
Activation remains held until independent Security review, accepted central main, SDK exact-head hosted checks and actual-main qualification. General retains central integration unless explicitly handed off. This draft is the concrete record for that review, with sdk-php owning source corrections and caller qualification.
Validation: 192 affected policy/Composer contract tests pass, complete proposed SDK workflow validation passes, and every fixture job plus all canonical source bytes/modes match the frozen consumer. An initial broader 193-test command also included the unchanged Docker effective-trust control; that control stopped at
docker infobecause the 1GiB address-space limit prevented Docker's Go runtime from creating a thread. That attempt remains runner-blocked. The affected 192-test suite then passed separately; no effective-trust PASS is claimed from the blocked attempt. Each of the six actual caller TLS controls is separately qualified above.Refs #297 and durable-workflow/sdk-php#418.