vlog-daily-check

name	vlog-daily-check
description	Review daily vlog-pipeline production status using the repo MCP tools. Use when the user asks to check today's or yesterday's VPS generation鎯呭喌, whether a scriptgen or video run finished, what files were produced, what is still pending for upload, or whether production was idle on a specific date.

Vlog Daily Check

Overview

Use the repo MCP tools first, not ad hoc shell guesses. Always resolve relative dates like "today" and "yesterday" into exact dates before concluding anything.

Workflow

1. Confirm the date window.

• Use the current VPS or local date and state the absolute date explicitly, for example 2026-04-19.
• If the user says "鏄ㄥぉ" or "today", repeat the resolved date in the answer.

2. Check whether generation is currently running.

• Use mcp__vlog__.vlog_status.
• Use mcp__vlog__.vlog_progress when checking an active video run.
• If the user may mean simulation work rather than video work, also check mcp__mirofish__.sim_list.

3. Check recent production history.

• Use mcp__vlog__.vlog_history for recorded upload/run history.
• Use mcp__vlog__.vlog_logs for recent generation logs.
• Use mcp__vlog__.vlog_docker_logs when the API history looks stale or incomplete.

4. Verify actual files for the target date.

• Prefer checking container-internal paths with mcp__vlog__.vlog_ssh plus docker exec vlog-pipeline ....
• For scriptgen output, inspect /app/data/scriptgen.
• For MiroFish/video output, inspect /app/data/mirofish and /app/data/logs when needed.
• Filter by exact date using find ... -newermt 'YYYY-MM-DD 00:00:00' ! -newermt 'YYYY-MM-DD+1 00:00:00'.

5. Check upload readiness.

• Use mcp__uploader__.upload_list for pending queues.
• Use mcp__uploader__.upload_status for recent upload history when relevant.

6. Summarize clearly.

• Separate what definitely happened from what was not observed.
• If no files or logs exist for the target date, say that directly.
• Distinguish script generation from final video generation.
• Mention whether the evidence came from history, logs, file timestamps, or pending upload queues.

Standard Checks

Daily Generation Check

Run the smallest useful set first:

• mcp__vlog__.vlog_status
• mcp__vlog__.vlog_history
• mcp__vlog__.vlog_logs
• mcp__uploader__.upload_list

If those are inconclusive, inspect dated files inside the container with mcp__vlog__.vlog_ssh.

"Did Yesterday Finish?" Check

Use this when the user asks whether a run completed.

• Check vlog_status first.
• Check target-date file timestamps under /app/data/scriptgen or /app/data/mirofish.
• Check the tail of the relevant log.
• Answer in one of these forms:
  • completed
  • still running
  • no evidence of a run on <date>
  • scriptgen completed, but no video generation evidence

When History and Files Disagree

Prefer file timestamps and container logs over high-level history summaries. The history endpoints can lag behind or only represent one stage of the pipeline.

Output Style

Keep the answer short and operational:

• exact date checked
• whether generation happened
• whether it was scriptgen or video generation
• current queue or pending upload state if relevant
• one next action when useful