Reduce scheduled search refreshes to twice monthly

[VatsalSy]

Change the search refresh schedule from daily at 04:00 UTC to the 1st and 15th of every month at 05:11 UTC (11 5 1,15 * *). This staggers the low-priority search refreshes under the approved organization-wide schedule reduction.

The change is limited to the cron entry and its adjacent schedule comment. Manual and event triggers, jobs, permissions, and publishing behavior are preserved.

Validation: YAML parsing, numeric cron range checks, semantic equality of the complete workflow after removing the schedule, byte equality outside the cron/comment edit, and git diff --check passed. No workflow was dispatched for validation. The repository-required lint check passed (0 errors, 3 existing warnings), and all 28 test suites / 214 tests passed.

Guarded CodeRabbit review is pending.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Essentials
• Run ID: 4a47d280-b3b8-4d63-afa8-a98bc75b6816

📥 Commits

Reviewing files that changed from the base of the PR and between d62fc8f and c48aa11.

📒 Files selected for processing: 1

• .github/workflows/update-search.yml

Included review availability: This review used your included allowance. 0 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 4 reviews per hour.

📜 Recent review details

🔇 Additional comments: 1

.github/workflows/update-search.yml: 1

5-5: LGTM!

📝 Walkthrough

The update-search workflow now runs on the 1st and 15th of each month at 05:11 UTC. Manual and push triggers remain unchanged.

Changes: Search update schedule

Layer / File(s)	Summary
Update schedule .github/workflows/update-search.yml	The scheduled run changes from daily at 04:00 UTC to 05:11 UTC on the 1st and 15th of each month. Manual and push triggers remain unchanged.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to c48aa

Automatic search refreshes now run on the 1st and 15th at 05:11 UTC instead of daily; manual and push updates remain available. The change is mergeable.

Pre-merge checks: 5

Passed checks: 5 passed

Check name	Status	Explanation
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly and concisely describes the main change: reducing scheduled search refreshes to twice monthly.

✨ Finishing Touches

✨ Simplify code

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

[comphy-bot]

comphy-bot review status for comphy-lab/comphy-lab.github.io#148 at c48aa114: completed

Review completed for this exact pull request head.

[comphy-bot]

Review: Reduce scheduled search refreshes to twice monthly

Reviewed exact head c48aa114ed8b693d58754a05915bc5a2ff8a1a8b (+1/-1 across one workflow).

No actionable findings. 11 5 1,15 * * schedules runs at 05:11 UTC on the 1st and 15th of every month, matching the updated comment and stated intent. The diff changes only that schedule entry and its adjacent comment; manual/push triggers and job behavior are unchanged.

Verification: inspected the complete changed patch and current peer-review evidence. Packet checks found no added conflict markers or trailing whitespace; the current-head build and PR hygiene checks succeeded. No PR code was executed and no workflow was dispatched. The intentionally reduced scheduled refresh frequency is not treated as a regression.