@salesforce/lds-runtime-aura 1.451.0-dev13 → 1.451.0-dev14

package/dist/ldsEngineCreator.js

@@ -2590,7 +2590,7 @@ function buildServiceDescriptor$d(luvio) {
         },
     };
 }
-// version: 1.451.0-dev13-c8cd268691
+// version: 1.451.0-dev14-2ce0dd97dc
 
 class AuraGraphQLNormalizedCacheControlCommand extends AuraNormalizedCacheControlCommand {
   constructor(config, documentRootType, services) {
@@ -2929,7 +2929,7 @@ function buildServiceDescriptor$9(notifyRecordUpdateAvailable, getNormalizedLuvi
         },
     };
 }
-// version: 1.451.0-dev13-c8cd268691
+// version: 1.451.0-dev14-2ce0dd97dc
 
 class RetryService {
   constructor(defaultRetryPolicy) {
@@ -5935,7 +5935,7 @@ function getEnvironmentSetting(name) {
     }
     return undefined;
 }
-// version: 1.451.0-dev13-175bc5540e
+// version: 1.451.0-dev14-e7b4018fe5
 
 const auraClientService = getAuraClientService();
 const defaultConfig = {
@@ -7705,7 +7705,7 @@ const SFAP_BASE_URL = 'api.salesforce.com';
 // to. Distinct from SFAP's `sfap_api` so the Data360 host-rewrite interceptor only
 // ever runs for that command — zero blast radius on the SFAP fleet.
 //
-// The tag is deliberately named after the *mechanism* (the `cdp_url` host rewrite),
+// The tag is deliberately named after the *mechanism* (the `cdp_tse_url` host rewrite),
 // not a capability, because this whole descriptor is interim: it exists only while
 // the mint service returns the fixed SFAP `baseUri` regardless of platform. When the
 // service returns the correct per-platform `baseUri`, the data 360 route can be re-evaluated.
@@ -7720,7 +7720,7 @@ const DATA_360_CDP_URL_REWRITE_AUTH_SCOPE = 'data_360_cdp_url_rewrite';
 // (`<domain-suffix>`) is environment-dependent — it differs per deployment
 // environment. This is why the interceptor strips any scheme before parsing
 // and applies no host-suffix policy — see the interceptor docblock's trust boundary.
-const CDP_URL_CLAIM = 'cdp_url';
+const CDP_URL_CLAIM = 'cdp_tse_url';
 function buildDispatchingSfapJwtResolver(legacyResolver, parameterizedResolver) {
     return {
         getJwt(params) {
@@ -7770,14 +7770,14 @@ function buildJwtAuthorizedSfapFetchServiceDescriptor(logger) {
  *
  * Unlike SFAP, the per-tenant base host is NOT returned in the mint response's
  * `baseUri` (which is the fixed SFAP host); it rides on the minted JWT as the
- * `cdp_url` claim. The standard `JwtRequestModifier` only receives `extraInfo`,
+ * `cdp_tse_url` claim. The standard `JwtRequestModifier` only receives `extraInfo`,
  * never the decoded claims, so the host rewrite cannot be expressed as a modifier
  * — it must read the token directly. This descriptor therefore uses a bespoke
  * interceptor ({@link buildData360HostRewriteInterceptor}) that mints the
- * parameterized SFAP JWT, attaches the Bearer token, decodes `cdp_url`, and
+ * parameterized SFAP JWT, attaches the Bearer token, decodes `cdp_tse_url`, and
  * rewrites the request host to that TSE.
  *
- * It reuses the module's `sfapJwtManager`: `cdp_url` is emitted on the same
+ * It reuses the module's `sfapJwtManager`: `cdp_tse_url` is emitted on the same
  * `SFAP_API`-scope JWT, so the Data360 command mints the same kind of token — it
  * just forwards the data-cloud scopes via the context-seed `jwtMintParams`.
  *
@@ -7907,25 +7907,25 @@ function buildJwtRequestInterceptor(logger) {
 /**
  * Request interceptor for the direct-to-Data360 command. It cannot use the
  * standard `JwtRequestModifier` seam because the tenant host is a JWT *claim*
- * (`cdp_url`), and modifiers only receive `extraInfo`. So — like the copilot
+ * (`cdp_tse_url`), and modifiers only receive `extraInfo`. So — like the copilot
  * interceptor that reads `decodedInfo.iss` — it holds the token directly:
  *
  *   1. Read the command's `jwtMintParams` off the per-request context seed and
  *      mint (via the parameterized SFAP resolver, routed by the dispatching
  *      resolver inside `sfapJwtManager`). Without mint params there is no token
  *      to authorize with, so leave the request untouched.
- *   2. Decode `cdp_url` from the JWT and resolve the tenant-specific endpoint
- *      (TSE). `cdp_url` is a bare host, so a scheme is prepended before parsing
+ *   2. Decode `cdp_tse_url` from the JWT and resolve the tenant-specific endpoint
+ *      (TSE). `cdp_tse_url` is a bare host, so a scheme is prepended before parsing
  *      and the protocol is forced to `https:`.
- *   3. Only after a usable `cdp_url` is confirmed, attach `Authorization: Bearer
+ *   3. Only after a usable `cdp_tse_url` is confirmed, attach `Authorization: Bearer
  *      <jwt>` and rewrite the request URL's host/protocol to the TSE.
  *
- * **Trust boundary.** `cdp_url` is a claim on a first-party, server-minted JWT
+ * **Trust boundary.** `cdp_tse_url` is a claim on a first-party, server-minted JWT
  * delivered over the same-origin Aura transport, so the interceptor does NOT police
  * its contents (no host-suffix or format allowlist) — the routing host is the
  * minting service's responsibility, and this mirrors the SFAP sibling, which
  * likewise trusts the server-provided `baseUri` rewrite target. The one guard that
- * remains is shape hygiene: if `cdp_url` is absent/empty/non-string (org not
+ * remains is shape hygiene: if `cdp_tse_url` is absent/empty/non-string (org not
  * CDP-provisioned, so the server's claim gate did not fire) the interceptor throws
  * a developer-facing error instead of an opaque parse failure. A minted token is
  * never attached until a usable host is in hand.
@@ -7961,7 +7961,7 @@ function buildData360HostRewriteInterceptor(logger) {
                 // eslint-disable-next-line @salesforce/lds/no-error-in-production
                 throw new Error(`Data360 fetch service: minted JWT has no usable "${CDP_URL_CLAIM}" claim; cannot route the request to a Data Cloud tenant endpoint.`);
             }
-            // `cdp_url` is a bare host (no scheme); prepend https so `new URL`
+            // `cdp_tse_url` is a bare host (no scheme); prepend https so `new URL`
             // parses it as an origin. Force https regardless of any scheme in the
             // claim — the TSE is always TLS.
             const tse = new URL(`https://${cdpUrl.replace(/^[a-z]+:\/\//i, '')}`);
@@ -11595,4 +11595,4 @@ function ldsEngineCreator() {
 }
 
 export { LexRequestStrategy, PDL_ENGINE_REGISTRATION_ID, PdlPrefetcherEventType, PdlRequestPriority, buildPredictorForContext, configService, ldsEngineCreator as default, initializeLDS, initializeOneStore, notifyUpdateAvailableFactory, registerRequestStrategy, saveRequestAsPrediction, subscribeToPrefetcherEvents, unregisterRequestStrategy, whenPredictionsReady };
-// version: 1.451.0-dev13-c8cd268691
+// version: 1.451.0-dev14-2ce0dd97dc

package/dist/types/fetch-service-descriptors/jwt-authorized-fetch-service.d.ts

@@ -11,14 +11,14 @@ export declare function buildJwtAuthorizedSfapFetchServiceDescriptor(logger: Log
  *
  * Unlike SFAP, the per-tenant base host is NOT returned in the mint response's
  * `baseUri` (which is the fixed SFAP host); it rides on the minted JWT as the
- * `cdp_url` claim. The standard `JwtRequestModifier` only receives `extraInfo`,
+ * `cdp_tse_url` claim. The standard `JwtRequestModifier` only receives `extraInfo`,
  * never the decoded claims, so the host rewrite cannot be expressed as a modifier
  * — it must read the token directly. This descriptor therefore uses a bespoke
  * interceptor ({@link buildData360HostRewriteInterceptor}) that mints the
- * parameterized SFAP JWT, attaches the Bearer token, decodes `cdp_url`, and
+ * parameterized SFAP JWT, attaches the Bearer token, decodes `cdp_tse_url`, and
  * rewrites the request host to that TSE.
  *
- * It reuses the module's `sfapJwtManager`: `cdp_url` is emitted on the same
+ * It reuses the module's `sfapJwtManager`: `cdp_tse_url` is emitted on the same
  * `SFAP_API`-scope JWT, so the Data360 command mints the same kind of token — it
  * just forwards the data-cloud scopes via the context-seed `jwtMintParams`.
  *

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@salesforce/lds-runtime-aura",
-    "version": "1.451.0-dev13",
+    "version": "1.451.0-dev14",
     "license": "SEE LICENSE IN LICENSE.txt",
     "description": "LDS engine for Aura runtime.",
     "main": "dist/ldsEngineCreator.js",
@@ -36,15 +36,15 @@
     "devDependencies": {
         "@conduit-client/service-provisioner": "3.26.1-dev3",
         "@conduit-client/tools-core": "3.26.1-dev3",
-        "@salesforce/lds-adapters-apex": "^1.451.0-dev13",
-        "@salesforce/lds-adapters-uiapi": "^1.451.0-dev13",
-        "@salesforce/lds-ads-bridge": "^1.451.0-dev13",
-        "@salesforce/lds-aura-storage": "^1.451.0-dev13",
-        "@salesforce/lds-bindings": "^1.451.0-dev13",
-        "@salesforce/lds-instrumentation": "^1.451.0-dev13",
-        "@salesforce/lds-network-adapter": "^1.451.0-dev13",
-        "@salesforce/lds-network-aura": "^1.451.0-dev13",
-        "@salesforce/lds-network-fetch": "^1.451.0-dev13",
+        "@salesforce/lds-adapters-apex": "^1.451.0-dev14",
+        "@salesforce/lds-adapters-uiapi": "^1.451.0-dev14",
+        "@salesforce/lds-ads-bridge": "^1.451.0-dev14",
+        "@salesforce/lds-aura-storage": "^1.451.0-dev14",
+        "@salesforce/lds-bindings": "^1.451.0-dev14",
+        "@salesforce/lds-instrumentation": "^1.451.0-dev14",
+        "@salesforce/lds-network-adapter": "^1.451.0-dev14",
+        "@salesforce/lds-network-aura": "^1.451.0-dev14",
+        "@salesforce/lds-network-fetch": "^1.451.0-dev14",
         "jwt-encode": "1.0.1"
     },
     "dependencies": {
@@ -76,11 +76,11 @@
         "@luvio/network-adapter-composable": "0.161.2",
         "@luvio/network-adapter-fetch": "0.161.2",
         "@lwc/state": "^0.29.0",
-        "@salesforce/lds-adapters-onestore-graphql": "^1.451.0-dev13",
+        "@salesforce/lds-adapters-onestore-graphql": "^1.451.0-dev14",
         "@salesforce/lds-adapters-uiapi-lex": "^1.415.0",
-        "@salesforce/lds-durable-storage": "^1.451.0-dev13",
-        "@salesforce/lds-luvio-service": "^1.451.0-dev13",
-        "@salesforce/lds-luvio-uiapi-records-service": "^1.451.0-dev13"
+        "@salesforce/lds-durable-storage": "^1.451.0-dev14",
+        "@salesforce/lds-luvio-service": "^1.451.0-dev14",
+        "@salesforce/lds-luvio-uiapi-records-service": "^1.451.0-dev14"
     },
     "luvioBundlesize": [
         {