Fix daily-log workflow change detection for newly generated files

[Copilot]

daily-log runs were completing successfully but often ended with No changes even when a new daily markdown file was generated. The workflow’s change check only inspected unstaged diffs, so untracked logs/... files were missed.

• What changed

  • Commit gate now checks staged changes
    • Stage logs before evaluating whether there is anything to commit.
    • Switch the condition from unstaged diff to cached diff.
  • Commit flow remains unchanged after detection
    • Bot identity, commit message format, and push behavior are unchanged.

• Why this addresses the issue

  • New files are untracked until staged; by staging first and checking --cached, the workflow correctly detects fresh daily log outputs.

- name: Commit if changed
  run: |
    git add logs
    if git diff --cached --quiet; then
      echo "No changes"
      exit 0
    fi
    git config user.name "github-actions[bot]"
    git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
    git commit -m "chore(log): daily KiriMonoLog $(date -u +'%Y-%m-%d')"
    git push

[CyberYui]

fix auto problem