Open-source publish: clean-room export of Context Broker

[rmdevpro]

Goal

One-time open-source publish of Context Broker via a separate public repo
(jmorrissette-rmdc/ContextBroker) that receives a curated, fresh-history
snapshot — no old commits, no issues/PRs carried over. This private repo
(rmdevpro/context-broker) remains the source of truth with full history.

docs/ and deployment-coupled tests are left behind (not moved). Everything
that crosses the boundary is fixed in place so the app encodes nothing
unpublishable.

Checklist

• Inventory sweep — authoritative include/exclude/scrub manifest (PII,
  internal identifiers, deployment-coupled tests, junk/dumps, secrets).
• Build export tree in ContextBroker-public staging dir; exclude docs/,
  deployment-coupled tests, dev-dump/junk (all_code.txt, token, user_id,
  parsed_*.txt, test_capabilities.txt, recent_turns.md, parse_*.py).
• Scrub crossing files — genericize PII/[Joshua26] in config/alerter.yml,
  example facts in config/prompts/memory_extraction.md, code comments
  (R5-m5, Rogers Fix 2), packages/mem0-fork/pyproject.toml description.
• OSS hygiene — add root LICENSE (Apache-2.0), packages/mem0-fork/LICENSE
  + NOTICE preserving mem0ai attribution, tighten .gitignore.
• Init public repo — git init, single clean initial commit, no private
  history present.
• Independent review by ctx-reviewer session; address findings, re-review
  until pass.
• Verify — token grep = 0 private hits, single commit, docker compose up
  health = 200, self-contained tests pass.
• Push — only after explicit user go-ahead.

Out of scope

• Rewriting deployment-coupled tests to run standalone (left behind for now).
• Cleaning this private repo's own history/docs (separate housekeeping).