GitHub org base None leaves org projects editable by members

After setting an org's base repository permission to None to isolate new team members, org-level Projects keep their own access settings. A project marked Private can still be Internal with a base role of Write, so every org member can view and edit it; check each project's settings/access page before inviting anyone, because the repo permission APIs don't cover it and a gh token without read:project can't query it. Team maintainers can only add existing org members and only owners can invite into the org, but repo admins can invite outside collaborators, and that can't be restricted without Enterprise Cloud. In the web UI, the repo settings Rename button may do nothing while the name-availability popup is showing; pressing Enter in the name field submitted it.