hermes - 💡(How to fix) Fix feat: support Jira and Confluence attachments

Feature Description

Support attachment operations for Jira and Confluence.

Motivation

Current Atlassian workflows often need to upload, list, download, and possibly delete attachments when interacting with Jira issues and Confluence pages. Without attachment support, users still need to switch to the web UI or use separate scripts, which breaks CLI completeness and automation workflows.

Proposed Solution

Add first-class attachment capabilities for both Jira and Confluence.

Jira

Support commands/APIs to:

• upload attachments to an issue
• list issue attachments
• download attachments
• optionally delete attachments (if permissions allow)

Example UX:

atlassian-cli jira issue attachment upload <ISSUE-KEY> ./report.pdf
atlassian-cli jira issue attachment list <ISSUE-KEY>
atlassian-cli jira issue attachment download <ISSUE-KEY> --name report.pdf --output ./report.pdf

Confluence

Support commands/APIs to:

• upload attachments to a page
• list page attachments
• download attachments
• optionally update/replace an existing attachment
• optionally delete attachments (if permissions allow)

Example UX:

atlassian-cli confluence page attachment upload <PAGE-ID> ./diagram.png
atlassian-cli confluence page attachment list <PAGE-ID>
atlassian-cli confluence page attachment download <PAGE-ID> --name diagram.png --output ./diagram.png

Notes

• Use multipart upload where required by the Atlassian APIs.
• Preserve useful metadata in output (filename, media type, size, attachment ID, download URL).
• If some operations are unsupported by permissions or product API differences, document the constraints clearly.
• Add help text, examples, and tests so the capability is discoverable.

Alternatives Considered

• Rely on raw HTTP API calls outside the CLI.
• Support only upload first and defer listing/downloading.

A staged rollout is acceptable, but upload + list should ideally land first for both products.