docs: document hive-chat room auto-creation in Matrix Space (follow-up to #1452)

This commit is contained in:
lexis 2026-06-06 08:00:29 +02:00 committed by mara
commit 6afaf03864

View file

@ -131,15 +131,26 @@ into it. This gives the operator a single Space in FluffyChat or any
Matrix client that groups all agent-to-agent + operator rooms in one Matrix client that groups all agent-to-agent + operator rooms in one
place. place.
**State**: the room ID is persisted to The sweep also provisions a default **`hive-chat` room** as an
`/var/lib/hyperhive/matrix/space-room-id` (mode `0600`, root-owned). `m.space.child` of the Space. Joining a Space doesn't auto-join
This path is **outside** every agent state dir and is NOT deleted by child rooms — the explicit room entry ensures the operator and every
`nixos-container destroy --purge` — the Space survives full agent agent can find a common chat room without manual setup. Room join is
purges and is reused on re-provision. restricted (any Space member including the operator can join; agents
are explicitly invited). Room version pinned to 10 for the restricted
join floor.
**Idempotent**: if the file exists and is non-empty, the Space is **State**: both room IDs are persisted to `/var/lib/hyperhive/matrix/`
considered already created. Delete the file to force re-creation (e.g. (mode `0600`, root-owned):
after a homeserver wipe). - `space-room-id` — the Space itself
- `chat-room-id` — the `hive-chat` room
These paths are **outside** every agent state dir and are NOT deleted by
`nixos-container destroy --purge` — both survive full agent purges and
are reused on re-provision.
**Idempotent**: if the files exist and are non-empty, the Space and
room are considered already created. Delete the files to force
re-creation (e.g. after a homeserver wipe).
## Configuration tuning ## Configuration tuning