docs: bring the wiki up to 5.0
The code moved from slots to users; the documentation had not. Two new
pages and a pass over what the change made wrong.
New:
- Upgrading to 5.0 — the one-way migration, what happens on the first
restart, entity IDs changing and what that costs automations, the
one-time unmanaged-code repair, and the restore-then-upgrade-again
path that strands recorder history.
- Managing guests and rentals — the three shapes this takes, and which
to pick. A recurring cleaner is a permanent user with a schedule
condition and needs no automation at all; a rental guest is a standing
user whose name and PIN rotate, which works because renaming is free;
add-and-remove is for when the count itself varies.
Updated:
- Services and Actions — add_user and delete_user were missing entirely.
- Custom Cards — lcm-user replaces lcm-slot (deprecated, still works),
addressing by user_entity_id or name, the remove action, and the new
add-user card.
- UI Strategies — the strategies generate user cards now, and an
add-user section. The strategy type and option names are unchanged.
- Blueprints, Tracking lock state change events — both take entity IDs
that all moved, and nothing rewrites an ID stored inside an
automation. Blueprints also gains "Finding a slot number", which the
repo's own BLUEPRINTS.md had and the wiki did not: three blueprints
ask for a number the interface deliberately never shows.
- Migrating from keymaster — reframed onto users. You name a person;
the slot number is chosen by reading the lock.
- Advanced Usage — its rental paragraph now points at the new page
instead of describing the slot-era approach.