[fix] open-core-m1: the drawer-mount check was asserting the pre-tab drawer

[AlexZ005]

Closes the last standing red in the roadmap-29 verification table. open-core-m1 has run 16/1 for about two months; the integrator A/B'd it against pristine 1.14.0, found it identical, and filed it for its own ticket. This is that ticket.

It is a test fault, not a product one. git diff -- src/ is empty.

What was wrong

The check PM: drawer section renders in the open info drawer was written at 4799994 (roadmap 14 PM, 2026-07-24), when ConnectInfoDrawer rendered {#if $drawerSlot}<CloudSlot …> inline in its single body — so the chevron showed the plugin's section immediately. The next day, 4b7b8cf ("one tabbed drawer (Info/Rooms/Toasts)") moved the cloud mount behind the Rooms tab. The suite was never updated, and it has been red for the entire life of the tabbed drawer.

Measured with a throwaway probe rather than inferred:

state	drawerTab	tabs	#connect-rooms-button	#cloud-drawer-section
inert, closed	info	–	no	no
plugin, chevron opened	info	Info/Rooms/Toasts	yes	no ← the failing read
plugin, Rooms shortcut	rooms	Info/Rooms/Toasts	yes	yes
plugin, Rooms tab	rooms	Info/Rooms/Toasts	yes	yes

Why the product stays untouched

The chevron opening on Info is deliberate — toggleInfo keeps the last tab, and the drawer's own job is connection and server info. The plugin's content already has a first-class way in: Connect grows #connect-rooms-button exactly when $drawerSlot is set, and openRooms opens the drawer on that tab. Auto-selecting Rooms on a plugin mount would hijack the info drawer for everyone running the cloud plugin.

What changed

• the check drives #connect-rooms-button — the way the app offers the mount — and asserts the section renders on the Rooms tab;
• new M1d: no Rooms affordance in the inert build, which is what stops the corrected check passing vacuously (that button exists only because a plugin mounted drawer content). 17 checks → 18; nothing was deleted;
• the e2e skill drops open-core-m1 from both dirty-baseline lists, records where the drawer mount now lives, and keeps the lesson: identical-on-base only rules out YOUR diff — when a red is pre-existing, spend the two minutes on when it started and what changed then.

Counterfactuals (product broken, restored byte-identically)

• removed <CloudSlot mount={$drawerSlot} /> from the Rooms tab → PM: drawer section renders on the drawer Rooms tab FAILS
• dropped $drawerSlot && from Connect's Rooms-button gate → M1d: no Rooms affordance in the inert build FAILS
• both together → exactly 2 FAILURES, no others; restored → 18/18

Gates

open-core-m1 16/1 → 18/18. Battery under the machine lock, ALL PASS: ai-presets · approval-timeout · connect-states · dial-metadata · join-result · net-handshake · open-core-m1 (7 suites, 203 checks, 399s). svelte-check 336/47 unchanged (identical by construction). vitest 178. npm run build green, server down.

Nothing owed on device — this touches no rendered behaviour.

🤖 Generated with Claude Code