[AlxcBTW]

What

Runs the upstream sync every day (04:17 UTC) instead of every Monday. Only the cron line changes, plus the three places that said weekly (the workflow header, the README paragraph, one row in docs/dev/FORK.md).

Why: the launcher issue anyplaynet/launcher 233 asks for a build newer than upstream's last release. Upstream publishes no per-commit or nightly build (its Release workflow runs only on a v* tag push, and its Actions artifacts need a token), so the fork's nightly pre-release is the only fresh source. It tracks upstream as fast as the sync pull request is merged.

What daily does: the job still keeps one open sync pull request. When upstream has moved and nobody has pushed to the branch, it rebuilds the branch and force-pushes it, then dispatches the builds again; build.yml cancels the older dispatched run for the same pull request, so builds do not pile up. A branch with a person's commits is never rewritten. A day without new upstream commits does nothing. The cost is more CI runs (free hosted runners) and a PR that changes under a reviewer; if that is a problem, merge the open PR as soon as it is green and the next day starts a fresh one.

Tested

Not run: a schedule change cannot be dispatched. The job itself ran green on dispatch in #36.

Checklist

• Based on current main; no other open PR implements the same functions
• One topic per PR; follow-ups go in a new PR
• No comments in code except technical debt
• Unimplemented paths throw (NotImplemented_nid_no_patch); silent stubs are listed under Silent stubs in their library's technical debt file
• No notes, investigation .md files or images added to the repository
• New third-party code is a submodule built from source
• Generic behaviour, not specific to one title
• Depends on: none
• Fixes: none
• Unblocks: none
• GPUs tested: n/a
• AI-assisted: yes

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}