ranade-oss keeps automated upstream changes on a short leash

This fork's sync process chose review over convenience when a proposed change touched deployment and security-sensitive settings.

An automated upstream review looked at a proposed change, then deliberately merged nothing. The reason was not a technicality: the proposal affected the checks applied during production builds and the settings used to connect external services.

ranade-oss has treated those areas as protected because they sit close to the fork's security model and deployment design. The sync system can bring in only narrowly defined, low-risk changes automatically; anything that could alter those guardrails is held back for investigation. It also keeps validation, limited repair steps and final merge checks in place rather than treating an automated review as approval.

For legal teams assessing reliability, that restraint matters as much as a new feature: it reduces the chance that upstream convenience quietly changes how a deployed legal-AI system is secured.