A subagent publishing an Artifact no longer pops the frame open on you.
What's wrong with this entry?
Publishing an Artifact now opens its frame only when the main agent published with an interactive UI, or when the create earlier asked for a deferred open. A publish from a subagent no longer opens the frame on its own.
- A failed frame open is remembered in app state (
frameOpenFailedPath/frameOpenFailedSeen) and shown once, cleared on success. - The deferred-open record is cleared on account and conversation resets.
frameOpenFailedSeen
Strings lifted out of the shipped bundle, so the claim above can be checked against them.