Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
Internal ChangesKind: in v2.1.269,
Internal ChangesSection of the release
Unclear What determines whether content is marked 'foreign', and what consuming that flag changes, is not stated.
What
Content schemas used for synced assets and comments, which already track fields like cowritten, typeLocked, and writerClass, gain a new optional boolean field called foreign. It's wired through the same serialization logic that handles those other fields.
Why
The finding doesn't state what marks content as 'foreign' or how that distinction is used, only that the field now exists and is threaded through alongside the existing metadata.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat determines whether content is marked 'foreign', and what consuming that flag changes, is not stated.
