{"version":"2.1.232","anchor":"live-doc-collaboration-metadata-on-published-artifacts","canonical_anchor":"live-doc-collaboration-metadata-on-published-artifacts","heading":"Live-doc collaboration metadata on published artifacts","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/live-doc-collaboration-metadata-on-published-artifacts","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Live-doc collaboration metadata on published artifacts\n\nPublished artifacts can carry live-doc collaboration details when that module is present.\n\n**What**\n\nPublishing an artifact to a live doc can now attach a `liveDocCollab` field and the artifact kind to the result. This depends on a live-doc module that may not be present in a given run, in which case the field is omitted and publishing behaves as before.\n\n**Details**\n\n- A new publish error, `dual_spelling_ambiguous`, is reported when contract or capabilities are declared under two different spellings.\n- A timing log was added around the third-leg read, printed as `[liveEdit:timing] third-leg read`.\n\n**Evidence**\n\n`dual_spelling_ambiguous`\n\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}