createPublishingCredentialAccessor is execution-fenced (Temporal contexts only) — the API-process amplify route threw EXECUTION_CREDENTIAL_FENCE. Use the established PgConnectionStore+vault accessor instead (same trust level as the archive amplify route's bot-token path). |
||
|---|---|---|
| .. | ||
| api | ||
| archive-bot | ||
| media-worker | ||
| scheduler | ||
| web | ||