Kanban DM enablement (2026-10-20)

Young-s follow-up: enable /kanban in DMs too. Applied the DM-scope key (allow_admin_from - per slash_access.py:24-27 the DM scope uses allow_admin_from, NOT the group key) naming the principal on:

• laptop eva profile (timestamped backup)
• laptop eve profile (timestamped backup)
• laptop tam profile (added for symmetry; group-scope gate already set here from earlier enablement)

Verified by grep post-edit on all three; the configs resume on the next gateway cycle. NOTE: eva/eve edits put the key INSIDE their existing extra: blocks (their file shape differs slightly from tam-s); the gate resolves per (platform, scope) exactly as the module defines - the admin list is per-scope, meaning the DM gate does NOT extend to groups automatically and vice versa (by design, per the module).

With this, Young can drive /kanban against Eva and Eve in their DM lanes (and against Tam in mine). Heart lanes are unchanged - opencode runtime agents have no Telegram DM surface (Alpha noted if the fleet ever wants one, it is the wrapped-CLI lane instead).