e2e: follow the provider words, folded landings and folded skills

[AbirAbbas]

make test-e2e-tui on dev 461a43fb6 (the 2026-09-29 pre-release pass, before dev moved to staging) passed 15 of 19. The four reds were the suite, not the product — each subtest was run alone before and after this change, and the product did what the manual says every time.

Subtest	What moved	Driver now
plain_launch_opens_connections_and_harnesses	/connect groups model sources under providers since #1513, not models	filters for the seeded account and requires its connected mark
a_nested_landing_asks_and_a_key_answers_it	the landing card folds to one row (#1607); one a answers it and records you took this as done	presses once, requires both tasks done on screen, waits for the receipt in the conversation
a_refused_landing_is_incomplete	same fold; the full run's blank launch (45 s, under load) did not recur in two isolated runs	presses n once, requires incomplete, waits for the receipt
foreign_skills_reach_the_conversation	the carried-skill line sits inside the folded activity (#1504, #1607); all three code words were in the answers	opens the ▸ worked disclosure and requires the skill line beside the matching answer

No product code or prompt change. One manual correction, and a placement for the owner to confirm: skills-a-turn-used.md said the skills · … line stays under the message, outside ▸ worked. #1627 deliberately changed that (countWork's carried-line exemption became "Skill-loading notes are retained work", and #1607's entry lists skills among what spilled outside live activity), while the same PR's #1504 entry and this page kept the old placement. The page now says what the binary does. If the old placement is the one wanted, it is a three-line restore in internal/tui3/workfold.go plus reverting this driver hunk and the page paragraph. Needles stay in internal/e2e/tuiwords_test.go, so the untagged gate still checks them against internal/tui3.

Proof: each subtest alone after the change: PASS (21.8 s, 20.7 s, 20.7 s, 99.2 s; skills ran both memory_on and memory_off). go test ./internal/e2e/ (untagged), go vet -tags e2e ./internal/e2e/, make test-laws, make pr-ready: green.

🤖 Generated with Claude Code