@f5xc-salesdemos/xcsh 19.39.0 → 19.40.0

package/package.json

@@ -1,7 +1,7 @@
 {
 	"type": "module",
 	"name": "@f5xc-salesdemos/xcsh",
-	"version": "19.39.0",
+	"version": "19.40.0",
 	"description": "Coding agent CLI with read, bash, edit, write tools and session management",
 	"homepage": "https://github.com/f5xc-salesdemos/xcsh",
 	"author": "Can Boluk",
@@ -51,13 +51,13 @@
 	"dependencies": {
 		"@agentclientprotocol/sdk": "0.16.1",
 		"@mozilla/readability": "^0.6",
-		"@f5xc-salesdemos/xcsh-stats": "19.39.0",
-		"@f5xc-salesdemos/pi-agent-core": "19.39.0",
-		"@f5xc-salesdemos/pi-ai": "19.39.0",
-		"@f5xc-salesdemos/pi-natives": "19.39.0",
-		"@f5xc-salesdemos/pi-resource-management": "19.39.0",
-		"@f5xc-salesdemos/pi-tui": "19.39.0",
-		"@f5xc-salesdemos/pi-utils": "19.39.0",
+		"@f5xc-salesdemos/xcsh-stats": "19.40.0",
+		"@f5xc-salesdemos/pi-agent-core": "19.40.0",
+		"@f5xc-salesdemos/pi-ai": "19.40.0",
+		"@f5xc-salesdemos/pi-natives": "19.40.0",
+		"@f5xc-salesdemos/pi-resource-management": "19.40.0",
+		"@f5xc-salesdemos/pi-tui": "19.40.0",
+		"@f5xc-salesdemos/pi-utils": "19.40.0",
 		"@sinclair/typebox": "^0.34",
 		"@xterm/headless": "^6.0",
 		"ajv": "^8.20",

package/src/internal-urls/build-info.generated.ts

@@ -17,17 +17,17 @@ export interface BuildInfo {
 }
 
 export const BUILD_INFO: BuildInfo = {
-	"version": "19.39.0",
-	"commit": "00fa51ea150526f7b5c80e5f8a271510f1e1129d",
-	"shortCommit": "00fa51e",
+	"version": "19.40.0",
+	"commit": "e25f0c5f25c2bc47d8e50a69b4ad6ac4edc7c3e5",
+	"shortCommit": "e25f0c5",
 	"branch": "main",
-	"tag": "v19.39.0",
-	"commitDate": "2026-06-22T17:19:19Z",
-	"buildDate": "2026-06-22T17:42:34.834Z",
+	"tag": "v19.40.0",
+	"commitDate": "2026-06-22T20:09:25Z",
+	"buildDate": "2026-06-22T20:31:47.773Z",
 	"dirty": true,
 	"prNumber": "",
 	"repoUrl": "https://github.com/f5xc-salesdemos/xcsh",
 	"repoSlug": "f5xc-salesdemos/xcsh",
-	"commitUrl": "https://github.com/f5xc-salesdemos/xcsh/commit/00fa51ea150526f7b5c80e5f8a271510f1e1129d",
-	"releaseUrl": "https://github.com/f5xc-salesdemos/xcsh/releases/tag/v19.39.0"
+	"commitUrl": "https://github.com/f5xc-salesdemos/xcsh/commit/e25f0c5f25c2bc47d8e50a69b4ad6ac4edc7c3e5",
+	"releaseUrl": "https://github.com/f5xc-salesdemos/xcsh/releases/tag/v19.40.0"
 };

package/src/prompts/system/system-prompt.md

@@ -211,6 +211,28 @@ When a user asks you to write, export, or save a resource manifest, produce a cl
 
 When fetching a resource from the API, strip the server-added metadata fields and inject the `kind` field (which the API response does not include). The `/manifest` slash command does this automatically.
 
+<schema-first-generation>
+Before generating any F5 XC JSON configuration — whether:
+- A manifest for `/apply`
+- An API payload for `xcsh_api`
+- A script, converter, or exporter that produces `{kind, metadata, spec}` objects
+
+You **MUST** read `xcsh://api-catalog/?resource={resource_name}&compact=true` to get:
+- The exact API path
+- Minimum required fields
+- OneOf group constraints
+- Correct field names (do NOT guess — e.g. `ip_endpoint` not `address`)
+
+You **MUST NOT** generate spec bodies from memory or generic conventions when the catalog is available.
+You **MUST NOT** use field names from one resource type on another.
+
+The minimum-settings principle (see Terraform Provider Override) applies equally:
+emit only required fields and user-requested values. Omit server-default fields.
+
+For bulk generation (converters, exporters), read the API spec ONCE per resource type,
+then apply the schema consistently across all generated objects.
+</schema-first-generation>
+
 {{#if userProfile}}
 ## Primary Human
 
@@ -311,7 +333,7 @@ Most tools resolve custom protocol URLs to internal resources (not web URLs):
   1. `xcsh://api-spec/{domain}?resource={name}` → full OpenAPI specification
   If the domain is unknown, read `xcsh://api-spec/` first to identify it.
 
-  **MUST NOT** read proactively.
+  `xcsh://api-spec/` **MUST NOT** be read proactively.
   Never start at `xcsh://api-spec/` for CRUD operations — the catalog is faster.
   Never guess API paths or request schemas.
   Also available: `xcsh://api-spec/workflows/` (step-by-step guides),

package/src/prompts/tools/xcsh-api.md

@@ -10,6 +10,9 @@ Pass all path `{placeholder}` values via `params`, e.g. `{ namespace: "default",
 Body is sent for all methods except GET when `payload` is provided — including DELETE operations that require a body.
 Payload values like `$F5XC_NAMESPACE` are auto-expanded from the active context.
 Use this tool after reading the API catalog to get the endpoint path and payload structure.
+The payload templates below are reference examples. When the API catalog is available,
+prefer `xcsh://api-catalog/?resource={resource_name}&compact=true` for the current minimum payload
+over these static templates.
 Response format:
 - **List**: `{"items": […], "errors": []}` — each item has `name`, `namespace`, `uid`.
 - **Single resource**: `{"metadata": {"name", "namespace"}, "system_metadata": {"uid", "creation_timestamp"}, "spec": {…}}` — noise-reduced in TUI (nulls/empties stripped).
@@ -80,7 +83,7 @@ Port choices (orthogonal): `"use_default_port": {}` (default) | `"port": <int>`
 
 Example — port 8443 in advertise_where: `{"virtual_site": {…, "network": "SITE_NETWORK_INSIDE_AND_OUTSIDE"}, "port": 8443}`
 
-**CRITICAL — all 7 SiteNetwork values work with BOTH `virtual_site` AND `site`**. "IP fabric network" = `SITE_NETWORK_IP_FABRIC` — valid for `virtual_site` too. Do NOT ask for alternatives; immediately use the matching enum.
+**CRITICAL — all 6 LB-valid SiteNetwork values work with BOTH `virtual_site` AND `site`**. Do NOT ask for alternatives; immediately use the matching enum. `SITE_NETWORK_IP_FABRIC` works with both reference types but is **NOT valid for HTTP LB advertising** (see above) — use it only in non-LB contexts.
 
 Example — advertise on a Customer Edge virtual site, inside and outside:
 ```json
@@ -154,7 +157,7 @@ Each of the 12 oneOf groups has two or three mutually exclusive choices — pick
 |url_categorization|`"disable_url_categorization":{}` OR `"enable_url_categorization":{}`||
 |management_network|`"disable_management_network":{}` OR `"enable_management_network":{}`||
 
-**SMSv2 routing rule**: When asked to create a SecureMesh site v2 that *uses* or *applies* a policy (forward proxy, firewall, log receiver, cluster group), the target resource is always `securemesh_site_v2s` — POST the site payload with the policy reference in the appropriate spec field. Do NOT create the policy resource as the action; the policy already exists as a prerequisite. For example, "Create a SecureMesh site v2 with forward proxy policy X" → POST to `securemesh_site_v2s` with `"active_forward_proxy_policies":{"active_forward_proxy_policies":[{"name":"X","namespace":"<ns>"}]}` in the spec.
+**SMSv2 routing rule**: When asked to create a SecureMesh site v2 that *uses* or *applies* a policy (forward proxy, firewall, log receiver, cluster group), the target resource is always `securemesh_site_v2s` — POST the site payload with the policy reference in the appropriate spec field. Do NOT create the policy resource as the action; the policy already exists as a prerequisite. For example, "Create a SecureMesh site v2 with forward proxy policy X" → POST to `securemesh_site_v2s` with `"active_forward_proxy_policies":{"forward_proxy_policies":[{"name":"X","namespace":"system"}]}` in the spec.
 
 **SecureMesh Site v2 Terraform HCL (`f5xc_securemesh_site_v2`)** — When asked to write Terraform for f5xc_securemesh_site_v2, use `resource "f5xc_securemesh_site_v2"` in system namespace. Each of the 12 oneOf groups maps directly to a Terraform block. Base HCL: