release(v2.1): prepare 2.1.0-RC.3 - green suites, every arm re-measured, metadata and docs aligned

Verification (recorded in docs/2.1.0-RC.3_WHAT_CHANGED.md and plan section 8d):
- 16/16 test suites green, run unfiltered through the MTP hosts in Release on net11.0: 2,897 tests,
  0 failed, 0 errors, 16 skipped (core 1,916; VectorSearch 248; Provider.Sync 135; EF Core 116;
  Analytics 81; EventSourcing 72; Graph.Advanced 65; CQRS 64; Search 58; Identity 53; Functional 38;
  Functional.Linq2DB 24; Projections 15; HybridSearch 6; Functional.Dapper 3;
  Functional.EntityFrameworkCore 3).
- Write-path regression gate PASSED (nothing slower than baseline x 1.50); the three "watch" entries
  sit inside the run's own 2.08x rep spread.
- Product-default regime, no SHARPCOREDB_* switch set (banner-confirmed). Fair PK: fixed-width
  UPDATE 324,560 and DELETE 736,046 against SQLite 258,213 / 342,452 - 0.8x and 0.5x, i.e. ahead;
  INSERT 108,661 against 156,946 - 1.4x behind, unchanged. Pure default: 96,266 / 55,533 / 79,337 /
  208,722, so UPDATE 3.6x behind (the documented NoEncryptMode mechanism). PageBased fixed-width:
  INSERT 175,562 at parity, UPDATE 58,464 - 4.9x behind, improved from 5.7x. Comparative SQL / Direct
  / StructRow reported separately: 85,560/67,482/63,853/107,871, 124,976/139,840/98,421/235,605,
  133,023/108,602. Multi-row batched 52,742 rows/s, 18.96 us/row, 4,341-4,343 B/row, 1,840,000 B data
  file, 488,890 B arena - the deterministic figures match the committed default.
- The machine was loaded, so the ratios are the comparable part: SQLite's own reference moved
  (fair-PK INSERT 202,292 on 09-16 against 156,946 here). Recorded rather than glossed.

Release mechanics:
- All 46 csproj files are on 2.1.0-RC.3 (a single distinct <Version>); the two IsPackable=false
  benchmark projects had stale 2.0.0.2 AssemblyVersion/FileVersion, now 2.1.0.0.
- 17 packable projects carried the inherited v2.0.0.2 PackageReleaseNotes boilerplate - replaced with
  a 2.1.0-RC.3 note; Aspire.Hosting's own note bumped.
- 18 package READMEs still described 2.0.0.2 as the current release - titles, "current release" lines
  and install commands now name 2.1.0-RC.3 (and the install commands no longer carry a "v" prefix,
  which a first pass introduced and this commit corrects). The core README gained a "What's New in
  2.1.0-RC.3" section and a footer that no longer claims 1,700+ tests.
- SharpCoreDB.Aspire.Hosting was missing from SharpCoreDB.CI.slnf, so "Manual NuGet Publish" would
  never have pushed it; added. publish-manual.yml Layer 3 pushed a "SharpCoreDB.Server.*" nupkg that
  cannot exist - replaced with the Aspire pattern.
- src/SharpCoreDB.Server is IsPackable=false and is NOT on nuget.org, yet the READMEs told consumers
  to "dotnet add package SharpCoreDB.Server". Corrected to SharpCoreDB.Server.Core and
  Server.Protocol plus the executable and container-image routes (root README, Server README and its
  NuGet.README.md).
- NUGET_PUBLISHING_GUIDE.md: RC.3 click-by-click, the packVersion input, a current line-state table,
  and the core-only vs full-package-set distinction.
- dotnet pack on SharpCoreDB.CI.slnf produces 27 packages, all at 2.1.0-RC.3, 0 errors; the full
  solution builds with 0 errors.

Docs: new docs/2.1.0-RC.3_WHAT_CHANGED.md (validation table, highlights, every measured arm, and the
open gaps stated plainly); CHANGELOG promotes [Unreleased] to [2.1.0-RC.3] - 2026-09-17 and drops an
empty duplicate heading; INDEX, PROJECT_STATUS, FEATURE_MATRIX and README updated; the performance
plan's section 0 records that release mechanics are now authorised.

