[Docs]: Structure Repository Standards via CODE_OF_CONDUCT.md and SUPPORT.md Layouts

Problem

Our repository backend includes comprehensive structural outlines but lacks explicit standard community guidelines blocks to govern international developer interaction bounds and onboarding support pipelines cleanly.

Proposed Solution

Inject two foundational documentation asset templates inside the root workspace nodes:

1. CODE_OF_CONDUCT.md: Implement the standardized Contributor Covenant text matrices layout to enforce inclusive open-source interaction bounds.
2. SUPPORT.md: Define explicit communication funnels detailing how community builders can open technical queries, report system memory bugs, or contact core operators directly.

Use Case

Completes our repository’s open-source compliance requirements grid, earning total structural trust from corporate enterprise purchasers and open core index algorithms.

Check the repository root for existing community and contribution guidance files before creating the two named assets. Add a standard Contributor Covenant layout to CODE_OF_CONDUCT.md and communication guidance for questions, memory-bug reports, and operator contact to SUPPORT.md. Done means both files exist at the root with the requested guidance.