# Support

## Before opening an issue

1. Search existing issues and documentation.
2. Run the relevant validation command from the root README.
3. Remove credentials, private paths, proprietary source code, and personal data.
4. For a diagnostic correction, include the language, tool/version, exact code or exception name, expected meaning, source URL, minimal trigger, and safe repair.

## Security concerns

Do not create a public issue for a vulnerability or sensitive data exposure. Follow [SECURITY.md](../SECURITY.md).

## Scope

LexiconError is an offline reference. Support covers catalog correctness, ingestion adapters, validated local imports, release artifacts, and the desktop interface. It does not include executing supplied snippets, diagnosing proprietary projects without a reproduction, or guaranteeing upstream compiler behavior.