Context: We hold a Trados Studio Professional Named User subscription. We run a standalone .NET Framework 4.8 application using the Project Automation API (Scan / Convert / Analyze / Pretranslate) on Windows 11 Pro. We are currently on Studio 2024 SR1 CU4 and planning the migration to Studio 2026 (19.0.0.3043), whose release notes add API licensing support for subscriptions. Questions:

1. In Studio 2026, does a standalone Project Automation API app licensed via a Named User subscription require an active cloud sign-in / internet connection at runtime? Does it read subscription.sdllic, or must Studio have signed in previously on that machine?

2. Does the running standalone process consume the Named User seat and block concurrent use of the Studio GUI by the same user? Does the documented 30-minute post-exit license block apply to the Named User seat?

3. Can Studio 2024 SR1 CU4 and Studio 2026 be activated simultaneously on the same machine under a Named User subscription (not perpetual/single-user)? Does the KB "How to license Trados Studio 2024 with a Trados Studio 2026 single-user license activation" apply to subscriptions?

4. Do you offer an extension/reset of the Studio 2024 30-day trial for customers with an active subscription during a migration?

5. What is the end of engineering support (patches/CUs) for Studio 2024 SR1 now that 2026 is GA?

6. Is a CU1 for Studio 2026 planned, and in what timeframe? Do you recommend 19.0.0.3043 for regulated production use, or waiting for CU1?

7. Can you confirm there will be NO "Studio 2024 SR2 / 18.2.x" installer with the subscription-licensing fix, and that the only vehicle for it is Studio 2026?

8. Current list price of Studio 2026 Professional for 2 seats (perpetual if still available, and network/CAL).

9. RDP scenario: is running Studio licensed via a Named User subscription over RDP to a Windows 11 Pro workstation (client OS, single interactive session, no RDS role installed) permitted? Your documentation prohibits the Terminal/RDS role on server operating systems; we need written confirmation for this Windows 11 Pro client scenario.

Thank you — answers to 1–3 are blocking a migration scheduled before mid-August.