Operator cross-organization task walkthrough dead ends

Found while walking the console as the operator over Org B (Task 9009). Each is a 1-2 sentence requirement: 1. New session (Slots page ⋯ New session) on another org's folder/MicroVM project is offered disabled with no working path: the Slots page is operator-only, so acting as the org lands on /no-access. Let the operator open the session in that org in one step (as slot declaration now does), or route it to a surface the org's seat can reach. 2. Add node with an org filter on one other org (e.g. `?orgs=org-b`) still defaults the Organization picker to the operator's own org; preselect the filtered org. 3. Another org's waiting task shows two stacked Act-as banners (the task-level "only Rename and Delete here" banner and the Answer panel's "Answer as <org>"); show one. 4. Duplicate is hidden on another org's task (`useTaskDetailActions.tsx`); offer it with Act as, as Delete and New task do. 5. Settings › Connections "Add connection" with an org filter on another org opens the dialog for the operator's own org; pass the filtered org so the connection lands where the operator is looking. Out of scope: changing who may do what (authz stays). Done means: each item has a vitest or api test, and a dev walkthrough as operator over another org shows each path working in one step or naming the switch up front (desktop + 390px screenshots).

Fixed all 5 cross-org dead ends for the operator (Slots New session → chat as the org, Add node/Add connection follow the org filter, one banner on a waiting task, Duplicate as the org). Vitest added per item; quick gate green; review lanes passed; desktop and 390px checked on the local stack. PR #6659 queued to the merge lane. Memory: none applied.