@@ -2,7 +2,7 @@
 
 > Event-native metrics layer: business metrics that move when events happen — measured **1.1 s p50** event-to-metric freshness on production defaults. Live entity lookups, typed contracts, dual-language SDKs, and release-gated delivery for people, dashboards, services, and AI agents alike.
 
-[![Release gate](https://img.shields.io/badge/release_gate-v1.6_published-brightgreen)](docs/dv2-multi-branch/RELEASE_STATUS.md)
+[![Release gate](https://img.shields.io/badge/release_gate-v2.0_published-brightgreen)](docs/dv2-multi-branch/RELEASE_STATUS.md)
 [![codecov](https://codecov.io/gh/brownjuly2003-code/agentflow/branch/main/graph/badge.svg)](https://codecov.io/gh/brownjuly2003-code/agentflow)
 [![Python](https://img.shields.io/badge/python-3.11+-blue)](pyproject.toml)
 [![License](https://img.shields.io/badge/license-MIT-blue)](LICENSE)
@@ -24,7 +24,7 @@ Consumers are whoever needs the number now: humans, dashboards, downstream servi
 
 - **Measured event-to-metric freshness** — an event entering the pipeline is reflected in `GET /v1/metrics/*` in **1.06 s p50 / 1.99 s p95** on production defaults (event-driven cache invalidation, no webhook registration), tunable to **238 ms p50**; a plain TTL cache on the same pipeline sits at ~15 s. Reproducible via `python scripts/benchmark_freshness.py` → [freshness benchmark](docs/freshness-benchmark.md)
 - **Lineage as a contract** — all six metrics declare their source events, serving table, and a 2.5 s p95 staleness budget in versioned contracts, exposed through `/v1/catalog` and `/v1/contracts` and pinned by tests against the actual write path
-- **Published release line through `v1.6.0`** on PyPI (`agentflow-runtime`, `agentflow-client`) and npm (`@yuliaedomskikh/agentflow-client`) via OIDC Trusted Publishers with SLSA provenance on every artifact
+- **Published release line through `v2.0.0`** on PyPI (`agentflow-runtime`, `agentflow-client`) and npm (`@yuliaedomskikh/agentflow-client`) via OIDC Trusted Publishers with SLSA provenance on every artifact
 - **Tested and gated** — 1,500+ unit tests plus a broad Windows no-Docker suite; CI enforces 13 required status checks (lint, schema, unit, integration, helm, perf, terraform, bandit, safety, npm-audit, trivy, contract, build-smoke) through branch protection
 - **Dual SDK parity** across Python and TypeScript — retries, circuit breakers, batching, pagination, contract pinning, idempotency keys, `as_of` historical reads — over sub-second entity lookups (p50 `38–55 ms`, p99 `167 ms` on local hardware)
 - **Security in the hot path** — tenant isolation on every read surface, parameterized queries, `sqlglot` AST validation for NL-to-SQL, fail-closed auth, secret scrubbing, and a Bandit gate for new findings
@@ -148,12 +148,12 @@ python scripts/bandit_diff.py .bandit-baseline.json .tmp/bandit-current.json
 
 ## Status
 
-**`v1.6.0` is the current release line** — PyPI `agentflow-runtime` /
+**`v2.0.0` is the current release line** — PyPI `agentflow-runtime` /
 `agentflow-client` and npm `@yuliaedomskikh/agentflow-client`, all
 published via OIDC Trusted Publishers with SLSA provenance attestations.
 CI on `main` is green across all 13 required checks.
 
-The `v1.1.0` → `v1.6.0` arc landed in six increments on top of a security
+The `v1.1.0` → `v2.0.0` arc landed in seven increments on top of a security
 audit-closure sprint:
 
 - **`v1.1.0`** — audit closure: tenant isolation across every read
@@ -187,8 +187,20 @@ audit-closure sprint:
   generation engine (LangGraph, routed through GraceKelly), the DV2 raw
   vault on PostgreSQL with `LISTEN`/`NOTIFY` freshness, the MinIO-backed
   PyIceberg catalog, and the OpenSSF Scorecard channel (5.8 → 7.0).
-
-The tagged line and `main` are in sync as of `v1.6.0`. See the
+- **`v2.0.0`** — the demo universe re-founded and the scale path shipped:
+  the business legend re-pinned end-to-end to an own-brand
+  kitchen-appliance importer in ₽ (breaking for the retired
+  fashion-retail/USD surfaces), the external real-retailer dataset removed
+  outright (breaking: loader deleted, its at-scale benchmark retired as
+  historical), the control plane externalized to PostgreSQL behind the
+  `ControlPlaneStore` port (ADR 0010, six slices incl. the Helm scale
+  profile), three operational read surfaces split out of the agent catalog
+  (ADR 0011: Order 360, stuck-orders worklist, exception inbox), and the
+  three-node demo topology (ADR 0012) implemented and deployed live on
+  Hugging Face Spaces — plus the G2 audit closure (spec/seed consistency,
+  journal-scan hardening, live evidence re-captures).
+
+The tagged line and `main` are in sync as of `v2.0.0`. See the
 [changelog](CHANGELOG.md) for full detail.
 
 ### Scope
 
@@ -1,31 +1,35 @@
-# Release status — v1.6.0 PUBLISHED
+# Release status — v2.0.0 PUBLISHED
 
-**Status (verified 2026-07-02 via live registry queries):** v1.1.0
-through v1.6.0 are all published on the three registries (PyPI
+**Status (verified 2026-07-06 via live registry queries):** v1.1.0
+through v2.0.0 are all published on the three registries (PyPI
 `agentflow-runtime` + `agentflow-client`, npm
-`@yuliaedomskikh/agentflow-client`). v1.6.0 is the architecture-fixing
-release: ClickHouse becomes the shipped serving engine (ADR 0006
-Phase 1 — pipeline sink, `ReplacingMergeTree` row versions,
-backend-routed event scan, dedicated CI E2E lane), PII protection moves
-from the removed app-level string-parse gate to engine-enforced vault
-governance (ADR 0006 Phase 2 — fail-closed column grants,
-per-jurisdiction officer roles, row policies, `SQL SECURITY DEFINER`
-views; every live adversarial probe green), plus the vendored NL→SQL
-generation engine routed through GraceKelly (ADR 0008), the DV2 raw
-vault PostgreSQL migration with `LISTEN`/`NOTIFY` freshness, the
-MinIO-backed PyIceberg catalog, ADR 0009, and the OpenSSF Scorecard
-channel (published score 5.8 → 7.0).
-
-v1.5.0 is a security & correctness hardening release: argon2id key
-hashing with an O(1) peppered lookup index, an NL→SQL guard bypass fix
-(typed `read_csv` / `read_parquet` scan functions denied in projection
-position), `sqlglot` control-byte and mutation-target repairs, and a
-strict-`mypy` expansion. No public API changes from v1.4.0.
+`@yuliaedomskikh/agentflow-client`). v2.0.0 is the major release that
+re-founds the demo universe and ships the scale path: the business
+legend re-pinned end-to-end to an own-brand kitchen-appliance importer
+in ₽ (breaking for the retired fashion-retail/USD surfaces), the
+external real-retailer dataset removed outright (breaking: loader
+deleted, its at-scale benchmark retired as historical), the control
+plane externalized to PostgreSQL behind the `ControlPlaneStore` port
+(ADR 0010, slices 1–6 incl. the Helm scale profile), three operational
+read surfaces split out of the agent catalog (ADR 0011), the three-node
+demo topology implemented and deployed live on HF Spaces (ADR 0012),
+and the G2 audit closure (spec/seed consistency, journal-scan
+hardening, live evidence re-captures, demo serving-backend pin).
+
+v1.6.0 was the architecture-fixing release: ClickHouse became the
+shipped serving engine (ADR 0006 Phase 1), PII protection moved to
+engine-enforced vault governance (ADR 0006 Phase 2), plus the vendored
+NL→SQL generation engine (ADR 0008), the DV2 raw vault PostgreSQL
+migration, the MinIO-backed PyIceberg catalog, and the OpenSSF
+Scorecard channel (5.8 → 7.0).
 
 ## Live registry state
 
 | Registry | Package | Version | Upload time (UTC) | Tag commit |
 |----------|---------|---------|-------------------|------------|
+| PyPI     | [`agentflow-runtime`](https://pypi.org/project/agentflow-runtime/2.0.0/) | 2.0.0 | 2026-07-06 16:23 | `a47d000` |
+| PyPI     | [`agentflow-client`](https://pypi.org/project/agentflow-client/2.0.0/)   | 2.0.0 | 2026-07-06 16:23 | `a47d000` |
+| npm      | [`@yuliaedomskikh/agentflow-client`](https://www.npmjs.com/package/@yuliaedomskikh/agentflow-client/v/2.0.0) | 2.0.0 | 2026-07-06 16:23 | `a47d000` |
 | PyPI     | [`agentflow-runtime`](https://pypi.org/project/agentflow-runtime/1.6.0/) | 1.6.0 | 2026-07-02 00:55 | `734132a` |
 | PyPI     | [`agentflow-client`](https://pypi.org/project/agentflow-client/1.6.0/)   | 1.6.0 | 2026-07-02 00:55 | `734132a` |
 | npm      | [`@yuliaedomskikh/agentflow-client`](https://www.npmjs.com/package/@yuliaedomskikh/agentflow-client/v/1.6.0) | 1.6.0 | 2026-07-02 00:55 | `734132a` |
@@ -55,21 +59,22 @@ the package registries. Backfills are metadata only — no re-publish: the
 PyPI/npm artifacts and Trusted Publishing runs predate those Release objects
 and remain the package source of truth (the publish workflows trigger on tag
 push, not on `release`). GitHub Releases and the PyPI/npm registries are now
-consistent through `v1.6.0`, with `v1.6.0` marked Latest.
+consistent through `v2.0.0`, with `v2.0.0` marked Latest (created 2026-07-06
+alongside the tag; no backfills were needed this cycle).
 
 ## Re-verify
 
 ```bash
 # PyPI metadata
-curl -sf "https://pypi.org/pypi/agentflow-runtime/1.6.0/json" -o /dev/null && echo OK
-curl -sf "https://pypi.org/pypi/agentflow-client/1.6.0/json"  -o /dev/null && echo OK
+curl -sf "https://pypi.org/pypi/agentflow-runtime/2.0.0/json" -o /dev/null && echo OK
+curl -sf "https://pypi.org/pypi/agentflow-client/2.0.0/json"  -o /dev/null && echo OK
 
 # npm metadata
-npm view "@yuliaedomskikh/agentflow-client@1.6.0" version dist.tarball
+npm view "@yuliaedomskikh/agentflow-client@2.0.0" version dist.tarball
 
 # Install smoke
 python -m venv /tmp/.afcheck && . /tmp/.afcheck/bin/activate
-pip install agentflow-runtime==1.6.0 agentflow-client==1.6.0
+pip install agentflow-runtime==2.0.0 agentflow-client==2.0.0
 python -c "from importlib.metadata import version; print(version('agentflow-runtime'), version('agentflow-client'))"
 ```
 
@@ -149,7 +154,14 @@ shows the changes. The high-level shape:
 
 ## How the release fired
 
-Tag `v1.6.0` on commit `734132a` triggered both
+Tag `v2.0.0` on commit `a47d000` (PR #166, the exact 10-file v1.6.0 cut
+pattern) triggered both publish workflows on 2026-07-06; both runs
+completed `success` and the packages were visible in the registries at
+2026-07-06T16:23Z (verified live). The `test_version` gotcha applied as
+documented: `pip install -e ./sdk` re-run before the local gate (full
+unit suite, 1670 passed).
+
+Previous cycle: tag `v1.6.0` on commit `734132a` triggered both
 [`publish-pypi.yml`](../../.github/workflows/publish-pypi.yml) (OIDC
 Trusted Publishing, no token) and
 [`publish-npm.yml`](../../.github/workflows/publish-npm.yml) (npm
@@ -173,6 +185,7 @@ same one.
 | v1.4.0     | `e58693b` | published  |
 | v1.5.0     | `c99d094` | published  |
 | v1.6.0     | `734132a` | published  |
+| v2.0.0     | `a47d000` | published  |
 
 The next release should follow the same recipe:
 bump 5 files (root `pyproject.toml`, `sdk/pyproject.toml`,