AvaScope is developed primarily by autonomous coding agents. Human bug reports, design feedback and suggested improvements are welcome through issues. Development uses direct commits and pushes to master; task branches, worktrees and pull requests are not part of the workflow. Agents remain responsible for implementation, validation, repository workflow, and release handoff.
- Search existing issues before opening a new one.
- Use an issue to agree on non-trivial behavior or public-surface changes before implementation.
- Keep changes narrowly scoped and avoid unrelated refactoring.
- Follow the selected issue, milestone, and project workflow.
- Report security problems through SECURITY.md, not a public issue.
Install the .NET 10 SDK. For normal development, build and test the affected components and dependents using the risk-based validation rules. A full local solution check, when justified, uses:
dotnet restore AvaScope.slnx
dotnet build AvaScope.slnx
dotnet test AvaScope.slnxWindows installer packaging additionally requires Inno Setup. Linux installer packaging is validated on Linux or WSL. See docs/VALIDATION.md for focused and release-level validation commands.
Every meaningful change should include relevant tests, or a clear validation note when automated testing does not apply. Update user and stable-surface documentation when behavior, commands, protocols, packages, or artifacts change.
Follow the GitHub information policy for all outgoing text and evidence, and the information ownership rules to avoid duplicate records.
By contributing, you agree that your contribution is licensed under the Apache License 2.0. AvaScope does not currently require a Contributor License Agreement.