Tighten admin operator triage state and actions

[DevCalebR]

Summary

• unify the admin business board around a single derived triage state per business
• stop archived businesses from polluting active needs-attention queues and collapse secondary admin/founder tools by default
• replace vague operator CTAs with specific next actions and add focused tests for state, badges, and filter counts

Root cause

The admin home was composing multiple independent status systems at once: lifecycle status, onboarding confidence, latest issue state, proof badges, and readiness/filter logic. Those layers were not using the same precedence rules, so a single business could render as Live, Live with warnings, and Needs attention at the same time. Archived businesses also flowed through the same active attention logic.

Validation run

• npm run env:check ✅
• npm run preflight:providers ✅
• npm run typecheck ✅
• npm run lint ✅
• npm run test ✅
• npm run build ✅

Notes

• PR base is codex/fix-owner-invite-autolink so the diff stays scoped to this admin/operator cleanup commit.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
callbackcloser	Ready	Preview, Comment	May 29, 2026 6:25pm