[Fleet]: Elastic Defend fails with "Input not supported" on FIPS-enabled Agent (Windows x64), causing Agent to go unhealthy.

**Kibana Build details:**
```
VERSION: 9.5.0-SNAPSHOT
BUILD: 104114
COMMIT: 2860842a141c80f2cef7f5c27a5840a157656ac2
```

**Host OS and Browser version:** Windows, All browsers

**Preconditions:**

1. A 9.5.0-SNAPSHOT Kibana cloud environment is available.
2. Windows x64 endpoint is available.
3. Elastic Agent 9.5.0 64-bit (x86_64) FIPS artifact has been downloaded.
4. FIPS Elastic Agent has been installed on the Windows x64 endpoint and enrolled in Fleet.

**Steps to reproduce:**

1. Navigate to Fleet → Agents.
2. Click on the enrolled FIPS agent, then navigate to its Agent Policy.
3. Add the Elastic Defend integration to the agent policy.
4. Wait 5–10 minutes.
5. Observe the agent transitions to Unhealthy.
6. Navigate to the Agent Details tab.
7. Expand the Elastic Defend integration row.
8. Observe the error message: "Input not supported".

**Expected Result:**
- Elastic Defend should install and run successfully on a FIPS-enabled Elastic Agent,

**Screenshots:**

**Screen recording**

https://github.com/user-attachments/assets/11d7fd59-6ff1-4074-a2fe-987b28591e72

**Agent logs**

[elastic-agent-diagnostics-2026-06-03T07-09-01Z-00 (1).zip](https://github.com/user-attachments/files/28545717/elastic-agent-diagnostics-2026-06-03T07-09-01Z-00.1.zip)

**ticket**
- https://github.com/elastic/ingest-dev/issues/7431

Start in Fleet → Agents by reproducing the failure with the Elastic Agent 9.5.0 Windows x64 FIPS artifact and collect the linked agent diagnostics logs. Review the related ingest-dev ticket 7431 and determine why Elastic Defend reports "Input not supported"; done means the integration installs and the FIPS agent remains healthy.

Written by the indexing model from the issue text.