Objective

Build Connector OS v1 for sail-command-center using the current connector registry as the source contract. Add persistence for connectors, connector_accounts, sync_runs, connector_artifacts, and connector_events; wire cron to store snapshots; surface health/freshness/blockers in the dashboard; live-validate what credentials allow.

Completed

• Added server-side Connector OS file store at src/lib/connector-store.ts.
• Added dashboard projection at src/lib/connector-os.ts.
• Added authenticated read endpoint GET /api/connectors.
• Updated GET /api/cron/connectors to persist snapshots after Authorization: Bearer $CRON_SECRET.
• Added Connector OS dashboard panel with persistence status, current/blocker/manual/event counts, top connector rows, and blockers.
• Extended env contracts in .env.example and render.yaml.
• Updated architecture, database schema, connector linking docs, and README.

Live Validation

• LITIFY_ORG reachable through Salesforce CLI.
• Connector OS local snapshot persisted to .data/connector-os-store.json with 27 connectors, 20 current/authenticated or available, 3 needs_login, 4 manual_capture, 54 persisted sync runs after two local runs.
• Vercel app connector listed 4 team projects.
• Direct probes confirmed Vercel, Render, GitHub, Notion, and Firecrawl availability in the prior/continuing run.
• Litify report hygiene audit generated /Users/samaguiar/Documents/Codex/connector-os-report-hygiene-2026-05-28/report_hygiene_summary.md.

Verification

• npm test passed: 7 files, 25 tests.
• git diff --check passed.
• tsc, next build, and next dev hung locally with no diagnostic output, matching the earlier local Next/TypeScript hang pattern. No background sessions were left running.