The companion's attach button fails on every file, because hermiq has no attachments endpoint

[rubenvdlinde]

What happens

The hermiq companion sits on every Nextcloud page. Its message box has a paperclip. You pick a file, and the upload fails with "Could not attach file", because hermiq has no endpoint to receive it.

Why

src/companion.js mounts nextcloud-vue's CnAiCompanion with chatAppId: 'hermiq' (companion.js:283-284). hermiq locks @conduction/nextcloud-vue at 2.55.1.

In 2.55.1, CnAiInput always renders the attach button (no v-if) and uploads with axios.post(attachmentsUrl(this.chatAppId), formData). attachmentsUrl() resolves to /index.php/apps/hermiq/api/chat/attachments (nextcloud-vue src/composables/aiChatConfig.js:94-95, src/components/CnAiCompanion/CnAiInput.vue:151-163, :1005).

hermiq registers no such route. appinfo/routes.php has chat/send, chat/warm, chat/history, chat/stats, chat/health and chat/stream, and no chat/attachments (routes.php:514-545). No controller under lib/Controller handles an upload for chat, and there are no attribute routes.

So the request 404s and the user sees a control that cannot work.

Fix direction

Either build the endpoint the component expects (text-decode and store the file, return { path, name }, and have the send and stream paths read attachments into the turn), or ask nextcloud-vue for a prop that hides the paperclip and pass it from companion.js until the endpoint exists. The first closes the ch-attach gap as well.

Live check

1. On any Nextcloud page, open the hermiq companion and click the paperclip.
2. Pick a small text file.
3. The browser's network tab shows POST /index.php/apps/hermiq/api/chat/attachments with 404, and the input shows "Could not attach file".

Matrix row: ch-attach, which reads "no" with "no attachment affordance". The row only searched src/views/Chat.vue. The affordance does exist, in the companion, and it is broken. This finding is not in the matrix.

[github-actions]

Thank you for opening this issue! It has been assigned to @rubenvdlinde for review.

What happens next:

1. A maintainer will review this issue and determine the appropriate action
2. If accepted, it may be converted into an OpenSpec change for structured development
3. You will be notified of any status changes

Triage labels:

• triage:accept-feature — accepted as a new feature
• triage:accept-bugfix — accepted as a bug fix
• triage:needs-info — more information needed
• triage:wontfix — will not be addressed
• triage:duplicate — duplicate of another issue