Rust #325: move the parity reference to the corrected published release (2.11.7) #863

Part of #325: move the Shared Server fixtures reference from published 2.11.5 to the corrected published release, 2.11.7, which carries the #861 fix (#862). Published 2.11.6 was surveyed below; it is not a target because of #861.

• Reference: Server 2.11.6, source d13ebdb5, Core 2.15.7. General's release record is Prepare Server 2.11.6 and Helm chart 0.3.6 release identity #856 (comment).
• Images:
  • index sha256:28e1ddeea655760e99748c48f2fa9bbecda37d3924864f6ee9011764144f2c2b;
  • amd64 sha256:c20c901eaa8dedfa04e5b89280f93b23a5e84e143410e3ceb63ff0881d701641;
  • arm64 sha256:f799cf5ca1b4276a1ac9293dd66e85c624cf91289a1b1b8086eeb10c3082a98a.

Local survey (October 29)

Published 2.11.6 amd64, SQLite with the maintenance loop running, every fixture in tests/Fixtures/ServerParity against the current expectations (main f249b00a):

• Pass unchanged: 70 of 75.
• bridge-adapters: update_again answers 500, a UNIQUE constraint on workflow_commands. This is a 2.11.6 regression, tracked in Published 2.11.6 answers a repeated bridge-adapter update with 500 #861. 2.11.5 passes in the same environment.
• waterline-import: read_project_export reports history_size_bytes: 4713, where the fixture expects 5431. This is the canonical history meter of Waterline v1 projection import has no event or history byte limit #770, published in Core 2.15.7.
• Not attributed to 2.11.6:
  • schedule-catalog (step statuses) fails the same way on 2.11.5 in this environment.
  • service-calls passed on 2.11.6 when run alone, after SQLite lock pressure blocked it in the full run.
• Not run locally: visibility-current-runs needs the published CLI artifact that CI provides.

Next

1. Wait for General's qualified 2.11.7 tuple (Security's Published 2.11.6 answers a repeated bridge-adapter update with 500 #861 hold requires the corrected release; no known-defect option).
2. Survey 2.11.7 the same way.
3. Align the native canonical history meter (rust-325-wip/canonical-history-bytes, e0ed32a6, Waterline v1 projection import has no event or history byte limit #770) and the waterline-import expectation together. The 2.11.6 difference (4713 against 5431) is that meter.
4. Add php-2.11.7.json and switch the reference sites (8 files name php-2.11.5).
5. Qualify with the full CI corpus, and record the result here and in Waterline v1 projection import has no event or history byte limit #770.