fix(ci): Correct core-flow validation report schedule

[LucasSantana-Dev]

Summary

• fix core-flow-validation-report.yml schedule expressions that caused push-time workflow load failures (0-job runs)
• keep daily and weekly reporting cadence with explicit, valid cron entries
• update cadence mapping logic and docs/changelog to match

Changes

• .github/workflows/core-flow-validation-report.yml
  • daily: 20 3 * * *
  • weekly: 25 3 * * 1
  • weekly cadence detection updated to 25 3 * * 1
• README.md
  • documented daily/weekly UTC schedule for report workflow
• CHANGELOG.md
  • added fix note for workflow load failure

Validation

• npm run lint
• npm run type-check
• npm run test
• npm run build
• local YAML parse check for core-flow-validation-report.yml

Why this PR

Main got an immediate red run after #464 merge (.github/workflows/core-flow-validation-report.yml, 0s, no jobs). This patch restores valid workflow loading while preserving the gate-reporting behavior.

Summary by CodeRabbit

• Chores
  • Updated report generation schedule to run daily with dedicated weekly reports on Mondays instead of the previous weekday/weekend pattern.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
siza-web	Ready	Preview, Comment	Mar 12, 2026 3:24am

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 9b187282-2940-4348-9ff3-1ec066c2d245

📥 Commits

Reviewing files that changed from the base of the PR and between b8a5416 and af8631f.

⛔ Files ignored due to path filters (2)

• CHANGELOG.md is excluded by !**/*.md
• README.md is excluded by !**/*.md

📒 Files selected for processing (1)

• .github/workflows/core-flow-validation-report.yml

---

Walkthrough

Updated GitHub Actions workflow scheduling configuration in core-flow-validation-report.yml by modifying cron expressions for scheduled triggers and adjusting the cadence detection logic to use a different Monday schedule ("25 3 * * 1" instead of "20 3 * * 1").

Changes

Cohort / File(s)	Summary
Workflow Scheduling Configuration .github/workflows/core-flow-validation-report.yml	Modified cron schedule expressions and updated cadence detection condition to reference new Monday schedule; changes affect when the report generation workflow is triggered and how its cadence is determined.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• feat(web): Add core flow validation report endpoint and workflow #464 — Directly modifies the same workflow file, updating schedule cron expressions and cadence-detection logic in core-flow-validation-report.yml.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'fix(ci): Correct core-flow validation report schedule' directly describes the main change: fixing the core-flow validation report schedule in CI workflows.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/core-flow-validation-report-cron

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[LucasSantana-Dev]

Review (Mandatory)

Findings

• None blocking. No functional regressions identified in this diff.

Assumptions / Open Questions

• Assumption: GitHub Actions treats no-job runs here as workflow-load validation failure; this change corrects schedule parsing and preserves intended daily+weekly cadence.
• Residual risk: low. Weekly report now runs 5 minutes after daily on Mondays by design.

Summary

• Diff is scoped and correct for the incident: workflow schedule/cadence mapping fix + README/CHANGELOG alignment.

[github-actions]

Project Scorecard

Scorecard: 84/100 (B)
────────────────────────────────────────
  security: 100/100 (A)
  quality: 80/100 (B) — 1 violations
  performance: 67/100 (D) — 1 violations
  compliance: 75/100 (C) — 1 violations
  dependency: 100/100 (A)

Recommendations:
  - Increase test coverage to meet the 80% threshold
  - Extend log retention to at least 90 days for compliance

[LucasSantana-Dev]

Review (Mandatory)

Findings

• None blocking. No functional regressions identified in this diff.

Assumptions / Open Questions

• Assumption: GitHub Actions treats zero-second no-job runs here as workflow-load validation failure; this change corrects schedule parsing and preserves intended daily+weekly cadence.
• Residual risk: low. Weekly report now runs 5 minutes after daily on Mondays by design.

Summary

• Diff is scoped and correct for the incident: workflow schedule/cadence mapping fix plus README/CHANGELOG alignment.