feat(#3713): add template search on GUI

[sickwell6988]

Add a client-side search for Task Templates with a search field, live case-insensitive filtering, live result count and an empty-state message]

[cursor]

Security review — PR #3945

Scope: feat(#3713): add template search on GUI (client-side template name filter in Templates.vue + i18n strings).

Prior automation threads: None found; nothing to reconcile.

Outcome: No medium, high, or critical vulnerabilities identified in the added/modified code.

What was reviewed

• Attack surface: New search state bound to a v-text-field; used only for client-side filtering (filterByName, filteredItems) and UI copy (noResultsText, xOfYTemplates).
• Backend / auth: No API, permission, or routing changes. Templates are still loaded via existing authenticated endpoints in ItemListPageBase; search does not fetch or expose additional data.
• XSS (primary candidate): noResultsText interpolates user input into noTemplatesMatchSearch, but the result is passed to Vuetify v-data-table :no-results-text, which renders it as a plain text child in a <td> (not v-html). Vue text rendering escapes HTML, so a payload like <img onerror=alert(1)> is displayed literally, not executed. The xOfYTemplates counter only passes numeric counts.
• Other classes: No injection sinks, SSRF, path traversal, deserialization, secret logging, or dependency changes in this diff.

No action required from a security standpoint for this change set.

  

_{Sent by Cursor Automation: Find vulnerabilities}

[sickwell6988]

#3713 - covers partially this

[sickwell6988]

Decided not to modify API, just modify GUI