Prepare RelayOS public alpha launch

.github/CODEOWNERS

@@ -0,0 +1,6 @@
+* @rufatixx
+
+/src/RelayOS.Core/Cryptography/ @rufatixx
+/src/RelayOS.Core/Storage/ @rufatixx
+/SECURITY.md @rufatixx
+/TRADEMARKS.md @rufatixx

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Questions and design discussions
+    url: https://github.com/rufatixx/RelayOS/discussions
+    about: Ask for help or discuss an idea before opening an implementation issue.
+  - name: Sensitive security report
+    url: https://github.com/rufatixx/RelayOS/security/advisories/new
+    about: Report vulnerabilities privately. Do not disclose sensitive details in an issue.

.github/workflows/core.yml

@@ -30,3 +30,19 @@ jobs:
 
       - name: Run Core tests
         run: dotnet test tests/RelayOS.Core.Tests/RelayOS.Core.Tests.csproj --configuration Release --no-build
+
+      - name: Run the console simulation
+        run: dotnet run --project samples/RelayOS.Simulator/RelayOS.Simulator.csproj --configuration Release -- "CI relay proof"
+
+      - name: Audit NuGet dependencies
+        run: dotnet list tests/RelayOS.Core.Tests/RelayOS.Core.Tests.csproj package --vulnerable --include-transitive
+
+      - name: Pack the Core alpha
+        run: dotnet pack src/RelayOS.Core/RelayOS.Core.csproj --configuration Release --no-restore --output artifacts
+
+      - name: Upload the NuGet package
+        uses: actions/upload-artifact@v4
+        with:
+          name: RelayOS.Core
+          path: artifacts/*.nupkg
+          if-no-files-found: error

CHANGELOG.md

@@ -0,0 +1,26 @@
+# Changelog
+
+All notable RelayOS changes are recorded here. The project follows Semantic
+Versioning for releases; the packet protocol has its own version field.
+
+## [0.1.0-alpha.1] - 2026-08-05
+
+### Added
+
+- Recipient-key payload encryption using ephemeral P-256 ECDH, HKDF-SHA-256,
+  and AES-256-GCM.
+- Durable JSON packet queues with atomic replacement, TTL pruning, priority
+  ordering, deduplication, and conflicting-ID detection.
+- Transport contracts and an in-process `LocalRelayHub` simulator.
+- Alice → Courier → Bob store-carry-forward tests and console simulation.
+- .NET MAUI Android source demo for the same local simulation.
+- Contributor, governance, security, trademark, and project identity policies.
+
+### Known limitations
+
+- No physical device transport, peer discovery, background operation, or
+  production routing.
+- No sender signatures, key-discovery system, or delivery receipts.
+- No independent security audit or Android release verification.
+
+[0.1.0-alpha.1]: https://github.com/rufatixx/RelayOS/releases/tag/v0.1.0-alpha.1

CITATION.cff

@@ -0,0 +1,21 @@
+cff-version: 1.2.0
+message: "If RelayOS supports your work, please cite the project and credit its creator."
+title: "RelayOS"
+type: software
+authors:
+  - family-names: "Asadzade"
+    given-names: "Rufat"
+repository-code: "https://github.com/rufatixx/RelayOS"
+url: "https://github.com/rufatixx/RelayOS"
+license: "AGPL-3.0-only"
+version: "0.1.0-alpha.1"
+date-released: "2026-08-05"
+abstract: >-
+  An experimental .NET 10 foundation for encrypted, delay-tolerant,
+  store-carry-forward message relay.
+keywords:
+  - delay-tolerant networking
+  - store-carry-forward
+  - encrypted messaging
+  - offline-first
+  - dotnet

CODE_OF_CONDUCT.md

@@ -0,0 +1,35 @@
+# RelayOS Code of Conduct
+
+RelayOS is committed to a focused, welcoming, and technically honest project
+community.
+
+## Expected behavior
+
+- Treat participants with respect, including when reviewing mistakes.
+- Discuss ideas and evidence rather than attacking people.
+- Make security, privacy, and compatibility concerns explicit.
+- Credit prior work and the people who contribute it.
+- Respect the distinction between the current simulator and future real-device
+  networking.
+
+## Unacceptable behavior
+
+Harassment, threats, discrimination, sexualized attention, deliberate
+intimidation, publishing private information, plagiarism, spam, and sustained
+disruption are not acceptable in project spaces.
+
+## Scope and enforcement
+
+This policy applies in RelayOS repositories, issues, pull requests,
+discussions, and project events. Maintainers may edit or remove content, close
+threads, reject contributions, or temporarily or permanently restrict
+participation when needed to protect the community.
+
+For ordinary disagreements, use the relevant issue or discussion. For a
+sensitive conduct report, contact the maintainer through the official
+[GitHub profile](https://github.com/rufatixx) to establish a private channel.
+Do not publish another person's private information in a report.
+
+Maintainers will handle reports as privately and fairly as the circumstances
+allow. Anyone enforcing this policy must disclose conflicts of interest and
+step aside when impartial handling is not possible.

CONTRIBUTING.md

@@ -70,4 +70,5 @@ Use temporary directories for storage tests and ensure they are cleaned up. Keep
 
 Use concise, imperative commit messages. In the pull request description, include what changed, how it was tested, and any remaining limitations. Never include credentials, exported private keys, user data, generated build output, or device-specific signing files.
 
-By contributing, you agree that your contribution is licensed under the repository's MIT License.
+By contributing, you agree that your contribution is licensed under the
+repository's GNU Affero General Public License v3.0 only (AGPL-3.0-only).