Artifact publishing gained live-document branches that only run if an optional module is present.
Live-document publishing paths exist but reach for a module whose presence is not visible in the build.
What's wrong with this entry?
The artifact tool gained handling for live documents: its own permission description and summary, a classification marker, a refusal when a URL is supplied instead, and a creation path sent on publish. Every one of these reaches for the live-doc module optionally, so whether that module is present in this build is not visible from the code itself.
- All call sites are optional-chained, meaning they do nothing at all if the module is absent.
LIVE_DOC_DESCRIPTION
Strings lifted out of the shipped bundle, so the claim above can be checked against them.