Get help and contribute

For a reproducible bug, use the issue templates. Search existing issues first. Include the release or commit, deployment type, relevant model and tool configuration, expected result, actual result and a minimal synthetic input.

Do not include credentials or private documents. For a suspected vulnerability, follow the private reporting instructions in SECURITY.md, rather than opening a public reproduction.

Before reporting an installation problem

Check installation and the selected deployment configuration. Record the command that failed and a redacted error. For a document answer, check source processing, collection binding and permissions. For a tool failure, preserve the tool error and run status. A connection probe is not proof that the task completed.

Contribute or scope implementation help

Read CONTRIBUTING.md, architecture and the relevant how-to before changing behavior. A focused documentation fix or a reproducible issue is a useful contribution. Coordinate larger changes with maintainers through the repository.

For deployment in your infrastructure, documentation, process creation or custom development, contact Vstorm or Kacper. Support commitments are scoped separately. Community issue reporting is not a contracted response SLA.