docs: purge OpenClaw/Hans specifics from core design

Portability audit — all platform-specific concerns moved to adapter layer:

- Gate Approval UX (Resolved Mechanics): rewritten as platform-agnostic.
  Core: runner writes gate_pending, calls notify_adapter.send(), polls
  blackboard for gate_approved. Universal path: agency CLI writes directly
  to blackboard. Adapter handles its own inbound response bridge internally.

- pending_gates.json removed from core directory structure and runner
  responsibilities — adapter-internal state, not a core concern.

- 'User → Hans → team_runner.start()' → 'User → team_runner.start()'
  Core has no dependency on a specific caller.

- 'notify_adapter.send(...to Andrew via Hans)' → 'notify_adapter.send()'
  throughout design.md and buildspec.md.

- anthropic.py description: 'via OpenClaw or direct API' → 'direct API'
  (anthropic adapter never goes via OpenClaw)

- Output/review decision: 'Hans messages Andrew' → 'notify_adapter.send()'
- Run visibility decision: 'Andrew via Hans' → 'via notify_adapter.send()'
- Decisions log: gate approval and visibility entries rewritten accordingly

Adapter layer correctly unchanged:
  adapters/notify/openclaw.py — OpenClaw-specific, owns its inbound bridge
  adapters/runtime/openclaw.py — OpenClaw sessions_spawn, correctly isolated
  team.yaml example config — adapter selection is config, not core

docs/buildspec.md

@@ -40,7 +40,7 @@ agent-teams/
 │   │   ├── notify.py        — abstract notification interface
 │   │   └── runtime.py       — abstract agent runtime interface
 │   ├── llm/
-│   │   ├── anthropic.py     — Claude via OpenClaw or direct API
+│   │   ├── anthropic.py     — Claude via direct Anthropic API
 │   │   ├── openai.py        — GPT / o-series
 │   │   └── ollama.py        — local models
 │   ├── vcs/
@@ -74,8 +74,6 @@ agent-teams/
 ├── runs/                    — runtime state, one subdir per run_id
 │   └── .gitkeep
 │
-├── pending_gates.json       — live file: gates currently awaiting approval (written by runner, read by Hans)
-│
 └── README.md
 ```
 
@@ -387,7 +385,7 @@ t5:
 ### 1. Run Kickoff
 
 ```
-User → Hans → team_runner.start(goal, config)
+User → team_runner.start(goal, config)  # via CLI or any caller
   → generate run_id
   → init blackboard (create runs/<run_id>/blackboard.db)
   → build T1 brief (goal_anchor = goal, retry_budget from config)
@@ -442,7 +440,7 @@ spawn T4 with brief
 ```
 runner reaches configured gate (e.g. t2_synthesis)
   → write event(gate_pending, detail={tier, summary, what_happens_next})
-  → notify_adapter.send(tier summary to Andrew via Hans)
+  → notify_adapter.send(tier summary + gate context)
   → halt: poll blackboard for gate_approved or gate_rejected
 
   gate_approved:
@@ -490,11 +488,11 @@ T1 completes integration
 7. `core/escalation.py` — retry + failure routing logic (called by tiers, not runner centrally)
 8. `adapters/runtime/openclaw.py` — wire up sessions_spawn + personality injection
 9. `adapters/runtime/claude_code.py` — coding agent runtime, personality via --system-prompt
-10. `core/team_runner.py` — full run lifecycle: spawn loop (monitors briefs table for `status=pending`, calls runtime_adapter.spawn()), gate logic (gate_pending halt, writes pending_gates.json, gate_approved/rejected resume), path amendment monitor, T3 mesh timeout → T2 escalation, T1 failure + terminal escalation only
+10. `core/team_runner.py` — full run lifecycle: spawn loop (monitors briefs table for `status=pending`, calls runtime_adapter.spawn()), gate logic (gate_pending halt, calls notify_adapter.send(), polls for gate_approved/rejected resume), path amendment monitor, T3 mesh timeout → T2 escalation, T1 failure + terminal escalation only
 11. `cli/agency.py` — run, watch, inspect, approve, reject, pause, resume; `watch` tails blackboard events and renders live log; `inspect` renders run tree
 12. `prompts/` — fallback tier prompts (used when no agent_personality set)
 13. `adapters/vcs/github.py` — PR creation + branch management
-14. `adapters/notify/openclaw.py` — Hans notification; used for gate surfaces (tier summary to Andrew)
+14. `adapters/notify/openclaw.py` — OpenClaw notification adapter; bridges gate summaries and run events to the operator via OpenClaw; manages its own inbound response state for gate approval routing
 15. `config/team.yaml` — example config with full visibility block
 16. `README.md` — how to run, how to add adapters, how to extend the roster; include `agency` CLI reference