[akashdhake]

Work item: W-24501804
https://gus.lightning.force.com/lightning/r/ADM_Work__c/a07EE00002nLhYnYAK/view

Stacked on #1070 (promote the command to GA). Until #1070 merges, this PR also shows its commit. This PR's own changes are commits 9721845 and 06f363a. I'll rebase once #1070 lands.

What and why

After sf template generate lightning-out finishes, three things are missing or unclear in the output. All wording was checked against Salesforce Core (266-main, and 264 for the Setup labels).

1. CLWR: link the app to a site. --runtime help said only "extra site-deployment step". A Metadata API deploy creates no site link, and the Lightning Out 2.0 App Manager UI creates it when you save on the "Linked Communities Site" tab. The CLWR runtime finds an app's components through that link. The command now says so.
2. Org-wide settings. The generated MyDomain and Security settings set isFirstPartyCookieUseRequired=false and enableOauthCorsPolicy=true for the whole org. Nothing in the output said that. A warning now does.
3. App ID. The old line didn't say where to find the App ID or what to do with it. It now points to Lightning Out 2.0 App Manager and the app-id attribute on <lightning-out-application>. For LWR_CORE, app-id is what adds the app's host domains to the allowed frame ancestors (SFDCContentSecurityPolicyFactory).

Changes

• --runtime: the summary is now one line ("Runtime the app targets: LWR_CORE or CLWR."). The detail moved to a new flags.runtime.description.
• New success.clwr-site: printed for CLWR runs only, right after the deploy command and before the App ID line.
• New warning.org-settings: printed as a warning for all runs, before the deploy command it refers to. Because it is a warning, it also appears in the warnings array of --json output. That is deliberate: the org-wide effect applies to automated runs too.
• success.app-id is reworded.
• Tests: run() is now exercised with the generator stubbed. They check that the CLWR guidance is shown only for CLWR, that the org-wide warning appears for every runtime, and the runtime summary/description split. I confirmed the LWR_CORE test fails if the CLWR gate is removed.

Testing

• Unit tests: 33 passing in the lightning-out file.
• yarn test (wireit): passes.
• yarn lint: 0 errors. 1 existing warning (sf-plugin/get-connection-with-version in digital-experience/site.ts), not from this change.
• --help output checked for the new --runtime text.
• Not run: the NUTs, and an end-to-end run against an org.

For copy review

Copy review requested: please review the wording in messages/lightningOut.md. Points I'd like a second look at:

• The Setup navigation sentence in success.clwr-site.
• The UI label names: "Lightning Out 2.0 App Manager", "Linked Communities Site", "Complete Deployment in Experience Builder".
• The org-settings warning, which uses the metadata field names.
• Naming: all new text says "Lightning Out 2.0", per the PM guidance to keep "2.0" until the beta is sunset.

Known gaps, not in this PR

• success.frontdoor applies only to authenticated CLWR. Guest CLWR uses org-url and site-prefix.
• --host-domains has no effect on how a CLWR app is framed.
• "Guest and authenticated users" for CLWR matches the Setup UI's runtime description. A 9/30 Slack answer said guest access isn't supported on CLWR yet, so the wording needs a final check with the PM.

[akashdhake]

Folded into #1070 so there is a single PR for W-24501804. All commits from this branch are now in #1070.