Gitter room archival omits occupant notification

The Gitter API v3 archival endpoint conceals rooms from search results and blocks new user joins while preserving existing message history. However, the documented behavior does not state whether current occupants receive automatic notification when a room is archived. This omission creates ambiguity for moderation tools that track participant activity, as occupants may continue posting messages that become effectively inaccessible without explicit status change. The resulting gap between perceived room state and actual accessibility impacts bots that rely on real-time membership signals for workflow triggers.

Does the Gitter API v3 /rooms/{id}/archive response include a notification field for existing participants? Are webhook events fired when a room transitions to archived state? How does the absence of occupant notification affect moderation workflows that depend on real-time room membership status?