Type-locked artifacts refuse edits to template files and refuse publishing index.html, all gated by two artifact-type flags that default off.
What
An artifact created from a type carries a lock recording which files belong to the type. Claude is told those files cannot be edited here, and publishing an index.html to such an artifact is refused because the page comes from the type. None of it is reachable without the two artifact-type flags, both of which default off.
Details
- The lock is carried through artifact read-back and share status, and the read path stops taking the plain-owner fast path for a locked artifact.
- The tool description states verbatim that a type-owned file belongs to the artifact's type and can't be changed here.
- Whether any of this is visible is frozen once per session at schema-build time.
- Creating a new artifact from a type is additionally blocked inside remote sessions.
- None of these symbols exist in v2.1.235.
Evidence
this file belongs to the artifact's type and can't be changed here
Strings lifted out of the shipped bundle, so the claim above can be checked against them.