Consent handling for artifacts now distinguishes content co-written by a non-owner from content whose files or assets derive from an artifact type the user didn't author. Reading such content throws a distinct refusal unless consent was granted, with messages like "a co-writer has published to this artifact" and "[ownership: yours, co-written: a non-owner has also published to it]".
Artifact co-writer / type-derived content consent gating
Artifacts now distinguish co-written content from type-derived content for consent purposes.
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
ImprovementsKind: in v2.1.260,
ImprovementsSection of the release