Agent Hub · Lovable Exit

Lovable Exit Check

Hermes Workflow · ops-portal-lovable-exit-agent

Idle

Loading readiness…

/lovable-exit OPERATOR REPORT — No run yet

Run result:No run yet

New migrations:Unknown

Schema changes:Unknown

Stop conditions:Unknown

Repo:—

AVAS target:iibplqgufsvkqfdejogh

Alignment:Phase 2 active — 14 items pending

Next action:Run the check first

LOVABLE EXIT — MIGRATION STATUS

10/24 items complete

Last run: No run yetCurrent phase: Phase 2 — Schema Migration

▶ Phase 2 active — AVAS target schema alignment pending June 16 M365 migrations

PHASE 1 — Prep Work3/4

[✓]Own Supabase project created

[✓]Supabase CLI installed and linked

[✓]All env vars documented and saved securely

[ ]pg_cron anon key replacement planned

PHASE 2 — Schema MigrationCurrent7/9

[✓]Gap tables applied

[✓]Gap columns applied

[✓]RLS policies applied

[✓]DB helper functions applied

[✓]Storage buckets created

[✓]Storage RLS applied

[✓]Auto-sync via Hermes active

[ ]June 16 migrations applied (M365 backup)

[ ]pg_cron recreated (at cutover)

PHASE 3 — Edge Functions0/3

[ ]All 53 functions deployed

[ ]All env vars set in AVAS target secrets

[ ]Webhook URLs updated in external services

PHASE 4 — Frontend Cutover0/3

[ ]VITE_SUPABASE_URL updated

[ ]VITE_SUPABASE_ANON_KEY updated

[ ]Auth redirect URLs updated

PHASE 5 — Verification0/5

[ ]Public report URLs tested

[ ]Quote signing flow tested

[ ]Partner portal tested

[ ]Halo sync tested

[ ]Email sending tested both brands

No run data yet — use Run Check above to run the first check.

Controlled Runner

Profile: ops-portal-lovable-exit-agent

Repo: /root/it-ops-portal

Prompt: predefined scan/control only

Safety Boundaries

No SQL, deploy, env, webhook, production, commit, push, or merge path is exposed to the runner.