ranade-oss puts the brakes on risky upstream changes
Rather than import a mixed bag of changes on faith, this fork has formally parked them until they can be tested safely in its own setup.
This is not a feature release. It is a clear risk decision: eight upstream changes were classified as deferred, with no production changes brought into ROSS.
The parked work includes database access controls, protections around prompts and legal citations, request validation, sign-in and deployment settings, storage and provider credentials, and an assistant-exploration interface. The common issue was fit: ROSS differs enough from upstream that adopting only part of a change could leave an incomplete or untestable result.
By recording those decisions, ranade-oss keeps its synchronisation queue moving without quietly accepting broad changes whose consequences it cannot yet verify.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?