docs(wiki): note log:read perm + entry presence/cooldown guard in reference pages

Sync the two canonical reference pages with this session's features: local-jwt-auth
gains the new log resource / log:read permission in the RBAC grid (links app-logs);
first-run-setup notes the one-car-one-ticket presence-loop/cooldown guard the admin
configures on a relay (links entry-double-press).

Claude-Session: https://claude.ai/code/session_01Xcm6ikLgGoCxxHrxtjkk5V
This commit is contained in:
2026-06-19 12:59:06 +02:00
parent 30e7fe85de
commit c0a775818b
2 changed files with 8 additions and 4 deletions
+5 -4
View File
@@ -8,10 +8,11 @@ updated: 2026-06-15
# First-Run Setup (device selection)
The admin install flow that makes the system **device-agnostic in practice**: on first run, an
admin adds **controllers** (each declaring its relays — entry/exit/both — and the entry-button
terminal) and then **readers/cameras/printers** bound to a controller relay, choosing from the
[[device-registry]] catalog and entering each device's connection config. There is **no lane** —
the pool-of-spaces model; see [[entry-exit-points]].
admin adds **controllers** (each declaring its relays — entry/exit/both — the entry-button
terminal, and the one-car-one-ticket guard: a presence-loop input or a cooldown, see
[[entry-double-press]]) and then **readers/cameras/printers** bound to a controller relay, choosing
from the [[device-registry]] catalog and entering each device's connection config. There is **no
lane** — the pool-of-spaces model; see [[entry-exit-points]].
> Implementation-derived (from `apps/server` + `apps/web`), not the source doc.