Provenance: the four results/*.json from this run are committed, per plan item 13.

Author: MPCoreDeveloper

.github/NUGET_PUBLISHING_GUIDE.md

@@ -61,20 +61,55 @@ order (with `--skip-duplicate`):
 |---|---|
 | `reason` | Free-text note shown in the run summary |
 | `versionSuffix` | Optional NuGet pre-release suffix. **Empty** → stable version from the `.csproj` files (e.g. `2.0.0.0`). **`preview.1`**, **`rc.1`**, **`beta.1`** → `2.0.0.0-preview.1` etc. |
+| `packVersion` | Explicit full package version (e.g. `2.1.0-RC.3`) passed as `/p:Version=…` to the whole pack. Leave empty to use the version each project declares. |
 
-### Scenario B2: Publishing the 2.0.0.0 release (click-by-click)
+This workflow packs **`SharpCoreDB.CI.slnf`**, i.e. every packable package in the family, and pushes
+them in dependency layers (core → dependents → mid-level → top-level → remaining).
+
+> `src/SharpCoreDB.Server` is **not** in that set: it is `IsPackable=false` (a standalone executable
+> shipped as the `sharpcoredb-server` binary and the `ghcr.io/mpcoredeveloper/sharpcoredb-server`
+> container image). Its packable libraries are `SharpCoreDB.Server.Core` and
+> `SharpCoreDB.Server.Protocol`, both of which *are* published.
+
+### Scenario B2: Publishing the 2.1.0-RC.3 release (click-by-click)
+
+1. Go to **https://github.com/MPCoreDeveloper/SharpCoreDB → Actions** (tab on top)
+2. In the left sidebar, select **"Manual NuGet Publish"**
+3. Click the blue **"Run workflow"** button (top right)
+4. In the dialog:
+   - **Branch**: `release/v2.1.0.0-RC.3` (the net11.0 / C# 15 preview RC line)
+   - **packVersion**: `2.1.0-RC.3`
+   - **versionSuffix**: leave **empty** (an explicit `packVersion` is supplied)
+   - **reason**: e.g. `2.1.0-RC.3 – validated RC of the net11.0 line (2,897 tests green)`
+5. Click **"Run workflow"**
+6. Open the run to watch it: the **Publish** job logs show `↗ Pushing <package>` per `.nupkg`, grouped in
+   dependency layers (core → dependents → mid-level → top-level).
+7. Verify: **https://www.nuget.org/packages/SharpCoreDB/** — `2.1.0-RC.3` should appear (`2.1.0-rc.3`
+   normalized). Other packages in the family should show the same version.
+
+> The v2.1 RC line is **pre-release**: NuGet will not select `2.1.0-RC.3` unless a consumer asks for it
+> explicitly or ticks *Include prerelease*.
+
+### Scenario B3: Publishing only the core package (quick path)
+
+The branch workflow `.github/workflows/ci-net11.yml` triggers on `release/v2.1.0.0-*` and has a
+`workflow_dispatch` **publish** job that packs and pushes **only** `src/SharpCoreDB/SharpCoreDB.csproj`
+at its declared version. Use it when only the core package changed; use Scenario B2 for a full release.
+
+### Scenario B4: Publishing the 2.0.0.2 release (click-by-click)
 
 1. Go to **https://github.com/MPCoreDeveloper/SharpCoreDB → Actions** (tab on top)
 2. In the left sidebar, select **"Manual NuGet Publish"**
 3. Click the blue **"Run workflow"** button (top right)
 4. In the dialog:
-   - **Branch**: `master` (the v2.0.0.0 trunk — SharpCoreDB v2 is now the leading line)
-   - **versionSuffix**: leave **empty** for the stable `2.0.0.0` release
-   - **reason**: e.g. `2.0.0.0 – performance-first V2 release`
+   - **Branch**: `master` (the v2.0 stable trunk)
+   - **versionSuffix**: leave **empty** for the stable `2.0.0.2` release
+   - **packVersion**: leave **empty** (each project declares its own version)
+   - **reason**: e.g. `2.0.0.2 – performance-first v2 release`
 5. Click **"Run workflow"**
 6. Open the run to watch it: the **Publish** job logs show `↗ Pushing <package>` per `.nupkg`, grouped in
    dependency layers (core → dependents → mid-level → top-level).
-7. Verify: **https://www.nuget.org/packages/SharpCoreDB/** — the `2.0.0.0` version should appear.
+7. Verify: **https://www.nuget.org/packages/SharpCoreDB/** — the `2.0.0.2` version should appear.
 
 > **Requires** the `NUGET_API_KEY` repository secret (`Settings → Secrets and variables → Actions`). If it was
 > used for the 1.9.7 publish it is already configured.
@@ -92,17 +127,29 @@ on:
 
 ## Version Management
 
-SharpCoreDB uses **4-part versions** (`n.n.n.n`, e.g. `2.0.0.0`). The versions come from the `<Version>` tags
-in `.csproj` files, but the **single source of truth for the SharpCoreDB package family is
-`<SharpCoreDBVersion>` in `Directory.Packages.props`** (used by all central package references).
+SharpCoreDB uses **4-part versions** (`n.n.n.n`, e.g. `2.0.0.0`) for its stable lines, and a
+**3-part version plus a prerelease label** for the pre-release lines (`2.1.0-RC.3`). The versions come
+from the `<Version>` tags in `.csproj` files, but the **single source of truth for the SharpCoreDB
+package family is `<SharpCoreDBVersion>` in `Directory.Packages.props`** (used by all central package
+references).
+
+**Current line state (2026-09-17):**
+
+| Line | Branch | Version | Latest published |
+|---|---|---|---|
+| v2.1 RC (net11.0 / C# 15 preview) | `release/v2.1.0.0-RC.3` | `2.1.0-RC.3` | `2.1.0-rc.1` (RC.3 not yet pushed) |
+| v2.0 stable (net10.0 / C# 14) | `master` | `2.0.0.3` | `2.0.0.3` |
+
+Every one of the **46 `.csproj` files on the v2.1 RC branch** carries the same `<Version>` — the
+release checklist is `git grep "<Version>" -- '*.csproj'` and it must return exactly one distinct value.
 
 Each packable project file carries the same version:
 
 ```xml
 <PropertyGroup>
-  <Version>2.0.0.0</Version>
-  <AssemblyVersion>2.0.0.0</AssemblyVersion>
-  <FileVersion>2.0.0.0</FileVersion>
+  <Version>2.1.0-RC.3</Version>
+  <AssemblyVersion>2.1.0.0</AssemblyVersion>
+  <FileVersion>2.1.0.0</FileVersion>
 </PropertyGroup>
 ```
 
@@ -238,4 +285,4 @@ For questions:
 ---
 
 **Created**: 2025-01-28  
-**Last Updated**: 2025-01-28
+**Last Updated**: 2026-09-17 (v2.1.0-RC.3 release preparation)

.github/workflows/ci-net11.yml

@@ -73,9 +73,11 @@ jobs:
         GITHUB_ACTIONS: "true"
 
   # Manual publish to NuGet.org (only via workflow_dispatch, using the repo's
-  # NUGET_API_KEY secret). Packs the net11.0 (C# 15 preview) core at the version pinned in the csproj.
+  # NUGET_API_KEY secret). This packs the net11.0 (C# 15 preview) CORE package at the version pinned
+  # in the csproj. For the full package set (all ~26 SharpCoreDB packages, in dependency order) use
+  # the "Manual NuGet Publish" workflow (publish-manual.yml), which packs SharpCoreDB.CI.slnf.
   publish:
-    name: Pack + Publish to NuGet.org
+    name: Pack + Publish core to NuGet.org
     runs-on: ubuntu-latest
     if: github.event_name == 'workflow_dispatch'
     timeout-minutes: 30

.github/workflows/publish-manual.yml

@@ -12,7 +12,7 @@ on:
         required: false
         default: ''
       packVersion:
-        description: 'Explicit full package version (e.g. 2.1.0-RC.2). Leave empty to use the version each project declares.'
+        description: 'Explicit full package version (e.g. 2.1.0-RC.3). Leave empty to use the version each project declares.'
         required: false
         default: ''
 
@@ -133,8 +133,8 @@ jobs:
           "SharpCoreDB.Projections.*.nupkg"
 
         push_layer "Layer 3 (top-level)" \
-          "SharpCoreDB.Server.[0-9]*.nupkg" \
           "SharpCoreDB.Graph.Advanced.*.nupkg" \
+          "SharpCoreDB.Aspire.Hosting.*.nupkg" \
           "SharpCoreDB.Provider.Sync.*.nupkg" \
           "SharpCoreDB.Provider.YesSql.*.nupkg" \
           "SharpCoreDB.Functional.Dapper.*.nupkg" \

README.md

@@ -24,9 +24,22 @@ Use it when you need:
 - Fast embedded storage with **AES-256-GCM encryption** and ACID guarantees
 - A secure network database via **gRPC (HTTP/2 + HTTP/3)**
 - Built-in **vector search**, **advanced analytics**, and **GraphRAG/graph algorithms**
-- A production-focused stack validated by a **1,777-test core suite** (0 failed; plus CQRS, VectorSearch, EF Core and Linq2DB suites) and **backward compatibility**
-
-> **Current release: v2.0.0.2 (2026-09-04)** — the v2.x engine line: fixed-width record layout is the
+- A production-focused stack validated by a **1,916-test core suite** (0 failed; **2,897 tests across
+  16 suites** in total) and **backward compatibility**
+
+> **🚧 Current pre-release: v2.1.0-RC.3 (2026-09-17) — the .NET 11 / C# 15 preview line.** Available on
+> the `release/v2.1.0.0-RC.3` branch, `net11.0` only. Highlights: the fixed-width inline capacity
+> ships at 16 by default on both storage paths (+12–19 % on the batched multi-row INSERT shape, per
+> the tracked measurement), the overflow arena appends a row's payloads in one call instead of one
+> file open per value, and in-place UPDATE/DELETE with deferred index maintenance put the
+> fixed-width fair-PK layout **ahead of SQLite on UPDATE (0.8×) and DELETE (0.5×)**.
+> Validated by **2,897 tests across 16 suites (0 failed, 16 skipped)** and the write-path regression
+> gate (PASSED). Honest caveats: INSERT is still ~1.4× behind SQLite on the fair-PK shape, the
+> PageBased engine's UPDATE is 4.9× behind, and the pure default (encrypted) config is 1.3–1.6×
+> behind the `NoEncryptMode` raw-speed posture. Full notes:
+> [`docs/2.1.0-RC.3_WHAT_CHANGED.md`](docs/2.1.0-RC.3_WHAT_CHANGED.md).
+
+> **Current stable release: v2.0.0.2 (2026-09-04)** — the v2.x engine line: fixed-width record layout is the
 > default for new PK tables, UPDATE/DELETE run in-place with commit-time tombstones, and a reopen
 > data-integrity hardening batch closed silent-data-loss edge cases (empty-value overflow reload,
 > single-file fixed-width arena markers, legacy 1.x delete-after-update purge).
@@ -106,7 +119,7 @@ Headline changes:
 - ⚡ **Removed hidden `D:\*.log` debug writes** that throttled every SELECT/execute/transaction/INSERT
 - 🛡️ **Native AOT readiness** — AOT-safe `TypeConverter`, `Option<T>` reader, `[RequiresDynamicCode]` annotations,
   source-generated DTOs/JSON (`tools/SharpCoreDB.AotSmoke` publishes + runs, exit 0)
-- ✅ validated by a **1,777-test core suite (0 failed)** plus CQRS (64), VectorSearch (143), EF Core (116) and Functional.Linq2DB (24)
+- ✅ validated by a **1,916-test core suite (0 failed)** — **2,897 tests across 16 suites** in total (CQRS 64, VectorSearch 248, EF Core 116, Provider.Sync 135, Search 58, HybridSearch 6, Functional.Linq2DB 24, …)
 - 🛡️ **Envelope encryption + full at-rest metadata encryption** — password-based per-file DEK (PBKDF2-HMAC-SHA256), encrypted block registry / FSM / WAL, key & password rotation APIs (#341 follow-on)
 - 🗜️ **Block-level Brotli/GZip compression** for single-file (`.scdb`) storage — transparent, per-block, applied before encryption / removed after decryption (#344)
 - ⚙️ **Configurable metadata region sizing** — `FsmSizePages` / `BlockRegistrySizePages` / `TableDirectorySizePages` remove the 512 MB single-file ceiling; byte-based file extension (~10 MB regardless of `PageSize`) (#345)
@@ -153,10 +166,15 @@ gRPC endpoint: `https://localhost:5001`
 Install client/server packages:
 
 ```bash
-dotnet add package SharpCoreDB.Server --version 2.0.0.2
+dotnet add package SharpCoreDB.Server.Core --version 2.0.0.2
 dotnet add package SharpCoreDB.Client --version 2.0.0.2
 ```
 
+> The server host is a standalone executable (`src/SharpCoreDB.Server`), distributed as the
+> `sharpcoredb-server` binary and the `ghcr.io/mpcoredeveloper/sharpcoredb-server` container image —
+> it is **not** published as the `SharpCoreDB.Server` NuGet package. The packable server-side
+> libraries are `SharpCoreDB.Server.Core` and `SharpCoreDB.Server.Protocol`.
+
 
 ---
 
@@ -170,14 +188,58 @@ dotnet add package SharpCoreDB.Client --version 2.0.0.2
 
 ---
 
-## Available NuGet packages (v2.0.0.2)
+## Available NuGet packages
+
+### v2.1.0-RC.3 — pre-release (`release/v2.1.0.0-RC.3`, net11.0 / C# 15 preview)
+
+```bash
+# Core
+dotnet add package SharpCoreDB --version 2.1.0-RC.3
+
+# Server/client
+dotnet add package SharpCoreDB.Server.Core --version 2.1.0-RC.3
+dotnet add package SharpCoreDB.Client --version 2.1.0-RC.3
+
+# Engines and extensions
+dotnet add package SharpCoreDB.Analytics --version 2.1.0-RC.3
+dotnet add package SharpCoreDB.VectorSearch --version 2.1.0-RC.3
+dotnet add package SharpCoreDB.Search --version 2.1.0-RC.3
+dotnet add package SharpCoreDB.HybridSearch --version 2.1.0-RC.3
+dotnet add package SharpCoreDB.Graph --version 2.1.0-RC.3
+dotnet add package SharpCoreDB.Graph.Advanced --version 2.1.0-RC.3
+dotnet add package SharpCoreDB.Distributed --version 2.1.0-RC.3
+dotnet add package SharpCoreDB.Provider.Sync --version 2.1.0-RC.3
+dotnet add package SharpCoreDB.EntityFrameworkCore --version 2.1.0-RC.3
+dotnet add package SharpCoreDB.Extensions --version 2.1.0-RC.3
+
+# Optional architecture packages
+dotnet add package SharpCoreDB.EventSourcing --version 2.1.0-RC.3
+dotnet add package SharpCoreDB.Projections --version 2.1.0-RC.3
+dotnet add package SharpCoreDB.CQRS --version 2.1.0-RC.3
+
+# Optional functional adapters
+dotnet add package SharpCoreDB.Functional --version 2.1.0-RC.3
+dotnet add package SharpCoreDB.Functional.Dapper --version 2.1.0-RC.3
+dotnet add package SharpCoreDB.Functional.EntityFrameworkCore --version 2.1.0-RC.3
+dotnet add package SharpCoreDB.Functional.Linq2DB --version 2.1.0-RC.3
+```
+
+> Pre-release versions are **not** selected by default — request the version explicitly (as above) or
+> tick *Include prerelease* in Visual Studio.
+>
+> The **server host is a standalone executable**, not a NuGet package: run
+> `dotnet run --project src/SharpCoreDB.Server -c Release` or use the
+> `ghcr.io/mpcoredeveloper/sharpcoredb-server` container image. The packable server-side libraries are
+> `SharpCoreDB.Server.Core` (hosting) and `SharpCoreDB.Server.Protocol` (wire contracts).
+
+### v2.0.0.2 — stable (`master`, net10.0 / C# 14)
 
 ```bash
 # Core
 dotnet add package SharpCoreDB --version 2.0.0.2
 
 # Server/client
-dotnet add package SharpCoreDB.Server --version 2.0.0.2
+dotnet add package SharpCoreDB.Server.Core --version 2.0.0.2
 dotnet add package SharpCoreDB.Client --version 2.0.0.2
 
 # Engines and extensions

SharpCoreDB.CI.slnf

@@ -4,6 +4,7 @@
     "projects": [
       "src\\SharpCoreDB\\SharpCoreDB.csproj",
       "src\\SharpCoreDB.Analytics\\SharpCoreDB.Analytics.csproj",
+      "src\\SharpCoreDB.Aspire.Hosting\\SharpCoreDB.Aspire.Hosting.csproj",
       "src\\SharpCoreDB.Client\\SharpCoreDB.Client.csproj",
       "src\\SharpCoreDB.Client.Protocol\\SharpCoreDB.Client.Protocol.csproj",
       "src\\SharpCoreDB.CQRS\\SharpCoreDB.CQRS.csproj",