экшены на Node 24; community-документы

Обновлены версии GitHub Actions, чтобы убрать предупреждение о Node.js 20:
actions/checkout v4→v5, actions/setup-dotnet v4→v5,
softprops/action-gh-release v2→v3 (все на node24).

Добавлены community-файлы: Code of Conduct, Contributing, Security policy,
шаблоны issue и pull request. В README добавлен раздел Contributing со
ссылками на них.

Author: IvanLarinDev

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,40 @@
+---
+name: Bug report
+about: Report a problem to help us improve Dropwheel
+title: "[Bug]: "
+labels: ["bug"]
+assignees: []
+---
+
+## Describe the bug
+
+A clear and concise description of what the bug is.
+
+## Steps to reproduce
+
+1. Go to '...'
+2. Click on '...'
+3. Scroll down to '...'
+4. See error
+
+## Expected behavior
+
+A clear and concise description of what you expected to happen.
+
+## Actual behavior
+
+What actually happened. Include error messages or logs if available.
+
+## Screenshots
+
+If applicable, add screenshots to help explain your problem.
+
+## Environment
+
+- OS: [e.g. Windows 11, macOS 14]
+- Browser / runtime: [e.g. Chrome 126, Node 20]
+- Dropwheel version / commit: [e.g. v1.0.0 or commit hash]
+
+## Additional context
+
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Security vulnerability
+    url: https://github.com/IvanLarinDev/dropwheel/security/advisories/new
+    about: Please report security issues privately, not as public issues.
+  - name: Questions & discussion
+    url: https://github.com/IvanLarinDev/dropwheel/issues
+    about: Ask questions or discuss ideas before opening a formal issue.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,24 @@
+---
+name: Feature request
+about: Suggest an idea or improvement for Dropwheel
+title: "[Feature]: "
+labels: ["enhancement"]
+assignees: []
+---
+
+## Problem / motivation
+
+Is your feature request related to a problem? Describe it.
+Example: "I'm always frustrated when [...]"
+
+## Proposed solution
+
+A clear and concise description of what you want to happen.
+
+## Alternatives considered
+
+Any alternative solutions or features you've considered.
+
+## Additional context
+
+Add any other context, mockups, or screenshots about the feature request here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,28 @@
+## Description
+
+Briefly describe what this pull request changes and why.
+
+## Related issue
+
+Closes #<!-- issue number -->
+
+## Type of change
+
+- [ ] Bug fix (non-breaking change that fixes an issue)
+- [ ] New feature (non-breaking change that adds functionality)
+- [ ] Breaking change (fix or feature that changes existing behavior)
+- [ ] Documentation update
+- [ ] Refactor / chore
+
+## How has this been tested?
+
+Describe the tests you ran and how to reproduce them.
+
+## Checklist
+
+- [ ] My code follows the project's style and conventions
+- [ ] I have performed a self-review of my changes
+- [ ] I have commented my code where necessary
+- [ ] I have updated documentation where needed
+- [ ] My changes generate no new warnings or errors
+- [ ] I have read the [Contributing guidelines](../CONTRIBUTING.md)

.github/workflows/ci.yml

@@ -9,9 +9,9 @@ jobs:
   build:
     runs-on: windows-latest
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v5
 
-      - uses: actions/setup-dotnet@v4
+      - uses: actions/setup-dotnet@v5
         with:
           dotnet-version: 10.0.x
 

.github/workflows/release.yml

@@ -12,9 +12,9 @@ jobs:
   release:
     runs-on: windows-latest
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v5
 
-      - uses: actions/setup-dotnet@v4
+      - uses: actions/setup-dotnet@v5
         with:
           dotnet-version: 10.0.x
 
