chore: reset repository history

SUPPORT.md

@@ -0,0 +1,61 @@
+# Support
+
+Thanks for using Xdrop.
+
+To keep answers discoverable and to align with open source best practices, please prefer public
+support channels for non-sensitive questions.
+
+## Where to ask what
+
+### Bug reports
+
+Use the bug report issue form when you can reproduce a defect in the current behavior.
+
+Include:
+
+- what you expected to happen
+- what actually happened
+- reproduction steps
+- environment details
+- logs or screenshots when relevant
+
+### Feature requests
+
+Use the feature request issue form for ideas that fit Xdrop's current scope.
+
+For larger changes, explain the problem first. A proposal is much easier to review when it starts
+with the user or maintainer pain it solves.
+
+### Questions and troubleshooting
+
+Use the question issue form for setup problems, workflow questions, or help understanding current
+behavior.
+
+Please share enough context for someone else to help:
+
+- what you are trying to do
+- what command or page you used
+- what you already tried
+- exact error output when available
+
+### Security issues
+
+Do not file public issues for vulnerabilities, exposed secrets, or anything that could put users at
+risk.
+
+Follow [SECURITY.md](SECURITY.md) and email [hi@xi-xu.me](mailto:hi@xi-xu.me) instead.
+
+## Before you open an issue
+
+- search existing issues and pull requests first
+- use the issue template that best matches your request
+- keep the conversation in the issue thread instead of moving to private messages
+- remove sensitive values, credentials, and full share links from logs and screenshots
+
+## Response expectations
+
+Xdrop is maintained on a best-effort basis. Maintainers will try to respond promptly, but there is
+no guaranteed SLA.
+
+If a thread has been quiet for more than 7 days and you have new information, a polite follow-up is
+welcome.