Dashboard Automation Bridge

Date: 2026-06-28 Status: implemented

Problem

The dashboard was previously a static hand-updated artifact. Chowmes daily and weekly CI cron jobs generated reports and updated the live SQLite/runtime artifacts, but Vercel served only whatever was committed to GitHub.

That meant daily and weekly CI runs did not automatically update the dashboard.

Decision

Use Chowmes as the executor and GitHub/Vercel as the static publishing path:

Hermes cron
  -> daily or weekly CI runner
  -> update ci.sqlite and report artifacts
  -> export dashboard-ready static files
  -> commit and push to algolia-competitive-intelligence GitHub repo
  -> Vercel auto-deploys

Do not make Vercel connect directly to the VPS SQLite database in v1.

Implementation

• Added ci_dashboard_publish.py.
• Added publish-dashboard.py.
• Daily and weekly cron wrappers now call the dashboard publisher after successful CI runs.
• The publisher exports:
• apps/dashboard/public/index.html
• apps/dashboard/public/data/latest.json
• latest-daily.md
• latest-weekly.md
• archived report markdown files
• Added a write deploy key named chowmes-dashboard-publisher to the GitHub repo.
• Cloned the repo into Chowmes at /opt/data/apps/algolia-competitive-intelligence.
• Updated live workspace skill code and /opt/data/scripts/ cron wrappers.

Verification

• Local build passed: npm run dashboard:build.
• Local tests passed: 20 passed.
• Live weekly renderer smoke passed.
• Live weekly wrapper smoke generated 2026-06-28-weekly artifacts.
• Chowmes successfully committed and pushed dashboard updates to GitHub.
• Vercel production showed the latest 2026-06-28-weekly dashboard update.
• Local vault dashboard artifact was synced with archive/data support.

Current Automation Contract

Daily:

competitive-research-daily cron
  -> /opt/data/scripts/competitive-research-daily.sh
  -> daily-research-run.py
  -> publish-dashboard.py
  -> GitHub push
  -> Vercel deploy

Weekly:

competitive-research-weekly cron
  -> /opt/data/scripts/competitive-research-weekly.sh
  -> weekly-review.py
  -> publish-dashboard.py
  -> GitHub push
  -> Vercel deploy

Remaining Risk

If GitHub push or Vercel deploy fails, CI reports still generate and Telegram still receives the report, but the public dashboard may lag. The next improvement should add an explicit dashboard publish health check and Athena/CI Bot alert.