The scanner still masks the repository owner's public GitHub handle when it names a sibling repository of the same owner, e.g. <owner>/<sibling> written in a record of <owner>/<repo>. isOwnRepoSlug (internal/adapter/scanner/identity.go) exempts the owner only in the repository's own owner/repo slug, so a managed repo that publishes to a sibling repo loses the handle in every record naming it, and each one is restored by hand. Extend the exemption to the remote's owner followed by '/<any repo name>', since that owner is public by the same argument; the owner alone and other owners stay masked. Reported from a managed repository that publishes to a sibling repository of the same owner.

The scanner still masks the repository owner's public GitHub handle when it names a sibling repository of the same owner, e.g. <owner>/<sibling> written in a record of <owner>/<repo>. isOwnRepoSlug (internal/adapter/scanner/identity.go) exempts the owner only in the repository's own owner/repo slug, so a managed repo that publishes to a sibling repo loses the handle in every record naming it, and each one is restored by hand. Extend the exemption to the remote's owner followed by '/<any repo name>', since that owner is public by the same argument; the owner alone and other owners stay masked. Reported from a managed repository that publishes to a sibling repository of the same owner.

Grounds

• pursued: a record of <owner>/<repo> naming <owner>/<sibling> keeps the owner's handle through every scanner-backed redactor (TestGithubUsernameSparesTheOwnersSiblingSlug); a sibling slug still rewritten, or the owner alone, another owner, or a slug after a non-forge host spared (TestGithubUsernameSlugExemptionIsAnchored), would show it wrong