Publishing an artifact re-checks capabilities fresh when frozen artifact types are enabled.
What's wrong with this entry?
Publishing an artifact now forces a fresh capability lookup, instead of reusing a cached one, when the request declares capabilities and frozen artifact types are enabled for a non-type publish. Fetched values are only adopted where none were supplied.
- The frozen-artifact-types state is computed when the schema is built; this branch runs only when its types flag is on.
- Publish also records the artifact's slug before waiting on share status, rather than after.
frozenArtifactTypes
Strings lifted out of the shipped bundle, so the claim above can be checked against them.