Add missing CID return arrows in IPFS/IPNS sequence diagrams

[Copilot]

Sequence diagrams showed the Backend adding metadata to IPFS but omitted the return arrow sending the CID back to the Client. This masked a critical dependency: the Client needs the CID to construct the IPNS record it signs in the next step.

Changes

• Added B->>C: Return CID after all B->>IPFS: Add metadata, return CID operations across 8 sequence diagrams
• Affected flows: File Upload, Create Folder (2 instances), Rename, Move (2 instances), Delete, Update File Content
• Bumped documentation version 1.8.1 → 1.8.2

Example

Before:

C->>B: POST /ipfs/add (encrypted metadata)
B->>IPFS: Add metadata, return CID
C->>C: Sign IPNS record (Ed25519)  # Where does C get the CID?
C->>B: POST /ipns/publish (signed record)

Loading

After:

C->>B: POST /ipfs/add (encrypted metadata)
B->>IPFS: Add metadata, return CID
B->>C: Return CID
C->>C: Sign IPNS record (Ed25519)
C->>B: POST /ipns/publish (signed record)

Loading

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.