ranade-oss fixes a release check that was reading yesterday's legal-source report
A small workflow correction makes production qualification judge the report it just generated, rather than silently falling back to an older one.
The issue was not in the legal-source checks themselves, but in the handoff between them. A formatting quirk in the automated release workflow distorted the report reference, so the final completion check did not receive it and instead used a stale July report.
ranade-oss has made that handoff unambiguous, added a regression test to prevent the same workflow shape returning, and refreshed the governed release record. The existing safeguards still fail closed if legal-source evidence or release-readiness requirements are missing. Publishing remains a separate, deliberate step.
The team also ran the relevant application, security, legal-source, website and production-build checks around the fix.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?