@salesforce/afv-skills 1.50.0 → 1.52.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@salesforce/afv-skills",
-  "version": "1.50.0",
+  "version": "1.52.0",
   "description": "Salesforce skills for Agentforce Vibes",
   "license": "CC-BY-NC-4.0",
   "files": [

package/skills/experience-ui-bundle-deploy/SKILL.md

@@ -1,8 +1,8 @@
 ---
 name: experience-ui-bundle-deploy
-description: "MUST activate when the project has a uiBundles/*/src/ directory and the task involves deploying to an org or post-deploy org setup. Deploys a UI bundle app and runs ordered setup: org auth, build, metadata deploy, permission-set and role assignment, Experience Cloud self-registration, social login / SSO / IDP linking (Auth Providers + SAML SSO configs on a React site), seed-data import, and GraphQL schema fetch + codegen. Trigger signals: *.network-meta.xml, org-setup.config.json (with a socialLogin block), data-plan.json, sfdx-project.json, or mentions of deploy, org setup, or social login / SSO / IDP linking on an Experience site. DO NOT TRIGGER when: creating a new UI bundle project (use experience-ui-bundle-project-generate); styling pages without deploying (use experience-ui-bundle-frontend-generate); adding a feature such as auth, search, or file upload without deploying (use the matching experience-ui-bundle-*-generate skill); configuring MFA permission sets (use experience-ui-bundle-mfa-configure)."
+description: "MUST activate when the project has a uiBundles/*/src/ directory and the task involves deploying to an org or post-deploy org setup. Deploys a UI bundle app and runs ordered setup: org auth, build, metadata deploy, permission-set and role assignment, Experience Cloud self-registration, social login / SSO / IDP linking (Auth Providers + SAML on a React site), site logout URL, seed-data import, and GraphQL schema fetch + codegen. Trigger signals: *.network-meta.xml, org-setup.config.json (socialLogin/logoutUrl), data-plan.json, sfdx-project.json, or mentions of deploy, org setup, social login/SSO, or logout URL on an Experience site. DO NOT TRIGGER when: creating a new UI bundle project (use experience-ui-bundle-project-generate); styling pages without deploying (use experience-ui-bundle-frontend-generate); adding a feature such as auth, search, or file upload without deploying (use the matching experience-ui-bundle-*-generate skill); configuring MFA permission sets (use experience-ui-bundle-mfa-configure)."
 metadata:
-  version: "1.2"
+  version: "1.3"
   domains: ["Experience", "Developer Experience"]
   relatedSkills:
     - "experience-ui-bundle-frontend-generate"
@@ -112,6 +112,46 @@ of this flow.
 Timeout 180s. Must complete before permission assignment and schema fetch —
 objects, fields, and permission sets appear in the org only after deploy.
 
+## Step 3b — Set the site logout URL (config-gated)
+
+Run only when `org-setup.config.json` has a top-level `logoutUrl`. If absent,
+no-op cleanly and say so. **Non-destructive and idempotent** — no ask needed.
+
+Runs **here, after the deploy** (not folded into it) because the platform rejects
+a relative logout URL (*"The logout page URL must be an absolute URL."*), and a
+shipped site-relative path (e.g. `/propertyrentalapp/`) is resolved to absolute
+against the site's Experience Cloud origin — which only exists once the site is
+deployed.
+
+Why it matters: a site with no `<logoutUrl>` sends a logging-out member to the
+**org default-site login page** — in a multi-site org that's a *different*
+community, so Sign Out lands on the wrong site's login page. Setting it steers
+logout back to this site (reload as Guest).
+
+Steps:
+
+1. **Read** `logoutUrl` from config; absent → skip.
+2. **Derive the site** — `scripts/derive-site-name.sh` (single `*.network-meta.xml`;
+   skip if zero/ambiguous).
+3. **Resolve, set, and deploy — one command.** Invoke the helper, which resolves
+   the value to an absolute URL (site-relative → matched against the community
+   `siteUrl` **path**, never guessing), writes `<logoutUrl>` idempotently in the
+   canonical position, and deploys only that file:
+
+   ```bash
+   node scripts/set-logout-url.mjs \
+     --logout-url "<logoutUrl from config>" \
+     --network-file <sourceRoot>/networks/<site>.network-meta.xml \
+     --target-org <org> --site <site> --deploy
+   ```
+
+**Best-effort:** the helper exits **0** on success or already-set, and **3** on a
+recoverable skip (network file missing, origin unresolvable, XML-special char, or
+deploy failure). Treat **exit 3 as a loud skip, not a setup failure** — continue
+the rest of setup and tell the user to set the logout URL manually in the site's
+Administration settings. Usage, exit-code contract, and port-provenance:
+`references/logout-url.md`.
+
 ## Step 4 — Assign permission sets
 
 Discover permission sets under `<packageDir>/main/default/permissionsets/`. If
@@ -305,6 +345,7 @@ developer action, not part of setup; if the user asks to preview the site, see
 1. Authenticate org
 2. Build UI bundles (pre-deploy)
 3. Deploy metadata (deploy-license gate if self-reg configured)
+3b. Set the site logout URL (if `logoutUrl` configured — post-deploy, idempotent, best-effort)
 4. Assign permission sets (config-driven assignee)
 5. Assign role (if configured)
 6. Enable self-registration (if configured — ask first)

package/skills/experience-ui-bundle-deploy/references/config-scaffold.md

@@ -35,7 +35,8 @@ Every top-level key is optional; each object is strict (no extra keys).
                         "accountName": "<display name>" },
   "socialLogin": { "communityMemberProfile": "<Profile name>",
                    "authProviderNames": ["<DeveloperName>", "..."],
-                   "communityUserPermset": "<PermissionSet API name>" }
+                   "communityUserPermset": "<PermissionSet API name>" },
+  "logoutUrl": "/<site-path>/ or https://<absolute-url>"
 }
 ```
 
@@ -60,6 +61,14 @@ Every top-level key is optional; each object is strict (no extra keys).
   `selfRegistration`, there is **no `siteName`** — the site is derived from the
   single `networks/<siteName>.network-meta.xml`. Full step detail:
   `references/social-login.md`.
+- **`logoutUrl`** (optional) drives step 3b. A **site-relative path** (e.g.
+  `/propertyrentalapp/`, recommended — domain-independent) or an absolute
+  `http(s)` URL. Setup resolves a relative value to the absolute URL the platform
+  requires (against the site's Experience Cloud origin) and writes it to the
+  site's `<logoutUrl>` Network metadata after deploy, so Sign Out returns members
+  to *this* site instead of the org default site. No `siteName` — the site is
+  derived from the single `networks/<siteName>.network-meta.xml`. Full step
+  detail: `references/logout-url.md`.
 
 ## Scaffolding flow (permset folder present, config missing)
 
@@ -68,8 +77,12 @@ Every top-level key is optional; each object is strict (no extra keys).
 2. **Ask the user, per permset, who to assign it to** — `currentUser`,
    `guestUser`, or `skip`. Default a whole-set answer to `currentUser` (not
    `skip`) since the folder exists on purpose; only use `guestUser` for permsets
-   meant for the site's guest user. Also ask whether they want a `role` and/or
-   `selfRegistration` block while you're writing the file (both optional).
+   meant for the site's guest user. Also ask whether they want a `role`,
+   `selfRegistration`, and/or `logoutUrl` block while you're writing the file (all
+   optional). For `logoutUrl`, phrase it as "point Sign Out back to this site?" —
+   if yes, default the value to the site-relative path `/<site-path>/` (step 3b
+   resolves it to absolute post-deploy). Skipping it leaves logout on the org
+   default site (see the `logoutUrl` note above).
 3. **Offer two equivalent paths** — let the user pick:
    - **Write the file**: copy `assets/org-setup.config.template.json` to
      `org-setup.config.json` at the project root and fill in the answers. This is

package/skills/experience-ui-bundle-deploy/references/logout-url.md

@@ -0,0 +1,97 @@
+# Logout URL — steer Sign Out back to this site
+
+Detail for the **logoutUrl** step (SKILL.md step 3b). The step is executed by the
+deterministic helper `scripts/set-logout-url.mjs` (a faithful port of the
+reference `org-setup.mjs` logout-URL logic); this file covers **why** it exists
+and **how** to run it, not a re-specification of the algorithm.
+
+Source of truth for the behavior: reference `org-setup.mjs` `ensureLogoutUrl`
+(1103-1169) and the `main()` logout-URL step (2137-2148); the pure resolution
+helpers in `org-setup-url.mjs` (`isAbsoluteLogoutUrl`, `firstPathSegment`,
+`pickCommunityBaseUrl`, `resolveLogoutUrl`) and the XML helpers in
+`org-setup-xml.mjs` (`assertSafeLogoutUrl`, `setLogoutUrl`) — all reproduced in
+`scripts/set-logout-url.mjs`. Config schema: `org-setup-config-schema.mjs`
+(93, `logoutUrl: z.string().min(1).optional()`).
+
+Provenance: this step ports the "logout redirects to the login page of a
+different site" fix, added to `org-setup.mjs` but not previously reflected in this
+skill.
+
+Run this step **only** when a top-level `logoutUrl` is set in
+`org-setup.config.json`. If it is absent, the step is a clean no-op — say so.
+Unlike self-registration and data import, it is **non-destructive and
+idempotent**, so it does **not** require asking first.
+
+## Why it matters
+
+An Experience Cloud site with no `<logoutUrl>` on its Network sends a logging-out
+member to the **org default-site login page**. In an org hosting more than one
+Experience/CLWR site, that default is a *different* community — so Sign Out drops
+the user on the wrong site's login page. Setting `<logoutUrl>` to this site's own
+URL steers logout back here (the user reloads as Guest on the same site).
+
+## Why it runs AFTER deploy (step 3b, not folded into deploy)
+
+The platform **rejects a relative logout URL** at deploy time: *"The logout page
+URL must be an absolute URL."* But a shipped template must stay
+domain-independent, so apps ship a **site-relative** path (e.g.
+`"logoutUrl": "/propertyrentalapp/"`) that is valid on every org they deploy to.
+Resolving that to the absolute URL the platform requires needs the site's
+Experience Cloud **origin**, which is only discoverable (via the Connect
+communities API) once the site exists — i.e. after the main deploy. An
+already-absolute config value (`http(s)://…`) is used as-is, with no lookup.
+
+## How to run
+
+```bash
+node scripts/set-logout-url.mjs \
+  --logout-url "<logoutUrl from org-setup.config.json>" \
+  --network-file <sourceRoot>/networks/<site>.network-meta.xml \
+  --target-org <org> \
+  --site <site> \
+  --deploy
+```
+
+Derive `<site>` first with `scripts/derive-site-name.sh` (it prints the base name
+of the single `*.network-meta.xml`, or exits non-zero when zero or more than one
+exist — an ambiguous site is skipped, never guessed). Omit `--deploy` to resolve
+and write the file **without** deploying (e.g. to inspect the change first).
+
+### What the helper does (so you don't re-derive it)
+
+- **Resolves** the config value to an absolute URL: already-absolute → used
+  verbatim; site-relative → its origin is matched from the org's communities
+  (`/connect/communities`, at the org's current API version), **path-first** then by site name, and it
+  refuses to fall back to an arbitrary community (resolving against the wrong
+  origin would silently produce a valid-but-wrong URL).
+- **Writes** `<logoutUrl>` into the network metadata idempotently — replaces an
+  existing value in place, or inserts a new node in the canonical alphabetical
+  position; an already-correct value is a byte-for-byte no-op (no deploy).
+- **Rejects** a URL containing an XML-special character (`& < > " '`) rather than
+  escaping it.
+- **Deploys** only the one network file (with `--deploy`).
+
+### Exit-code contract (best-effort)
+
+| Exit | Meaning | What the step should do |
+|------|---------|-------------------------|
+| `0` | Applied (changed), already-correct (unchanged), or deployed | Report success; continue. |
+| `3` | **Recoverable skip** — network file missing, origin unresolvable, XML-special char, or deploy failed | **Do not treat as a setup failure.** Continue the rest of setup; tell the user to set the logout URL manually. |
+| `1` | Usage / argument error | Fix the invocation. |
+
+On a skip, tell the user to **set the logout URL manually in the site's
+Administration settings** (Setup → Digital Experiences → the site →
+Administration → Login & Registration → Logout URL).
+
+## Config shape
+
+```json
+{ "logoutUrl": "/propertyrentalapp/" }
+```
+
+- Top-level key (a sibling of `permsetAssignments` / `socialLogin`), optional.
+- A **site-relative path** (recommended — domain-independent) or an absolute
+  `http(s)` URL. A relative value is resolved to absolute at deploy time; an
+  absolute value is used as-is.
+- Like `selfRegistration` / `socialLogin`, there is **no `siteName`** — the site
+  is derived from the single `networks/<site>.network-meta.xml`.

package/skills/experience-ui-bundle-deploy/scripts/set-logout-url.mjs

@@ -0,0 +1,304 @@
+#!/usr/bin/env node
+// Resolve + set the Experience Cloud site logout URL (deploy step 3b).
+//
+// Deterministic helper for the "site logout URL" step: it resolves the shipped
+// (site-relative or absolute) logoutUrl config value to the ABSOLUTE URL the
+// platform requires, writes it idempotently into the site's network metadata,
+// and (optionally) deploys just that file. The SKILL.md step invokes this
+// instead of re-deriving the algorithm in prose. Faithful port of the reference
+// org-setup.mjs helpers (org-setup-url.mjs + org-setup-xml.mjs).
+//
+// Why absolute + post-deploy: the platform rejects a relative logout URL at
+// deploy time ("The logout page URL must be an absolute URL."), and a shipped
+// site-relative path is resolved against the site's Experience Cloud origin,
+// which only exists once the site is deployed.
+//
+// Usage:
+//   node scripts/set-logout-url.mjs \
+//     --logout-url "/myapp/" \
+//     --network-file <sourceRoot>/networks/<site>.network-meta.xml \
+//     --target-org <org> \
+//     [--site <siteName>] [--deploy]
+//
+// Exit codes:
+//   0  applied (changed), already-correct (unchanged), or deployed
+//   3  best-effort SKIP (file missing / origin unresolvable / XML-special char /
+//      deploy failure) — NOT a setup failure; the caller logs loudly and continues
+//   1  usage / argument error
+//
+// A skip (exit 3) means: tell the user to set the logout URL manually in the
+// site's Administration settings (Setup -> Digital Experiences -> the site ->
+// Administration -> Login & Registration -> Logout URL).
+
+import { readFileSync, writeFileSync, existsSync } from 'node:fs';
+import { execFileSync } from 'node:child_process';
+
+// Connect "communities" REST resource. Its API version is resolved from the org
+// at runtime (see resolveApiVersion) so it never goes stale as versions
+// increment; this pinned floor — the version used by the reference org-setup.mjs
+// port — is the fallback used only when that lookup fails. This step reads just
+// `siteUrl`/`name`, whose shape is stable across versions, so the exact version
+// is not load-bearing.
+const FALLBACK_API_VERSION = 'v62.0';
+const XML_SPECIAL_CHARS = /[&<>"']/;
+
+// ---- argument parsing -------------------------------------------------------
+
+function parseArgs(argv) {
+  const args = { deploy: false };
+  for (let i = 0; i < argv.length; i += 1) {
+    const a = argv[i];
+    switch (a) {
+      case '--logout-url': args.logoutUrl = argv[++i]; break;
+      case '--network-file': args.networkFile = argv[++i]; break;
+      case '--target-org': args.targetOrg = argv[++i]; break;
+      case '--site': args.site = argv[++i]; break;
+      case '--deploy': args.deploy = true; break;
+      default:
+        fail(1, `unknown argument: ${a}`);
+    }
+  }
+  if (!args.logoutUrl) fail(1, 'missing --logout-url');
+  if (!args.networkFile) fail(1, 'missing --network-file');
+  if (!args.targetOrg) fail(1, 'missing --target-org');
+  return args;
+}
+
+function fail(code, message) {
+  console.error(`set-logout-url: ${message}`);
+  process.exit(code);
+}
+
+function skip(message) {
+  console.error(
+    `set-logout-url: SKIP — ${message}. Set the logout URL manually in the site's ` +
+      `Administration settings (Login & Registration -> Logout URL).`,
+  );
+  process.exit(3);
+}
+
+// ---- pure URL helpers (port of org-setup-url.mjs) ---------------------------
+
+/** True when `value` is an absolute http(s) URL — already deployable as-is. */
+function isAbsoluteLogoutUrl(value) {
+  return /^https?:\/\//i.test(String(value).trim());
+}
+
+/** Leading path segment of a URL or path: "/app/" -> "app", "/" -> "". */
+function firstPathSegment(pathOrUrl) {
+  let pathname;
+  try {
+    pathname = new URL(pathOrUrl).pathname; // absolute URL
+  } catch {
+    pathname = String(pathOrUrl).split(/[?#]/)[0]; // relative path
+  }
+  return pathname.replace(/^\/+/, '').split('/')[0];
+}
+
+/**
+ * Choose the community whose siteUrl anchors a relative logout path — match on
+ * the siteUrl PATH first, then on `name` == siteName. Never guesses an arbitrary
+ * community (resolving against the wrong origin yields a valid-but-wrong URL).
+ */
+function pickCommunityBaseUrl(communities, configLogoutUrl, siteName) {
+  const list = Array.isArray(communities) ? communities.filter((c) => c && c.siteUrl) : [];
+  const seg = firstPathSegment(configLogoutUrl);
+  if (seg) {
+    const byPath = list.find((c) => firstPathSegment(c.siteUrl) === seg);
+    if (byPath) return byPath.siteUrl;
+  }
+  if (siteName) {
+    const byName = list.find((c) => c.name === siteName);
+    if (byName) return byName.siteUrl;
+  }
+  return null;
+}
+
+/** Resolve a config value to an absolute URL (relative -> against baseUrl origin). */
+function resolveLogoutUrl(configLogoutUrl, baseUrl) {
+  const value = String(configLogoutUrl).trim();
+  if (isAbsoluteLogoutUrl(value)) return value;
+  if (!baseUrl) {
+    throw new Error(
+      `logout URL "${configLogoutUrl}" is site-relative but no Experience Cloud community ` +
+        `site URL was found to resolve it into an absolute URL`,
+    );
+  }
+  let resolved;
+  try {
+    resolved = new URL(value, baseUrl).href;
+  } catch (e) {
+    throw new Error(`could not resolve "${configLogoutUrl}" against "${baseUrl}": ${e.message}`);
+  }
+  if (!isAbsoluteLogoutUrl(resolved)) {
+    throw new Error(`resolved logout URL "${resolved}" is not an absolute http(s) URL`);
+  }
+  return resolved;
+}
+
+// ---- XML helpers (port of org-setup-xml.mjs setLogoutUrl) -------------------
+
+/** Direct child element names of <Network> (depth-aware, no XML deps). */
+function networkChildNames(xml) {
+  const open = xml.match(/<Network\b[^>]*>/);
+  const close = xml.lastIndexOf('</Network>');
+  if (!open || close === -1) return [];
+  const inner = xml.slice(open.index + open[0].length, close);
+  const tag = /<(\/?)([A-Za-z_][\w.-]*)\b[^>]*?(\/?)>/g;
+  const names = new Set();
+  let depth = 0;
+  let m;
+  while ((m = tag.exec(inner)) !== null) {
+    const [, closing, name, selfClose] = m;
+    if (closing) {
+      depth -= 1;
+    } else if (selfClose) {
+      if (depth === 0) names.add(name);
+    } else {
+      if (depth === 0) names.add(name);
+      depth += 1;
+    }
+  }
+  return [...names];
+}
+
+function firstChildIndent(xml) {
+  const m = xml.match(/\n([ \t]+)<[A-Za-z_]/);
+  return m ? m[1] : '    ';
+}
+
+/**
+ * Returns { xml, changed }. Idempotent (unchanged when already equal); replaces
+ * an existing value in place; else inserts <logoutUrl> in the canonical
+ * alphabetical position among Network's top-level children. Throws on an
+ * XML-special char in the URL (reject, don't escape).
+ */
+function setLogoutUrl(xml, url) {
+  if (XML_SPECIAL_CHARS.test(String(url))) {
+    throw new Error(`logoutUrl "${url}" contains an XML-special character (& < > " ')`);
+  }
+  const node = `<logoutUrl>${url}</logoutUrl>`;
+  const existing = xml.match(/<logoutUrl>([^<]*)<\/logoutUrl>/);
+  if (existing) {
+    if (existing[1] === url) return { xml, changed: false };
+    return { xml: xml.replace(/<logoutUrl>[^<]*<\/logoutUrl>/, node), changed: true };
+  }
+  // Absent — insert before the first top-level sibling that sorts after "logoutUrl".
+  const successor = networkChildNames(xml)
+    .filter((name) => name > 'logoutUrl')
+    .sort()[0];
+  if (successor) {
+    const beforeSuccessor = new RegExp(`(\\n[ \\t]*)(<${successor}\\b)`);
+    if (beforeSuccessor.test(xml)) {
+      return { xml: xml.replace(beforeSuccessor, `$1${node}$1$2`), changed: true };
+    }
+  }
+  const indent = firstChildIndent(xml);
+  const beforeClose = /(\n)([ \t]*<\/Network>)/;
+  if (beforeClose.test(xml)) {
+    return { xml: xml.replace(beforeClose, `\n${indent}${node}$1$2`), changed: true };
+  }
+  return { xml: xml.replace(/(<Network\b[^>]*>)/, `$1\n${indent}${node}`), changed: true };
+}
+
+// ---- org I/O ----------------------------------------------------------------
+
+/**
+ * Resolve the org's highest supported REST API version (e.g. "v66.0") via the
+ * version-less `/services/data/` endpoint. Falls back to FALLBACK_API_VERSION
+ * if the lookup fails or returns nothing usable, so resolution is never worse
+ * than a fixed pin.
+ */
+function resolveApiVersion(targetOrg) {
+  try {
+    const out = execFileSync(
+      'sf',
+      ['api', 'request', 'rest', '/services/data/', '--target-org', targetOrg],
+      { encoding: 'utf8', timeout: 120000 },
+    );
+    const versions = JSON.parse(out);
+    const max = Array.isArray(versions)
+      ? versions
+          .map((v) => parseFloat(v && v.version))
+          .filter((n) => !Number.isNaN(n))
+          .sort((a, b) => a - b)
+          .pop()
+      : undefined;
+    if (max) return `v${max.toFixed(1)}`;
+  } catch {
+    // Unreachable org, unexpected shape, etc. — fall through to the pinned floor.
+  }
+  return FALLBACK_API_VERSION;
+}
+
+function fetchCommunities(targetOrg) {
+  const apiVersion = resolveApiVersion(targetOrg);
+  const out = execFileSync(
+    'sf',
+    ['api', 'request', 'rest', `/services/data/${apiVersion}/connect/communities`, '--target-org', targetOrg],
+    { encoding: 'utf8', timeout: 120000 },
+  );
+  const parsed = JSON.parse(out);
+  return Array.isArray(parsed.communities) ? parsed.communities : [];
+}
+
+function deployNetworkFile(networkFile, targetOrg) {
+  execFileSync(
+    'sf',
+    ['project', 'deploy', 'start', '--source-dir', networkFile, '--target-org', targetOrg],
+    { stdio: 'inherit', timeout: 120000 },
+  );
+}
+
+// ---- main -------------------------------------------------------------------
+
+function main() {
+  const args = parseArgs(process.argv.slice(2));
+
+  if (!existsSync(args.networkFile)) {
+    skip(`network metadata not found: ${args.networkFile}`);
+  }
+
+  // 1. Resolve to an absolute URL.
+  let absoluteUrl;
+  try {
+    let baseUrl = null;
+    if (!isAbsoluteLogoutUrl(args.logoutUrl)) {
+      baseUrl = pickCommunityBaseUrl(fetchCommunities(args.targetOrg), args.logoutUrl, args.site);
+    }
+    absoluteUrl = resolveLogoutUrl(args.logoutUrl, baseUrl);
+  } catch (e) {
+    skip(`cannot resolve an absolute logout URL — ${e.message}`);
+  }
+
+  // 2. Write it into the network metadata (idempotent).
+  let result;
+  try {
+    result = setLogoutUrl(readFileSync(args.networkFile, 'utf8'), absoluteUrl);
+  } catch (e) {
+    skip(`cannot set <logoutUrl> in ${args.networkFile} — ${e.message}`);
+  }
+
+  if (!result.changed) {
+    console.log(`logout URL already set to "${absoluteUrl}"; no change (skipping deploy).`);
+    process.exit(0);
+  }
+  writeFileSync(args.networkFile, result.xml);
+  console.log(`set <logoutUrl>${absoluteUrl}</logoutUrl> in ${args.networkFile}`);
+
+  // 3. Deploy only that file (best-effort).
+  if (args.deploy) {
+    try {
+      deployNetworkFile(args.networkFile, args.targetOrg);
+      console.log(`deployed <logoutUrl> for "${args.site || args.networkFile}".`);
+    } catch (e) {
+      skip(
+        `failed to deploy the network file (${e.message}). If the org's Network ` +
+          `emailSenderAddress differs from the shipped value it can block this deploy`,
+      );
+    }
+  }
+  process.exit(0);
+}
+
+main();