fix: schedule weekly advisory after the closed UTC cutoff

[Pigbibi]

Summary

• Run weekly review and public publication on Sunday, after the weekly UTC cutoff is fully closed; preserve the existing 12:30/13:00 UTC clock times
• Add Saturday/Sunday, month/year boundary, authentic-source freshness, and exact workflow schedule regression coverage
• Update existing English/Chinese design and roadmap documents with the input-publication incident, bounded recovery stages, and remaining upstream identity constraints

Scope

Exactly eight files. The closed-period helpers, freshness/provenance gates, scoring, frontend code, and upstream data remain unchanged. This PR contains no RSCP or PETR changes and does not import generated data.

The latest upstream theme artifact remains a separate review candidate. This schedule fix does not establish that the upstream publication gaps are resolved or that final recommendations must become nonzero.

Verification

• Regression tests before cron edit: 2 expected schedule failures, 9 passes
• Focused workflow/build/time-contract suite: 34 passed
• Complete existing QAR suite: 387 passed (Python 3.12, project-declared pytest >=8)
• Whitespace checks clean
• Exact eight changed paths and Git blob hashes verified against base 0c96b62; prior docs: human-readable README ordering and governance file cleanup #77 documentation changes preserved

Trigger boundary

Current publication and frontend-republish workflows have no push trigger. This branch/PR invokes ordinary CI; no collection, AI request, manual workflow dispatch, or deployment was performed. A later scheduled public-publication run retains its existing report-generation and deployment behavior.

Draft for required-check review; merge remains a separate action.