[rmcdaniel]

Part of #325. This moves the Shared Server fixtures' published PHP reference from 2.11.1 to Server 2.11.4 (Core 2.14.2):

• source ad3ac5fda0a30a58084b2d68569f2d91e23fabf3;
• linux/amd64 sha256:bee30cde…;
• linux/arm64 sha256:cc297aa7….

General and Security verified these artifacts (#802, server-325 chat 2846 and 2848).

1. Native follows Core 2.14 (7b5ada605)

• Repair-pass report: adds service_call_dispatch_candidates, service_call_dispatches_enqueued and service_call_dispatch_failures. Native runs a call's handler when it accepts the call, so it has no outbox and reports zeros.
• Service-call execute: wait_timeout_seconds is bounded at 60 (Update completion wait_timeout_seconds is caller-unbounded #775), not 86400.
• Handler metadata: names service_call_idempotency_key, which is null for a call dispatched when it is accepted.

2. poll_transport in task-queue views (a4c1de7af)

Published 2.11.3 reports WorkerPollDiagnostics::snapshot on every task-queue list and detail entry. Native records no early poll disconnects, so it reports {"status":"unavailable","retention_seconds":900,"last_disconnect":null}, as PHP does without its cache. It never claims no_recent_observation.

Native returns the ordinary JSON response to every poll, declining the opt-in progress transport. The contract allows this, because SDKs must accept both (#325 comment 6432802069).

3. The reference move (e5d2aeb15)

• tests/Fixtures/ServerParityBaselines/php-2.11.4.json is the new baseline. The SDK, CLI, Waterline and sample-app pins are unchanged.

• All 40 reference pins name it: image pulls, the PHP runner image and the script defaults.

• The takeover cohorts are unchanged: each names its own source release and layout (php2111 still takes over published 2.11.1 as php-2.11.1).

• The 2.11.4 API route table equals 2.11.1's apart from the poll-progress middleware, so the route inventory stands.

• repair-pass and service-calls expect the Core 2.14 answers above.

• Boundary for Workflow #931: service-calls no longer repeats an idempotency key from another caller namespace.

  • Published 2.11.1 created a separate call for that caller.
  • 2.11.3 and 2.11.4 replay the first call and rebind its handler identity.
  • The prepared correction refuses the foreign caller.

  Nothing else in the fixture referred to that call, and the fixture's contract says why. It now has 90 requests. The step returns when a release carries the correction; until then native keeps 2.11.1's separate call.

Fixes after the first runs

• 912f49a6d: two tests the move had left on 2.11.1.
  • The image-pull unit test pins the reference as a regex (php-2\.11\.1); it now names 2.11.4. The comparator unit batch passes 2417/2417.
  • The update-wait ceiling execution test: a 61-second wait is now a 422 validation failure before routing, as 2.11.3 answers, and a 60-second wait still reaches the unserved handler kind.
• 0a64b6ede: the move had also changed the php2111 takeover cohort's expected layout to php-2.11.3, and every cohorts part failed its table count. Those six lines are not reference pins and are restored; the workflow no longer changes any expected layout.

4. Docs (2bf5fdfee)

A checkpoint (docs/rust-server-port-checkpoints/2026-10-27-reference-2114.md) and the refreshed current state.

Checks run

• Full selection against 2.11.4: CI's fixture selection (the corpus without update-validation) recorded on SQLite against published 2.11.4. Before the boundary, only service-calls differed: the replayed-from-another-caller step and the three steps that follow from it.
• After the boundary: repair-pass, service-calls and storage-test pass against both 2.11.4 and native from this branch, and the two records compare equal.
• Contract test: the service-calls contract test passes 22/22.
• Native tests: the full SQLite library (338) and execution (560) suites pass.
• Policies: both organization policies pass.

5. SQLite qualification boundary for service-calls (7f6564f53, added after queue attempts)

Two of this PR's three merge-queue groups failed on the published 2.11.4 reference, not on native: PHP answered service-calls held[0] with 429 on the first call to a one-in-flight operation (runs 40463072450 and 40466604924), under SQLite writer contention from its own maintenance loop (Server #796; evidence in #796 comment 6436288360). The SQLite job now records service-calls apart from its main corpus with PHP's maintenance loop stopped, the boundary #723 already uses for update-validation. That includes #754's single fresh-prefix retry after database is locked. Fixture assertions are unchanged; the MySQL and PostgreSQL jobs keep service-calls in their main corpus with their loops running. Remove the boundary when the reference carries the #796 fix. Its unit tests pass 14/14 in the 2.11.4 image, and both organization policies pass.

CI runs the full selection on all four databases.

🤖 Generated with Claude Code

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
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]

Merged through the merge queue at 2026-10-27T08:23:34Z.

• Main is now b99cb41626a4234d00cecf8e8cc051f8881c00bf, with parents 8ef937273 (main, Cache source-free PHP CI tools from qualified main runs #808) and 7f6564f53 (this PR's tested head).
• Tree 0653ac4f equals git merge-tree --write-tree 8ef937273 7f6564f53.
• Queue attempts: this was the fourth.
  • Attempts 2 and 3 were dropped when published PHP 2.11.4 answered service-calls held[0] with 429 on SQLite (Investigate first-call PHP service rate rejection during SQLite maintenance #796).
  • 7f6564f53 added the SQLite boundary that records service-calls with PHP's maintenance loop stopped. The PR CI and the queue group both passed at that head, including the SQLite corpus part.
• Parity reference for Shared Server fixtures is now published 2.11.4 (Core 2.14.2).
• Still set aside until a release carries the fixes:
  • the service-calls "replay other caller" step (Workflow #931);
  • the SQLite isolation of service-calls (Investigate first-call PHP service rate rejection during SQLite maintenance #796).