A boost to a gated connection (admin1/admin_majority/admin_consensus) now holds with awaiting_publish_approval on the same publish-phase poll the publish route uses, instead of executing the reblog. The holder re-invokes amplify after the pass (hold-and-retry: no durable amplify queue exists and the poll-close transaction must not do network I/O). Unset/auto connections behave exactly as before; the route answers 202 on hold, 200 on execute. Adds amplify-governance IT suite (3 live-DB tests). |
||
|---|---|---|
| .. | ||
| api | ||
| archive-bot | ||
| media-worker | ||
| scheduler | ||
| web | ||