Manifest: additive capabilities key (plan 04)

[ronaldtse]

Manifest: additive capabilities key (versions catalog plan 04)

The release manifest's per-runtime <stem>.manifest.json entries gain an additive capabilities array — display metadata owned by the factory, never a selector axis. The versions catalog renders it when present (solid chip) and keeps its dotted "derived" chip as the pre-key fallback.

What's in it

• scripts/upload_release.rb manifest_entry: entry[:capabilities] = ["jit"] when the package's version carries the jit flavor, [] otherwise — sourced from PythonVersion#jit? (the line grammar's owner; no second hand-written copy), additive like abi/image/dll before it.

Verification

This repo carries no spec suite for scripts/ (no spec/ directory), so the emitter is verified by inspection + the next release's published manifests — the versions-catalog PR (plan 04 step 3) curls the released assets and quotes them. Happy to add a spec suite if wanted.

Notes

• After this merges and a release publishes, tamatebako/versions collector fetches per-runtime manifests for latest rows (bounded: one request per line × triplet) and lets the key win over the derived chip.
• The ruby factory's twin PR: Manifest: additive capabilities key (plan 04) tebako-runtime-ruby#149.