docs: refine README positioning and finalize 0.3.0 changelog date

Use neutral performance-focused wording for Granian RSGI and move 0.3.0 changelog notes from unreleased to a dated release section.

Author: ZhuchkaTriplesix

CHANGELOG.md

@@ -5,7 +5,9 @@ All notable changes to OxyRoute are documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and the project
 adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## [0.3.0] - unreleased
+## [Unreleased]
+
+## [0.3.0] - 2026-04-27
 
 ### Added
 

README.md

@@ -1,6 +1,6 @@
 # OxyRoute
 
-**RSGI-first** web toolkit: HTTP routing, JSON/form handling, JWT validation, response mapping, and native WebSockets on a **Rust** hot path ([PyO3](https://pyo3.rs/) + [Maturin](https://www.maturin.rs/)), with your business logic in ordinary **Python** handlers. Pair it with **[Granian](https://github.com/emmett-framework/granian)** using `--interface rsgi` for the intended stack.
+High-performance web framework for **Granian RSGI**, tuned for high **single-worker** throughput: routing, JSON/form parsing, JWT checks, response mapping, and native WebSockets run on a **Rust** hot path ([PyO3](https://pyo3.rs/) + [Maturin](https://www.maturin.rs/)), while business logic stays in plain **Python** handlers.
 
 [![CI](https://github.com/QueryaHub/OxyRoute/actions/workflows/ci.yml/badge.svg?branch=main)](https://github.com/QueryaHub/OxyRoute/actions)