Repository visibility precedence change across codecov.yml schema versions

A private source repository should keep Codecov coverage reports and commit details non-public.

Repository visibility is documented as driven by the provider, but codecov.yml can include a public setting and the Codecov UI provides a Public Reports control. Parsing of privacy-related keys differs between Codecov SaaS, Codecov Enterprise Server, and across codecov.yml schema versions, and defaults are not consistent across deployments.

When a configuration template intended for public repositories is reused for a private repository, the precedence between provider visibility, codecov.yml, and UI settings is unclear.

Does a codecov.yml public: true entry override provider private visibility on Codecov SaaS? Does the YAML schema version change how the public key is parsed for privacy settings? Does changing visibility in the Codecov UI affect a public flag set in codecov.yml?