Publishing an artifact can join its shared room, or report why it didn't.
Skip reasons like not_declared appear in publish output.
What's wrong with this entry?
One routine now decides whether your session joins an artifact's shared room after you publish it, reporting a reason such as not_declared in the publish output when it does not.
- It reads the artifact's declared capabilities, then checks the consent markers recorded when the artifact was created.
- Returns immediately unless the room module is present and the room capability check passes; that module is absent here.
not_declared
Strings lifted out of the shipped bundle, so the claim above can be checked against them.