build: open 2.1.0, and move the package-validation baseline to 2.0.0

CHANGELOG.md

@@ -10,6 +10,8 @@ A version's heading reads `## <version> — Unreleased` until the release is pre
 the release date. The release workflow refuses a tag whose section still says `Unreleased`, and the
 section is the GitHub release's notes.
 
+## 2.1.0 — Unreleased
+
 ## 2.0.0 — 2026-10-14
 
 Still `net10.0` and Metalama 2026.1. What builds or runs differently, and what to write instead:

Directory.Build.props

@@ -1,6 +1,6 @@
 <Project>
     <PropertyGroup>
-        <Version>2.0.0</Version>
+        <Version>2.1.0</Version>
         <Authors>CaffeinatedCoder</Authors>
         <Copyright>Copyright (c) 2026 CaffeinatedCoder</Copyright>
         <PackageLicenseExpression>MIT</PackageLicenseExpression>
@@ -43,7 +43,7 @@
     -->
     <PropertyGroup>
         <EnablePackageValidation>true</EnablePackageValidation>
-        <PackageValidationBaselineVersion>1.5.1</PackageValidationBaselineVersion>
+        <PackageValidationBaselineVersion>2.0.0</PackageValidationBaselineVersion>
     </PropertyGroup>
 
     <!-- Provenance: a consumer stepping into this code gets the exact source it is running. -->

design/plan.md

@@ -6,7 +6,7 @@ you touch; the rest is reference.
 
 | Page | Holds | Changes |
 |---|---|---|
-| [Roadmap](roadmap.md) | What is open: before the tag, 2.1, 2.x with a spike first, 3.0.0 | as work is taken or done |
+| [Roadmap](roadmap.md) | What is open: 2.1, 2.x with a spike first, 3.0.0 | as work is taken or done |
 | [Decisions](adr/README.md) | One record per decision, dated, with the evidence that settled it; a decision is changed by a new one that names it | append only |
 | [Packages](packages.md) | The package map, what each depends on, and the namespaces | rarely |
 | [Discovery is by interface](discovery.md) | Why nothing is found by name, and how the analyzer and the satellites find a value object | with the area |

design/roadmap.md

@@ -3,12 +3,6 @@
 What is open, and nothing else. Done work is in the [changelog](../CHANGELOG.md) and in git. Each
 item names the decision that scoped it.
 
-## 2.0.0, before the tag
-
-- The release: merge so the help links' headings exist on `main`, and tag `v2.0.0`. The changelog's
-  section is dated and the analyzer rows are shipped; the release workflow and `ChangelogTests` check
-  both.
-
 ## 2.1, additive
 
 - An optional `Cause` on `Fault<TFault>`, an exception kept beside the reason and the detail for the