ranade-oss puts a hard stop on automatic upstream adoption

A proposed sync records what has changed upstream, but refuses to carry sensitive changes into ROSS without a decision.

Rather than treating synchronization as a green light, ranade-oss is using it as a disciplined review checkpoint. The branch remains unmerged while it identifies changes that could affect how ROSS handles access, data, and reviewed legal sources.

The held-back areas include:

identity, multi-factor sign-in, and project-sharing changes that could alter access to production data;
database and migration work with knock-on security implications;
editable workflow changes that could weaken reviewed-source provenance;
a Word add-in workspace, which ROSS does not offer;
deployment and dependency changes that need separate review.

One future workflow-hardening item is also parked until its underlying redesign exists. The useful result is visibility into upstream drift without quietly changing a legal product's governance boundaries.