Problem
POST /api/plugins/hypermultimedia/:documentId requires a verified user (apps/hocuspocus.server/src/api/routers/hypermultimedia.router.ts:30-36). The controller then spends that user on the private-document and read-only gates.
A service-role caller has no user. So an automated media upload has to create a real account first, and a failed cleanup leaves that account behind.
What to decide
Whether a service-role bearer may skip the user requirement on a public, unlocked document. The gate here is about access, not about identity.
Acceptance
Notes
A service-role write carries the operation, never a person. Do not solve this by minting a bot user row.
Problem
POST /api/plugins/hypermultimedia/:documentIdrequires a verified user (apps/hocuspocus.server/src/api/routers/hypermultimedia.router.ts:30-36). The controller then spends that user on the private-document and read-only gates.A service-role caller has no user. So an automated media upload has to create a real account first, and a failed cleanup leaves that account behind.
What to decide
Whether a service-role bearer may skip the user requirement on a public, unlocked document. The gate here is about access, not about identity.
Acceptance
Notes
A service-role write carries the operation, never a person. Do not solve this by minting a bot user row.