Problem
The admin connections page's `Connection` interface includes `confidence: number | null`, and the API's `select()` returns the column, but the table only renders Edge/Kind/Why/Status/Review/Actions columns — `confidence` is fetched and typed but never rendered anywhere.
Impact
`confidence` is the AI model's own self-reported confidence score for each generated connection — directly useful context for a moderator deciding whether to approve, flag, or retire a low-confidence edge. Right now that signal is silently dropped on the floor even though it's already in the payload, so moderators have no way to sort/prioritize review by how confident the model was.
Location
`app/admin/connections/page.tsx:18` (interface field), table rendering at lines 96-104 (no corresponding column)
Suggested fix
Add a "Confidence" column to the connections table (e.g. rendered as a percentage or a small bar/badge), and optionally allow sorting/filtering the list by it to help triage the lowest-confidence connections first.
Problem
The admin connections page's `Connection` interface includes `confidence: number | null`, and the API's `select()` returns the column, but the table only renders Edge/Kind/Why/Status/Review/Actions columns — `confidence` is fetched and typed but never rendered anywhere.
Impact
`confidence` is the AI model's own self-reported confidence score for each generated connection — directly useful context for a moderator deciding whether to approve, flag, or retire a low-confidence edge. Right now that signal is silently dropped on the floor even though it's already in the payload, so moderators have no way to sort/prioritize review by how confident the model was.
Location
`app/admin/connections/page.tsx:18` (interface field), table rendering at lines 96-104 (no corresponding column)
Suggested fix
Add a "Confidence" column to the connections table (e.g. rendered as a percentage or a small bar/badge), and optionally allow sorting/filtering the list by it to help triage the lowest-confidence connections first.