[CI] Version both baseline files and split conformance badges per spec (#459)

- Rename conformance-baseline.yml to conformance-baseline-2025-11-25.yml
  so both baseline files carry their spec revision symmetrically, and
  bring conformance-server/conformance-client up to the same rigor
  (--suite all, pinned CONFORMANCE, baseline check) as the draft targets
- score.php now takes a required spec-version and writes
  <suite>-conformance-<spec-version>.json, so 2025-11-25 and 2026-07-28
  each get their own badge instead of only the dated one
- conformance-weekly.yaml generates and publishes badges for both
  matrix entries instead of gating on 2025-11-25 only, and drops the
  now-stale unversioned badge files from the badges branch
- README shows all four badges alongside the existing packagist/CI/PHP
  version/license row
- Trimmed workflow comments to the minimum needed
This commit is contained in:
Christopher Hertel 2026-08-18 23:42:36 +02:00 • committed by GitHub
commit 78a8926f17
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -1,8 +1,8 @@
# Expected conformance failures for spec revision 2026-07-28.
#
# Separate from conformance-baseline.yml because the two revisions exercise
# different lifecycles against different endpoints: the dated baseline covers
# the handshake era served at /, this one covers the modern (SEP-2575) era
# Separate from conformance-baseline-2025-11-25.yml because the two revisions
# exercise different lifecycles against different endpoints: the other file
# covers the handshake era served at /, this one the modern (SEP-2575) era
# served at /stateless.
#
# Entries are per-check (scenario:check-id) rather than whole scenarios, so a
@ -11,6 +11,7 @@
#
# Run with:
# make conformance-draft-server
# make conformance-draft-client
server:
# --- Pre-existing, not lifecycle-specific ----------------------------------