# Support

## Start here

- Read the [README](README.md) for installation, configuration, usage, security, scope, and troubleshooting.
- Check the [requirements traceability reference](docs/requirements-traceability/README.md) when you need the implementation or verification home for a product requirement.
- Reproduce visual-verification issues with the checked-in [UI restoration example](examples/ui-restoration/README.md).
- Search existing [issues](https://github.com/Anionex/dsh-vision-toolkit/issues) and [pull requests](https://github.com/Anionex/dsh-vision-toolkit/pulls) before opening a duplicate.

## Where to ask

- Reproducible defect: use the bug report form.
- Installation, configuration, or usage question: use the question form.
- Focused product improvement: use the feature request form.
- Security concern: follow [SECURITY.md](SECURITY.md) and report it privately.
- Code contribution: read [CONTRIBUTING.md](CONTRIBUTING.md) before opening a pull request.

Open the repository's [issue chooser](https://github.com/Anionex/dsh-vision-toolkit/issues/new/choose) to select the appropriate form.

## Information to include

Provide the DSH snapshot and profile, plugin commit or release, operating system, Node.js and Python versions, runtime mode, affected `vision_*` tool or Settings action, minimal reproduction steps, expected behavior, and sanitized output. For visual defects, attach the smallest non-private input and generated Artifact that reproduce the result.

Remove API keys, authorization headers, complete prompts or conversations, private image content, and unrelated workspace paths. A support issue is public unless GitHub explicitly marks the channel private.