BlueMapWebChat (BMWC)

## 4.6.3

- Added optional read-only administrator group-chat content audit. Explicit accounts listed in `private-chat-super-admins` can open group-chat message bodies from the administrator metadata view only when `group-chat.admin-audit.enabled: true`.
- Group-chat audit access does not require room membership and does not join the room, mark messages read, change unread counts, send messages, upload files, hide messages, or modify membership. Ordinary ADMIN/MODERATOR roles do not gain content access automatically.
- Every group-chat audit page read is recorded as `admin.group-audit-read` with the actor, room ID, pagination position, limit, and returned count. Message bodies are not copied into the audit log.
- Refreshed the bundled 4.6.3 configuration comments to describe the current update-check, cross-server DM, relay, read-status, and administrator-audit behavior. Existing `config.yml` setting values are not rewritten; only unchanged older bundled comment blocks are refreshed, while custom comments are preserved.
- Fixed DM/group native video and audio playback during live message/status refreshes. Private-chat message lists now reconcile by stable message key like public chat: existing message/media DOM stays mounted, new messages are inserted without rebuilding the conversation, and delivery/read metadata updates in place. Active playback therefore continues from its current position. Leaving or switching a private conversation now hard-discards that conversation's message/media DOM and private media-open state; re-entering starts from the unopened click-to-load state (or a newly created non-playing media element when click-to-load is disabled), so no previous player is reused or auto-resumed.
- Fixed pinned-message source metadata in the detached pinned-message window. Clickable Web/Game DM targets and relay server badges now use the same transparent/buttonless metadata styling as normal chat instead of falling back to browser default button chrome.

### Configuration added in 4.6.3

Compared with the bundled 4.6.2 defaults, 4.6.3 adds only:

```yaml
group-chat:
  admin-audit:
    enabled: false
```

The configuration review marker also changes to:

```yaml
config-version: "4.6.3"
```

Both gates are required to open group-chat bodies:

```yaml
private-chat-super-admins:
  - "ExactMinecraftNameOrUUID"

group-chat:
  admin-audit:
    enabled: true
```

The existing `direct-message.admin-audit.enabled` switch remains independent and continues to control only DM body auditing.