fix(zscaler): shorten Integration Model title to "Zscaler Internet Access"

Zscaler/ZIA/OpenAPIs/zscaler_zia_api-latest.json

@@ -3,7 +3,7 @@
   "info": {
     "version": "latest",
     "x-vendor-api-version": "ZIA REST API v1 (via OneAPI)",
-    "title": "Zscaler Internet Access (ZIA) API",
+    "title": "Zscaler Internet Access",
     "description": "Zscaler Internet Access (ZIA) API provides programmatic access to ZIA policy and configuration objects: firewall filtering rules and their supporting objects, URL filtering and categories, cloud app control, DLP dictionaries/engines/rules, file type control rules, locations, rule labels, and user/group/department management.\n\nAuthentication: OAuth2 client-credentials via Zscaler's unified OneAPI platform (brokered through Zidentity). Requires OneAPI access to be enabled for your organization by your Zscaler account team -- it is not self-service. Generate a client ID/secret at Admin Portal > API Key Management > OneAPI Credentials.\n\nThis spec was built directly from Zscaler's official, actively-maintained zscaler-sdk-go source (github.com/zscaler/zscaler-sdk-go) -- endpoint paths, HTTP verbs, and field-level request/response schemas (including per-field doc comments) were extracted from the SDK's typed Go structs and service functions.\n\nSource: https://github.com/zscaler/zscaler-sdk-go/tree/master/zscaler/zia/services",
     "x-itential-curated": "Scoped to ZIA's most commonly automated policy/config areas rather than its full 60+ service surface: Firewall Policies (filtering rules and supporting objects -- network services/applications, IP source/destination groups, time windows, app services), URL Filtering & Categories, Cloud App Control, DLP (dictionaries, engines, web rules, notification templates, ICAP servers), File Type Control, Locations, Rule Labels, and User Management (users, groups, departments) -- 111 operations, all traced to real endpoint constants and typed request/response structs in Zscaler's official SDK. Excludes DNS control, forwarding control, IPS/NAT control, SSL inspection, sandbox, traffic forwarding/GRE, NSS feeds, malware protection, bandwidth control, and ~50 other more specialized ZIA service areas."
   },

Zscaler/ZIA/OpenAPIs/zscaler_zia_api-v3.8.46.json

@@ -3,7 +3,7 @@
   "info": {
     "version": "3.8.46",
     "x-vendor-api-version": "zscaler-sdk-go v3.8.46",
-    "title": "Zscaler Internet Access (ZIA) API",
+    "title": "Zscaler Internet Access",
     "description": "Full Zscaler Internet Access (ZIA) API surface, extracted from Zscaler's official zscaler-sdk-go source (github.com/zscaler/zscaler-sdk-go, release v3.8.46) -- endpoint paths, HTTP verbs, and field-level request/response schemas were derived directly from the SDK's typed Go structs and service functions. Preserved as-is (uncurated) for reference; see zscaler_zia_api-latest.json for the curated subset covering common CRUD automation.\n\nAuthentication: OAuth2 client-credentials via Zscaler's unified OneAPI platform (brokered through Zidentity), or legacy per-product obfuscated-API-key + session-cookie auth (not modeled here).\n\nSource: https://github.com/zscaler/zscaler-sdk-go/tree/v3.8.46/zscaler/zia/services"
   },
   "servers": [

Zscaler/ZIA/README.md

@@ -27,7 +27,7 @@ This project provides OpenAPI specs for automating against ZIA's REST API via an
 | Requirement | Version |
 |---|---|
 | Itential Platform | 6.x |
-| `Zscaler Internet Access (ZIA) API:latest` Integration Model | Required to build automation against the OpenAPI spec, and to run the Studio Project below |
+| `Zscaler Internet Access:latest` Integration Model | Required to build automation against the OpenAPI spec, and to run the Studio Project below |
 | Zscaler OneAPI access enabled for your organization | Required — not self-service; contact your Zscaler account team |
 
 ## Integration Configuration
@@ -94,7 +94,7 @@ Full spec extracted from `zscaler-sdk-go` release `v3.8.46` (479 operations) —
 
 ### Zscaler ZIA Project
 
-Backed by the **`Zscaler Internet Access (ZIA) API:latest`** Integration Model (see [`zscaler_zia_api-latest.json`](./OpenAPIs/zscaler_zia_api-latest.json) above). The project contains **111 workflows** organized into **9 folders**.
+Backed by the **`Zscaler Internet Access:latest`** Integration Model (see [`zscaler_zia_api-latest.json`](./OpenAPIs/zscaler_zia_api-latest.json) above). The project contains **111 workflows** organized into **9 folders**.
 
 #### Folder Structure
 
@@ -114,5 +114,5 @@ Backed by the **`Zscaler Internet Access (ZIA) API:latest`** Integration Model (
 
 | Dependency | Notes |
 |---|---|
-| `Zscaler Internet Access (ZIA) API:latest` Integration Model | Import from [`zscaler_zia_api-latest.json`](./OpenAPIs/zscaler_zia_api-latest.json) before importing the project |
+| `Zscaler Internet Access:latest` Integration Model | Import from [`zscaler_zia_api-latest.json`](./OpenAPIs/zscaler_zia_api-latest.json) before importing the project |
 | `Zscaler` integration instance | Create in **Admin > Integrations** with the connection properties above. Workflows are wired to an integration instance named `Zscaler` — update the `adapter_id` value in each workflow task if yours is named differently |