docs: v1.0.0 — full documentation update

- ROADMAP.md: mark all v0.9.8–v0.9.10 items shipped; Phase 4
  accountability features complete; v1.0 criteria all met; update to
  reflect current state as of v0.9.10
- DEPLOYING.md: add SMTP/email section, ENCRYPTION_SECRET_KEY entry,
  fix OPENAI_MODEL default (gpt-4o → gpt-4o-mini), add pocketveto.org
  reference
- UPDATING.md: replace personal git remote with YOUR_GIT_REMOTE
  placeholder for public deployability
- ARCHITECTURE.md: add member_scores table, alignment API, LLM Batch
  API, email unsubscribe, bill tab UI, topic tags constant, Fernet
  encryption pattern, feature history through v0.9.10

Authored by: Jack Levy

UPDATING.md

@@ -9,7 +9,7 @@ How to push new code from your development machine and pull it on the production
 The workflow is:
 
 ```
-Local machine  →  git push  →  git.jackhlevy.com  →  (pull on server)  →  docker compose up --build -d
+Local machine  →  git push  →  YOUR_GIT_REMOTE  →  (pull on server)  →  docker compose up --build -d
 ```
 
 You develop locally, push to the Gitea remote, then update the production server — either manually over SSH or via an automated webhook.
@@ -42,7 +42,7 @@ On the server, clone from your Gitea instance:
 ```bash
 ssh user@YOUR_SERVER_IP
 cd /opt                           # or wherever you want to host it
-git clone https://git.jackhlevy.com/jack/civicstack.git
+git clone https://YOUR_GIT_REMOTE.git
 cd civicstack
 ```
 
@@ -54,7 +54,7 @@ If your Gitea repo is private, create a **deploy token** in Gitea:
 Store credentials so `git pull` doesn't prompt:
 ```bash
 # Using a personal access token stored in the URL
-git remote set-url origin https://YOUR_TOKEN@git.jackhlevy.com/jack/civicstack.git
+git remote set-url origin https://YOUR_TOKEN@YOUR_GIT_REMOTE.git
 ```
 
 Verify: