What problem does this address?

#72044 was merged (with the feature behind an experiment flag still), but there might still be some follow-ups to work on. Lets record any future tasks here.

What is your proposed solution?

Something that might need further improvement is the test on the button used to edit patterns. In the PR 'Unlock pattern' / 'Lock pattern' was shipped.

There were also several ideas from this comment - #72044 (comment) (cc: @fcoveram @jasmussen)

Here's a video taken from that comment:

And the changes involved:

• The editor’s header is the affordance area for exiting the pattern editing context. The feature is already there, and if it surfaces more entity properties, it would convey better what users are editing.
• Since “not synced” patterns now have a friction layer before tweaking the internal blocks, it should be spotted easily in the list view to avoid frustrations related to “why I can edit one block, but not this one”. For that, I think we could include the color icon in the list item and an idicator in the child blocks to show that they differ of other regular blocks.
• In addition to Jay’s point about the interaction for editing a pattern, I think that editing a sync pattern here should be the same as editing it in focused edit mode. In that vein, going to Style > Patterns and selecting a pattern to edit it should have the same editor’s header but without the back action.

Some future possibilities were also mentioned:

Overall, I think the editor’s header could be simpler and show the nested entities concept through a breadcrumb. This idea needs more polishing, but the idea can be expanded to nest different entities.