chore(release): update v2.6.3 core benchmark notes

Author: GaspardKirira

CHANGELOG.md

@@ -25,6 +25,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Fixed WAF session configuration handling for target length, body size, and mode validation in isolated tests.
 - Fixed runtime worker shutdown behavior when yielding tasks are still being rescheduled.
 - Improved router route metadata so tests can validate registered paths, methods, and heavy-route flags.
+- Fixed and stabilized Core benchmark workloads so long-running benchmark targets do not block full benchmark runs.
 
 ### Changed
 
@@ -35,6 +36,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Strengthened the core test layout with dedicated test groups for HTTP, router, session, server, runtime, executor, config, and app behavior.
 - Updated core test registration so network-based tests use isolated ports, timeouts, and serial execution where required.
 - Improved `vix tests` live progress reporting to show completed, total, running, and elapsed test state during long CTest runs.
+- Updated the Core module README with benchmark workflow documentation and a link to the official v2.6.3 benchmark baseline article.
+- Documented the benchmark rule that official performance numbers must be generated from Release builds, not dev/debug builds.
+- Updated Core benchmark registration so benchmark binaries are grouped under `build-release/benchmarks/core` when `VIX_CORE_BUILD_BENCHMARKS=ON`.
 
 ### Added
 
@@ -47,6 +51,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Added executor test coverage for metrics, task options, runtime executor construction, lifecycle, submit/post behavior, metrics, and shutdown.
 - Added config test coverage for defaults, environment loading, set/get behavior, typed accessors, database settings, WAF settings, TLS settings, logging settings, reload behavior, and copy/move behavior.
 - Added app test coverage for constructors, config access, dev mode, templates, routes, groups, middleware, protected routes, static directories, static hooks, lifecycle behavior, module initialization, and stdout configuration.
+- Added the official Vix Core benchmark suite covering runtime tasks, runtime queues, runtime scheduler, runtime workers, executor submit/post/metrics, router matching, router registration, HTTP request/response behavior, fake transport sessions, app route registration, and app group registration.
+- Added shared benchmark utilities for measuring median time, mean time, operations per second, warmup iterations, measured samples, and JSON report generation.
+- Added `scripts/run_core_benchmarks.sh` to run the full Core benchmark suite and write versioned JSON reports.
+- Added `scripts/compare_core_benchmarks.py` to compare current benchmark results against a baseline using configurable warning and failure thresholds.
+- Added `benchmarks/baselines/` for versioned official benchmark baselines.
+- Added the official Core `v2.6.3` Release benchmark baseline generated on Linux x86_64 with GCC 13.3.0.
+- Added a blog article documenting the Vix Core v2.6.3 benchmark baseline and the performance workflow.
 
 ## v2.6.2
 

README.md

@@ -63,9 +63,7 @@ irm https://vixcpp.com/install.ps1 | iex
 
 More installation options:
 
-```text
 https://vixcpp.com/install
-```
 
 ## Quick start
 
@@ -256,10 +254,10 @@ Cnerium attaches to Vix and protects selected write operations.
 | [Rix](https://github.com/rixcpp/rix)                                | Official userland library layer for Vix.cpp, distributed through the registry.                                                   |
 | [Vix Pico](https://github.com/vixcpp/pico)                          | Production-style backend used to validate Vix modules, deployment, auth, PDF generation, SQLite, KV, jobs, and WebSocket routes. |
 | [Vix Game](https://github.com/vixcpp/vix-game)                      | Game-oriented project built on the Vix.cpp runtime foundation.                                                                   |
-| [Softadastra Runner](https://github.com/softadastra/runner)         | Small command runner built with Vix.cpp and `vix::process`.                                                                      |
 | [Kordex](https://github.com/softadastra/kordex)                     | JavaScript and TypeScript runtime layer built on Vix and Softadastra.                                                            |
-| [Softadastra Engine](https://github.com/softadastra/softadastra)    | Local-first and offline-first runtime foundation for reliable applications.                                                      |
 | [Cnerium](https://github.com/softadastra/cnerium)                   | Reliability-first application framework built on Vix and the Softadastra SDK.                                                    |
+| [Softadastra Engine](https://github.com/softadastra/softadastra)    | Local-first and offline-first runtime foundation for reliable applications.                                                      |
+| [Softadastra Runner](https://github.com/softadastra/runner)         | Small command runner built with Vix.cpp and `vix::process`.                                                                      |
 | [Softadastra Cloud](https://github.com/softadastra/cloud)           | Reliability testing control plane for reports, scores, and dashboard results.                                                    |
 | [Softadastra Converdict](https://github.com/softadastra/converdict) | Reliability verification platform for distributed systems.                                                                       |
 | [Softadastra PulseGrid](https://github.com/softadastra/PulseGrid)   | Real-time service monitoring built with Vix.cpp.                                                                                 |
@@ -333,7 +331,7 @@ vix tests
 Add a package:
 
 ```bash
-vix add rix/csv
+vix add rix/rix@0.9.1
 vix install
 ```
 
@@ -389,9 +387,7 @@ Contributions are welcome.
 
 Read the contribution guide:
 
-```text
 https://docs.vixcpp.com/contributing
-```
 
 You can contribute by improving the runtime, writing examples, testing Vix on real projects, improving documentation, or publishing packages for the Vix registry.