Implement standard GitHub community health files using repository references

Background

Currently, we need a way to reference standard community files (like CODE_OF_CONDUCT.md and SECURITY.md) without duplicating them across repositories while ensuring they remain prominently visible on the repository landing page.

Problem

• Maintaining multiple copies of community files across repositories creates maintenance overhead
• Changes to these documents require updates in multiple places
• We want to keep the prominent visibility GitHub provides for these files on repository landing pages

Proposed Solution

Still being investigated

Files to Include

• CODE_OF_CONDUCT.md
• SECURITY.md
• Any other standard community health files we want to centralize

Acceptance Criteria

• Community files are stored in a central location
• Files are properly linked/referenced/updated in dependent repositories
• Files appear prominently on repository landing pages

Resources

• GitHub Docs: Creating a default community health file

Start with the linked GitHub documentation on default community health files and review the requested CODE_OF_CONDUCT.md and SECURITY.md files. Define how central storage and references or updates would work for dependent repositories, then verify that the files remain prominent on each repository landing page.