Good Open Source Hygiene to Improve Community Collaboration

Did quick audit and in interest of helping the project in OS hygiene and helping with CYA on your future contributions as you grow, could be expanded for all repos under org:

1. Could Use a CodeOwners file to help external parties know who to contact; example: https://github.com/IntersectMBO/osc-documentation/blob/master/CODEOWNERS
2. Should expand and make a contributing.md file that shows how people can better participate: https://github.com/IntersectMBO/cardano-node/blob/master/CONTRIBUTING.md
3. Need a Security md file for reporting vulnerabilities safely if any; example: https://github.com/cardano-scaling/mithril/blob/main/SECURITY.md
4. Easy to include code of conduct related to engagements: https://github.com/IntersectMBO/osc-documentation/blob/master/CODE_OF_CONDUCT.md
5. Something to consider for CYA even though you're using AGPL 3, while somewhat permissive license doesn't exclude the need for having a contributor license agreement completely, example: https://opensource.google/documentation/reference/cla/
6. Ease of access also I would include a PR and Issues template, helps later down the road and for contributors putting them in.
7. Also for security of your project, I would enable content reports, its very helpful for workflow management

Start by reviewing the repository's current GitHub metadata and the linked CODEOWNERS, CONTRIBUTING.md, SECURITY.md, and CODE_OF_CONDUCT.md examples. Clarify which recommendations apply to openlifu-python versus all organization repositories, then define the agreed files, templates, reporting settings, and any CLA decision as complete.