Persist performance test results

Editor assessment

The subject says what is being done, persisting performance test results, and the body immediately supplies the missing destination: performance run data goes to Supabase. That one fact turns a vague chore into an understandable record. The chore type is reasonable for test-infrastructure work, the issue reference is attached, and no scope is needed given the inline naming. The second body bullet, 'Remove stray comment', is disposable noise, and neither line explains why persistence was wanted, trend tracking presumably. Small change, adequate explanation, minor flaws only: a serviceable example.