[janosmurai]

Type of change

• New feature
• Documentation update

Related issue

SHD-1073 — Public collection and file orchestration APIs

Description

Restores collection, membership and file APIs, five-minute upload links, upload forwarding and storage-event processing. The server enforces caller access and owns metadata/status orchestration. KC owns all RustFS operations; the server has no storage credentials or direct S3 client.

Core operation remains available without the optional KC service.

Validation

• cargo fmt --check
• cargo clippy --all-targets --all-features -- -D warnings
• cargo build --verbose --all-features
• cargo test --offline --locked --all-features
• Relevant Docker, service-integration, or documentation checks

Local commands used offline, locked dependencies. Independent ordinary parallel tests passed 180 cases, with one inherited transport diagnostic ignored.

An independent isolated upload-to-MCP run passed 74 assertions using real server/KC/RustFS/Qdrant services and a deterministic embedding double. Coverage includes PDF/DOCX uploads, storage-write origin, user/admin isolation, forged/replayed requests, identical-text file deletion, failure fences and no-KC standalone operation. An independent extension rerun passed 78 primary assertions covering actual provider embeddings, disk-backed restart and security cases, plus 83 separate fault-injection assertions; cleanup was verified.

Deployment and compatibility

Adds a reversible operation-state migration. KC integration is opt-in. Existing public upload paths remain facades over authenticated KC internal APIs.

Documentation

Documents the public/internal boundary, configuration, upload lifecycle and recovery limitations.

Checklist

• I added or updated tests for changed behavior, or explained why tests are not needed.
• I updated user-facing and API documentation where necessary.
• My commits follow the Conventional Commits specification.
• Every commit includes a Signed-off-by trailer (git commit -s).

AI assistance:

• Tool: Codex and Hermes.
• Model: implementation and independent review used gpt-6.1-sol through shaide.
• Used for: implementation, tests, independent review and integration verification.
• Human verification: done.