# Support

中文说明：[SUPPORT_ZH.md](SUPPORT_ZH.md)

Horosa is being prepared for a formal open-source GitHub release. This file describes the intended support path once the repository is public, while also making clear what still needs maintainer confirmation.

## Start With Self-Service

Before opening a support request, check:

- [README.md](README.md)
- [README_EN.md](README_EN.md)
- [PROJECT_STRUCTURE.md](PROJECT_STRUCTURE.md)
- [Horosa_Desktop_Installer/README.md](Horosa_Desktop_Installer/README.md)

## Public Support Model

The intended support flow after publication is:

- bug reports: GitHub issue templates
- feature requests: GitHub issue templates
- usage questions and open discussion: GitHub Discussions
- security problems: private reporting path described in [SECURITY.md](SECURITY.md)

## What To Include In A Support Request

- platform: web, app, or both
- workspace or module involved
- provider mode and model if AIAnalysis is involved
- reproducible steps
- expected versus actual behavior
- sanitized logs, screenshots, or backup snippets
- whether the issue affects only a local environment or multiple environments

## Current Public Contact

- public support email: `maxwelldhx@gmail.com`
- GitHub Discussions: intended public discussion surface for usage questions, ideas, and open-ended feedback
- private or enterprise support: not separately documented at this time

## Before Public Launch

Until the repository is fully published:

- use the repository docs first
- keep sensitive issues private
- use the security path in [SECURITY.md](SECURITY.md) for anything involving credentials, installer integrity, or local data exposure