Live paths, born-live markers and a live-files publish flag run end to end but the extra schema fields require three simultaneous conditions.
What
Publishing an Artifact gains a live-paths concept throughout: publish results carry live paths and a born-live marker, share status stores the paths and when they were issued, and the publish request sends a live-files flag that is also passed to publish telemetry. The visible part is extra top-level fields spliced into the Artifact tool's input schema, and that only happens when three conditions all hold.
Details
- Schema fields appear only when the live-edit gate is open, the files capability is enabled, and a live-paths predicate returns true.
- That predicate lives on a module loaded lazily from a separate chunk, absent from the main bundle, so what it defaults to is decided outside this code.
- The combined boolean is also stored as a latch on the durable artifact state. It is written at exactly one place and read nowhere in the build, so it currently affects nothing.
- None of these fields exist in 2.1.241.
Evidence
livePathsGateLatch
Strings lifted out of the shipped bundle, so the claim above can be checked against them.