What
When a published artifact does not locally look like it has a comment room but was created from a type with the room setting on, publish now asks the server for the artifact's capabilities before deciding, instead of trusting only local knowledge.
Details
- If that read fails or comes back empty, the reported room status is the existing skip reason, or the new value
unreadwhen there is none. - Still inside the existing room consent and schema checks; no new flag.
Evidence
zt.artifactRoomSkipReason(ee) ?? "unread"
Strings lifted out of the shipped bundle, so the claim above can be checked against them.