docs: update project docs, NC Talk guide, Tina persona, and gitignore

- CLAUDE.md: add new auth/onboarding files to directory map, update
  security section (JWT/bcrypt/invite details), expand recently completed
- README.md: fix Web UI auth description, add User Management section
- TODO__Agents.md: mark NC Talk docs and auth/onboarding complete,
  update Holly onboarding plan to reflect single-instance multi-user approach
- docs/NEXTCLOUD_TALK_BOT.md: complete guide — occ commands, nginx config,
  clarify incoming vs outgoing HMAC difference, multi-user note, full
  troubleshooting table
- home/holly/persona/tina/: flesh out all four persona files with real
  content (DCC name origin, metal music, reading, foster cats, Holly's profile)
- .gitignore: exclude home/**/auth.json, invite.json, profile.json

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

documentation/TODO__Agents.md

@@ -45,17 +45,19 @@ See `ARCH__Intelligence_Layer.md` for full design. Initial scope:
 - [ ] Target: markdown files from `~/DgrZone_Nextcloud/` and `~/OSIT_Nextcloud/`
 - [ ] Tag strategy: source path, date, topic tags from frontmatter or filename
 
-### [Channel] Nextcloud Talk integration — stabilize
+### [Channel] Nextcloud Talk integration ✅ Complete
 - NC Talk bot is implemented (`cortex/routers/nextcloud_talk.py`)
-- HMAC signing: sign `random + message_text` (NOT raw body) — already fixed
-- [ ] Test end-to-end after any Cortex restart
-- [ ] Document the bot registration process in `docs/NEXTCLOUD_TALK_BOT.md` (complete it)
+- HMAC: incoming uses `random + raw_body`; outgoing reply uses `random + message_text` — both correct
+- [x] Test end-to-end after any Cortex restart — confirmed working 2026-03-20
+- [x] Bot registration docs completed in `docs/NEXTCLOUD_TALK_BOT.md` — 2026-03-20
+- **Note:** Currently uses default user/persona only — per-conversation persona routing is a future enhancement
 
-### [Multi-user] Holly agent instance
-- Plan: run two separate Cortex instances, not multi-user in one service
-- Reverse proxy: `inara.dgrzone.com` → port A, `holly.dgrzone.com` → port B
-- [ ] Create `holly/` identity directory (parallel to `inara/`)
-- [ ] Second `docker-compose` service or separate systemd unit
+### [Multi-user] Holly onboarding
+- Multi-user is built into Cortex — single instance, multiple users under `home/`
+- `home/holly/persona/tina/` directory created from template (stub content — needs real persona files)
+- [ ] Send Holly's invite email: `python manage_passwords.py invite holly holly.danner@gmail.com`
+- [ ] Walk Holly through onboarding flow (`/setup/{token}` → persona creation)
+- [ ] Review and flesh out Tina's persona files (IDENTITY.md, SOUL.md, PROTOCOLS.md, USER.md)
 
 ---
 
@@ -79,9 +81,26 @@ See `ARCH__Intelligence_Layer.md`. Full design not yet started.
 - `cortex/routers/` already has pattern; add `gitea.py`
 - Gitea Actions (CI) for "run tests on push" — simpler than custom runner
 
-### [Channel] Google Chat integration
-- `cortex/routers/google_chat.py` already exists (stub?)
-- [ ] Review current state, complete or document gaps
+### [Auth] Session auth + persona onboarding ✅ Complete
+- bcrypt passwords stored in `home/{username}/auth.json`
+- JWT session cookies (HS256, 30-day expiry) — `auth_utils.py`, `auth_middleware.py`
+- Login/logout at `/login`, `/logout`
+- Invite tokens (72h, one-time-use) — admin generates via `manage_passwords.py invite <user> [email]`
+- Self-service onboarding: `/setup/{token}` (set password) → `/setup/persona` (create persona)
+- Multi-persona switcher in UI header — `/api/personas` endpoint
+- SMTP invite email — `noreply@oneskyit.com`, HTML + plain text body
+- CSS routing fix — `app.mount("/static")` must precede `app.include_router(ui.router)`
+- Committed: 2026-03-20
+
+### [Channel] Google Chat integration ✅ Complete
+See `cortex/routers/google_chat.py`. Committed: 2026-03-20
+- [x] JWT verification via `authorizationEventObject.systemIdToken` (audience = endpoint URL, issuer = accounts.google.com)
+- [x] Workspace Add-on event format: event type inferred from payload key (`messagePayload`, `addedToSpacePayload`, etc.)
+- [x] Response format: `hostAppDataAction.chatDataAction.createMessageAction.message.text`
+- [x] Session management, LLM pipeline, session logging — same pattern as NC Talk
+- [x] Nginx: `/channels/` prefix exposed without basic auth (covers all future channel integrations)
+- **Note:** Google Chat API now forces the Workspace Add-on framework — legacy standalone bot format is gone.
+  `{"text": "..."}` and `renderActions` do NOT work; `hostAppDataAction` is required.
 
 ### [Distill] Monitor first auto_distill_long run
 - Scheduled for ~April 1 at 04:00