@@ -33,7 +33,7 @@ jobs:
           Compress-Archive -Path dist-sc/* -DestinationPath "Dropwheel-${{ github.ref_name }}-win-x64-self-contained.zip"
 
       - name: Create GitHub Release
-        uses: softprops/action-gh-release@v2
+        uses: softprops/action-gh-release@v3
         with:
           files: Dropwheel-*.zip
           generate_release_notes: true

CODE_OF_CONDUCT.md

@@ -0,0 +1,134 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official email address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement by opening a
+[GitHub issue](https://github.com/IvanLarinDev/dropwheel/issues) or, for
+sensitive matters, through a
+[private security advisory](https://github.com/IvanLarinDev/dropwheel/security/advisories/new).
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

CONTRIBUTING.md

@@ -0,0 +1,61 @@
+# Contributing to Dropwheel
+
+Thanks for your interest in contributing to Dropwheel! This document explains how
+to propose changes so they can be reviewed and merged smoothly.
+
+By participating in this project you agree to abide by our
+[Code of Conduct](CODE_OF_CONDUCT.md).
+
+## Ways to contribute
+
+- **Report a bug** — open a [bug report](https://github.com/IvanLarinDev/dropwheel/issues/new/choose).
+- **Request a feature** — open a [feature request](https://github.com/IvanLarinDev/dropwheel/issues/new/choose).
+- **Improve docs** — fixes to the README or other documentation are always welcome.
+- **Submit code** — pick up an open issue or propose a change via a pull request.
+
+## Before you start
+
+For anything larger than a small fix, please open an issue first to discuss the
+approach. This avoids duplicate work and makes review faster.
+
+## Development workflow
+
+1. **Fork** the repository and clone your fork.
+2. **Create a branch** from `main` with a descriptive name, e.g.
+   `feature/smart-routing` or `fix/shelf-overflow`.
+3. **Make your changes** in focused, logically separated commits.
+4. **Test** your changes locally and make sure existing behavior still works.
+5. **Push** the branch to your fork.
+6. **Open a pull request** against `main` and fill in the PR template.
+
+## Commit messages
+
+Write clear, imperative commit messages, for example:
+
+```
+Add smart routing fallback for empty shelf
+Fix off-by-one in wheel index calculation
+```
+
+Reference related issues where relevant (e.g. `Fixes #123`).
+
+## Pull request guidelines
+
+- Keep pull requests focused; one logical change per PR is easier to review.
+- Fill out the pull request template completely.
+- Link the issue your PR addresses.
+- Describe what you changed and how you verified it.
+- Be responsive to review feedback.
+
+## Reporting security issues
+
+Please do **not** report security vulnerabilities through public issues. See our
+[Security Policy](SECURITY.md) for how to report them privately.
+
+## Questions
+
+If anything is unclear, open a
+[GitHub Discussion or issue](https://github.com/IvanLarinDev/dropwheel/issues)
+and we'll help you get started.
+
+Thank you for helping make Dropwheel better!

README.md

@@ -137,6 +137,13 @@ are tuned per theme.
   copied; files renamed by the conflict dialog are not tracked by Undo.
 - One orb (multi-monitor placement works; one wheel instance).
 
+## Contributing
+
+Contributions are welcome. See [CONTRIBUTING.md](CONTRIBUTING.md) for how to
+propose changes, [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md) for community
+expectations, and [SECURITY.md](SECURITY.md) for reporting vulnerabilities
+privately. Bug reports and feature requests use the issue templates.
+
 ## License
 
 [MIT](LICENSE) © Ivan Larin

SECURITY.md

@@ -0,0 +1,48 @@
+# Security Policy
+
+We take the security of Dropwheel seriously. Thank you for helping keep the
+project and its users safe.
+
+## Supported versions
+
+Dropwheel is under active development. Security fixes are applied to the latest
+release and the `main` branch. Older versions may not receive fixes.
+
+| Version | Supported          |
+| ------- | ------------------ |
+| latest  | :white_check_mark: |
+| older   | :x:                |
+
+## Reporting a vulnerability
+
+**Please do not report security vulnerabilities through public GitHub issues,
+discussions, or pull requests.**
+
+Instead, report them privately using GitHub's private vulnerability reporting:
+
+1. Go to the [Security advisories page](https://github.com/IvanLarinDev/dropwheel/security/advisories/new).
+2. Click **Report a vulnerability**.
+3. Provide as much detail as you can (see below).
+
+If private reporting is unavailable, please open a minimal placeholder issue
+asking a maintainer to contact you, without disclosing any vulnerability
+details.
+
+## What to include
+
+To help us triage quickly, please include:
+
+- A description of the vulnerability and its potential impact.
+- Steps to reproduce, or a proof of concept.
+- The affected version, component, or file.
+- Any suggested mitigation, if known.
+
+## What to expect
+
+- We aim to acknowledge your report within a few business days.
+- We will investigate and keep you informed of progress.
+- Once a fix is available, we will coordinate disclosure and credit you if you
+  wish.
+
+We ask that you give us a reasonable amount of time to address the issue before
+any public disclosure. Thank you for practicing responsible disclosure.