Please address the comments from this code review:

## Overall Comments
- In `TkComment.vue`, the delete confirmation uses the `ADMIN_COMMENT_DELETE_CONFIRM` i18n key for a user-initiated delete; consider introducing a dedicated user-facing confirmation string (e.g. `COMMENT_DELETE_CONFIRM`) to avoid admin-specific wording leaking into the regular UI.
- The ownership-check and delete logic for `COMMENT_DELETE_FOR_USER` is duplicated with only small variations across all backends; consider extracting a small shared helper (or at least centralizing the error messages/constants) to keep the behavior consistent and reduce maintenance overhead.

## Individual Comments

### Comment 1
<location path="src/client/view/components/TkComment.vue" line_range="264-267" />
<code_context>
     },
+    async onDelete () {
+      if (!confirm(t('ADMIN_COMMENT_DELETE_CONFIRM'))) return
+      const result = await call(this.$tcb, 'COMMENT_DELETE_FOR_USER', {
+        id: this.comment.id
+      })
+      if (!result.code) {
+        this.$emit('load')
+      }
</code_context>
<issue_to_address>
**suggestion:** Handle and surface backend errors for comment deletion instead of silently ignoring them.

Currently, a non-zero `COMMENT_DELETE_FOR_USER` `code` is ignored. Please handle this case by surfacing an error (e.g., toast or inline message) so users understand why the comment wasn’t deleted.

Suggested implementation:

```
    async onDelete () {
      if (!confirm(t('ADMIN_COMMENT_DELETE_CONFIRM'))) return
      try {
        const result = await call(this.$tcb, 'COMMENT_DELETE_FOR_USER', {
          id: this.comment.id
        })

        if (!result || result.code) {
          // Surface backend error to the user
          const message =
            (result && (result.message || result.errorMsg)) ||
            t('ADMIN_COMMENT_DELETE_FAILED')
          // TODO: replace alert with project-standard toast/notification
          alert(message)
          return
        }

        this.$emit('load')
      } catch (e) {
        console.error('COMMENT_DELETE_FOR_USER failed', e)
        // TODO: replace alert with project-standard toast/notification
        alert(t('ADMIN_COMMENT_DELETE_FAILED'))
      }
    },

```

1. Add a translation key `ADMIN_COMMENT_DELETE_FAILED` to your i18n resources (e.g., `"ADMIN_COMMENT_DELETE_FAILED": "Failed to delete comment. Please try again later."` or similar).
2. Replace the `alert(...)` calls with your app’s standard mechanism for surfacing errors (e.g., `this.$toast.error(message)`, `this.$message.error(message)`, or a dedicated inline error component), following existing patterns elsewhere in the codebase.
3. If your backend uses a different property than `message`/`errorMsg` for error text, adjust the error extraction logic accordingly.
</issue_to_address>