peleduri/varsec

AI Summary: This issue proposes translating the project's English-only README into Simplified Chinese and Spanish to broaden its global reach and attract more international users and contributors. The solution involves creating `README_zh-CN.md` and `README_es.md` files with full, accurate translations and adding a language selector to the main `README.md`. This initiative aims to replicate the success seen in other projects that benefited from translated documentation.

AI Summary: This GitHub issue proposes creating a "First 10 Minutes" guided tutorial to address new user onboarding difficulties. The current getting-started guide assumes adapter access, causing users to bounce when they can't immediately run anything. The new tutorial will provide step-by-step commands using mock data, expected outputs, and troubleshooting, aiming to convert README visitors into active users.

AI Summary: This issue proposes adding a CODE_OF_CONDUCT and various issue/PR templates to the repository. These files are crucial for signaling mature governance, standardizing contributions, and fostering enterprise adoption and community trust. The proposed solution includes specific templates like Contributor Covenant and structured bug/feature request forms.

AI Summary: This issue proposes creating five new subdirectories under `adapters/examples/` to provide concrete guidance for contributors on how to implement different types of adapters. Each new directory will contain a `README.md` explaining the adapter type, a `credentials.example.yaml` demonstrating authentication patterns, and an `mcp-manifest.example.json` defining the tool interface. This will resolve the current problem of non-existent example directories listed in the main README.

AI Summary: This issue addresses the absence of five crucial JSON mock data files, which are referenced in the `tests/mock-data/README.md` but do not exist. Their absence prevents proper testing and demonstration of the framework without live adapter connections. The proposed solution is to create these five JSON files with 5-10 realistic, fictional records each, covering asset inventory, SIEM events, cloud posture, ticketing, and messaging data.