Under the hood
Copying a type-locked artifact now goes through a dedicated access check instead of the generic one
What
The function that checks whether a user can access an artifact now takes a mode parameter, defaulting to "copy". When that mode is used on an artifact that is locked to a specific type, the check is now routed through a dedicated function instead of the general ownership/read check that other access requests use.
Why
This lets copy permission for type-locked artifacts be evaluated with its own dedicated logic, separate from ordinary read access.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The finding doesn't say what the dedicated check does differently from the generic one, or what a type-locked artifact is.