Even worse in this case: https://it.wikipedia.org/w/index.php?title=Carmine_Buschini&action=edit&redlink=1 tells me, I'm not allowed to create that page (https://it.wikipedia.org/w/index.php?title=Carmine_Buschini&action=info confirms this), while VE let's me start editing (and probably will fail when I try to save).

Another example on enwiki - going to a page with editnotices (e.g. https://en.wikipedia.org/w/index.php?title=Abortion&action=edit) using the source editor works fine - if switching to VE the notices are lost, manually looking for them in the triangle button says no notices. (Firefox, monobook)

The notices seem to only show up expanded when opening it initially, usually - otherwise they're always collapsed, and users are not likely to expand them to look at them. In the case of editnotices and the like, the whole point is for them to be seen and in many cases used, so hiding them away in a typically closed thing, which cannot be kept around while doing anything else on the page, is perhaps not the best approach.

The referenced Carmine_Buschini page now displays identically in action=edit and veaction=edit, because of a side-effect of @matmarex's recent ae8b0a1. The page isn't editable, so the #ca-edit element (the edit tab) isn't shown, so VE refuses to load.

...the "your skin isn't supported" message it leaves in the console is admittedly rather misleading in this case.

@Jdforrester-WMF: Should we be allowing veaction=edit to forcibly load VE in this case, with the associated edit notices, or is the current behavior correct?

In T153118#3210532, @DLynch wrote:

The referenced Carmine_Buschini page now displays identically in action=edit and veaction=edit, because of a side-effect of @matmarex's recent ae8b0a1. The page isn't editable, so the #ca-edit element (the edit tab) isn't shown, so VE refuses to load.

...the "your skin isn't supported" message it leaves in the console is admittedly rather misleading in this case.

That's T162411: "Your skin is incompatible with VisualEditor" warning on protected pages.

@Jdforrester-WMF: Should we be allowing veaction=edit to forcibly load VE in this case, with the associated edit notices, or is the current behavior correct?

That's T53547: VisualEditor: Provide a "view VE" mode / disable editing for protected pages.

Because my account has +sysadmin, for me navigating from https://it.wikipedia.org/w/index.php?title=Carmine_Buschini read mode to "create" or going straight to https://it.wikipedia.org/w/index.php?title=Carmine_Buschini&veaction=edit I get:

The second edit notice is correct, but isn't populated for some reason.

(Ignore the warning background telling me I'm using high-powered account on a production wiki.)

If I switch to the old wikitext editor and back again I get an empty set of notices:

… which was just fixed in T162812: Edit intro is not shown when a user switches from wikitext editor to visualeditor.

Consequently, post-Thursday the only outstanding issue that isn't already in another task is the titleprotectedwarning edit notice getting populated?

This recently came up again on the administrator's noticeboard on dewiki; the recreate-message appears after the editnotices and the newarticletext that is quite long (https://de.wikipedia.org/wiki/MediaWiki:Newarticletext-0) so in the end will only be shown after scrolling down which most users won't do. It should at least be moved to the top of the flyout as it is actually a warning rather than just information messages like newarticletext.