# Support

Jun OS is a volunteer fan project without guaranteed response times, but good diagnostic details make it much easier to help.

## Start here

1. Read [When things go sideways](README.md#when-things-go-sideways) and the wiki's [Common Fixes](https://github.com/efficiencyx/JunOS/wiki/9-Common-Fixes).
2. Check the full [configuration reference](docs/configuration.md).
3. Search open and closed GitHub issues.
4. If the problem remains, open a **Setup or support request**. Use a **Bug report** when you have a repeatable defect, or a **Feature request** for a new capability.

Include your installation method, OS, relevant hardware, provider and model, enabled profiles, release or commit, commands already tried, and a short relevant log excerpt.

## Protect your data

Issues are public. Never post:

- `.env` files, passwords, API keys, registration keys, recovery codes, or session/data-key cookies;
- private chat history, memory notes, journals, or database contents;
- recovered game assets, game archives, or copyrighted source files;
- a complete log when a small redacted excerpt shows the problem.

Replace sensitive values with clear placeholders such as `<redacted-api-key>`. If a log contains local paths with your username, redact those too.

## Security problems

Do not use a public support or bug issue for an exploitable vulnerability. Follow the private reporting instructions in [SECURITY.md](SECURITY.md#reporting-a-vulnerability).

## Project boundaries

Support is best-effort. The project cannot provide original game assets, debug modified or pirated game files, guarantee compatibility with every model or unsupported GPU, or recover lost local state. Back up the `omega_state` volume or `runtime/state` before making risky local changes. Keep your recovery code separately: a backup alone cannot unlock encrypted content if you lose both the password and code.