docs: update GitHub audit

Author: Cuica20

reports/github-audit.md

@@ -5,30 +5,30 @@ Generated: 2026-09-06 (America/Lima)
 ## Environment
 
 - Git: `2.55.0.windows.5`
-- GitHub CLI: not installed or not available on `PATH`; `gh --version` and `gh auth status` could not run.
-- Git identity in the parent workspace: `DSRP Ops <panel@local>`.
+- GitHub CLI: installed and authenticated as `Cuica20` through the system keyring.
+- GitHub token scopes verified: `gist`, `read:org`, `repo`, `workflow`.
+- Viewer role for `DataScienceResearchPeru/ai-community`: `ADMIN`.
 
-## Detected repository
+## Detected repository and organization
 
-- `https://github.com/DataScienceResearchPeru/ai-community.git` responded successfully to `git ls-remote` but has no refs, indicating an empty repository at audit time.
-- The local clone was created only after the read-only audit, on branch `feature/community-foundation`.
-
-## Unknown until GitHub CLI is available
-
-- Authenticated user and token scopes
-- Organization membership and role
-- Related DSRP repositories
-- Existing teams and permissions
-- Repository plan and branch-protection capabilities
+- Repository: `DataScienceResearchPeru/ai-community`.
+- Visibility: private. Description and topics are empty.
+- Issues are enabled; Discussions are disabled.
+- Default branch: `feature/community-foundation`; `main` does not yet exist.
+- The pushed foundation commit is `5551e18` on `origin/feature/community-foundation`.
+- Organization: `DataScienceResearchPeru`, plan `free`, 106 public repositories and 6 private repositories.
+- Existing team: `dsrp-github-team` (closed). The proposed `community`, `mentors`, and `maintainers` teams do not exist.
+- Related repositories include `AI_Curriculum`, `Semilleros-DSRP`, `Retos`, `GithubParticipantes`, `rules`, and many public learning repositories.
 
 ## Risks
 
-- GitHub administration cannot be safely inspected or automated without `gh` authentication.
-- Existing GitHub settings may exist even though the repository is empty; do not overwrite them.
+- GitHub's API rejects branch protection for this private repository on the Free plan. It must be public before protections for `main` can be applied.
+- Changing public visibility exposes all current and future repository content. Review the branch before making that change.
+- Making `main` the default branch requires first creating it from the reviewed foundation commit. The existing feature branch should be retained until the transition is confirmed.
 
 ## Recommendations and proposed actions
 
-1. Install GitHub CLI and run `gh auth status`.
-2. Run `scripts/github/audit-github.sh` with `GITHUB_ORG=DataScienceResearchPeru`.
-3. Review `scripts/github/*.sh --dry-run` before any remote change.
-4. Confirm the organization plan before designing an exact branch protection rule payload.
+1. Review the foundation branch, then create `main` from commit `5551e18` and set it as the default branch.
+2. Change the repository to public, add the approved description and topics, and enable Discussions.
+3. Create the three proposed teams only if desired; do not modify `dsrp-github-team`.
+4. Once public, recheck branch-protection availability and apply the reviewed rule for `main`.