Problem
The status matrix records each backend's published image_tag, whose -0.2.x_g<sha> suffix is the plugin commit. But which plugin version a vLLM line (0.20.2 / 0.24.0) actually uses across backends is not stored structurally — it must be reconstructed by diffing PyPI wheel lists against matrix suffixes by hand (2026-09-05: that comparison happened manually and was error-prone).
Two consequences:
- Recorded coverage is asymmetric. iluvatar 0.24.0 carries two different plugin tags (4.4.0 =
g84a4ca2, 4.5.0 = g07063fd); 0.20.2 4.5.0 = gc0c060a6, 4.4.0 = g587e2fe. The user model is one shared plugin head per line covering both corex backends.
- A record PR only writes
image_tag. The record step (record_app_image_tag.py) derives and writes the tag but does not also write plugin_fl_version as its own field, so the "this is the plugin this line ships" fact is only implicit in a tag suffix.
Desired
- Per-backend structured
plugin_fl_version field in packaging/vllm/status_matrix.vllm*.yaml, written by record_app_image_tag.py in the same pass that writes image_tag (image_tag suffix stops being the only carrier).
- Converge iluvatar to one shared plugin head per line when a shared wheel exists (the plugin wheel is shared between corex4.4.0 and corex4.5.0).
Notes
Not a blocker for the current 0.20.2 deliveries — filed separately so the fix is not mixed into delivery work.
Problem
The status matrix records each backend's published
image_tag, whose-0.2.x_g<sha>suffix is the plugin commit. But which plugin version a vLLM line (0.20.2 / 0.24.0) actually uses across backends is not stored structurally — it must be reconstructed by diffing PyPI wheel lists against matrix suffixes by hand (2026-09-05: that comparison happened manually and was error-prone).Two consequences:
g84a4ca2, 4.5.0 =g07063fd); 0.20.2 4.5.0 =gc0c060a6, 4.4.0 =g587e2fe. The user model is one shared plugin head per line covering both corex backends.image_tag. The record step (record_app_image_tag.py) derives and writes the tag but does not also writeplugin_fl_versionas its own field, so the "this is the plugin this line ships" fact is only implicit in a tag suffix.Desired
plugin_fl_versionfield inpackaging/vllm/status_matrix.vllm*.yaml, written byrecord_app_image_tag.pyin the same pass that writesimage_tag(image_tag suffix stops being the only carrier).Notes
Not a blocker for the current 0.20.2 deliveries — filed separately so the fix is not mixed into delivery work.