Updated the command-center iteration automation from read-only audit posture to fix-first execution posture. The active prompt now requires reversible internal fixes, live connector checks, and continued improvement of the daily_ops_events spine.
Implemented the live command-center intake lane. The app now reads Microsoft Graph Outlook messages and CallRail calls, normalizes them into dailyOpsEvents, and renders a narrow Today's Intake Exceptions panel in the dashboard. The panel is designed to reduce overwhelm by showing current action clusters instead of broad connector placeholders.
Files changed for this slice include src/lib/adapters/outlook-callrail-daily-ops.ts, src/lib/dashboard-data.ts, src/components/command-center.tsx, src/lib/mock-data.ts, README.md, .env.example, and the automation prompt at /Users/samaguiar/.codex/automations/command-center-iteration-loop/automation.toml. The prior staged daily_ops_events contract and tests remain part of the working change set.
Live source reads verified: Microsoft Graph app-only read worked for sam@kylawoffice.com, and CallRail API read worked against the Sam Aguiar Injury Lawyers account. The local command-center API at http://127.0.0.1:3007/api/dashboard-data returned mode=live with data.dailyOpsEvents=8. The UI intentionally shows the top 6 events to keep the decision lane compact.
Local app surface verified: http://127.0.0.1:3007 is running with live credentials loaded. Desktop browser QA confirmed the Today's Intake Exceptions panel renders with Outlook plus CallRail evidence. Mobile browser QA at 390x844 confirmed the new panel renders and has no horizontal overflow.
Hosted deploy was not performed. The sail-command-center repo already contained broad unrelated dirty changes from other agents. Deploying from that tree would risk shipping changes outside this session. A future hosted deploy should isolate this slice in a clean branch or deployment package first.
npm test passed: 10 files, 35 tests. npm run lint passed. npm run build passed with the same pre-existing Turbopack NFT warning tied to connector-store/source route tracing. Automation TOML parsed successfully after the prompt update.
Current blocker: hosted deployment safety, not source credential access. The app-runtime Graph and CallRail reads work locally.
Rollback path: revert the files changed in this slice and restore the previous automation.toml prompt from file history or the prior memory entry. No public site, paid ads, client-facing sends, DNS, or production destructive changes were made.
Best pickup is to isolate this command-center slice from the unrelated dirty tree, then deploy it to the protected hosted command-center endpoint. After that, wire the stale marketing/mobile overflow follow-up separately, since the new intake panel itself passed mobile QA.
Continue from the 2026-06-15 follow-up memory entry for command-center-iteration-loop. Do not repeat the read-only audit. Start by checking the dirty sail-command-center tree, isolate the Outlook plus CallRail dailyOpsEvents changes into a clean branch or deployment package, rerun npm test, npm run lint, npm run build, and browser QA, then deploy only if the package contains this slice and no unrelated agent changes.