Universal Autofill Issue with Cisco Secure Client - Incorrectly Fills/Overwrites Password with TOTP

1Password Version: [e.g., 1Password for Mac 8.10.78] 
Operating System: [e.g., macOS Sequoia 15.5]

I'm experiencing an issue with Universal Autofill when trying to connect to a VPN via Cisco Secure Client, which requires a Username, Password, and a time-based one-time password (which the app labels as "Passcode").

Expected Behavior: When using Universal Autofill (Command + \), I expect 1Password to:

1. Correctly fill the "Username" field in the application.
2. Correctly fill the "Password" field in the application.
3. Correctly fill the "Passcode" (TOTP) field in the application with the 6-digit code from the "one-time password" field in my 1Password login item.

Actual Behavior Observed:

I've encountered a couple of problematic behaviors:

Scenario 1: Default "one-time password" field label in 1Password

1. I place my cursor in the "Username" field of [Application Name].
2. I trigger Universal Autofill.
3. The "Username" field is filled correctly.
4. The "Password" field is filled correctly initially.
5. Almost immediately, the "Password" field gets partially overwritten by the first 3 digits of my 6-digit TOTP.
6. The application's "Passcode" field then gets filled with the remaining 3 digits of the TOTP.
• Result: Incorrect password (due to being overwritten) and an incomplete/incorrect Passcode, leading to login failure.

Scenario 2: Renaming the 1Password "one-time password" field label to "Passcode" To try and match the application's field label, I edited my 1Password login item and changed the label of the "one-time password" field to "Passcode".

1. I place my cursor in the "Username" field of [Application Name].
2. I trigger Universal Autofill.
3. The "Username" field is filled correctly.
4. The "Password" field in the application is then completely overwritten by the full 6-digit TOTP.
5. The application's "Passcode" field is left blank.
• Result: Incorrect password (it's now the TOTP) and a blank Passcode, leading to login failure.

Suggestion/Feature Request: Could you please investigate improving Universal Autofill's compatibility or some customization ability with some app the have unusually numbers of fields? Specifically, it seems to struggle with correctly identifying and populating the distinct "Password" and "Passcode" (TOTP) fields after the username in this app in particular, especially when the application expects a separate TOTP input. Improved handling for multi-step or multi-field logins involving TOTPs in desktop applications would be highly beneficial.