fix planning docs

Signed-off-by: Connor Tsui <connor.tsui20@gmail.com>

Author: connortsui20

benchmarks-website/planning/00-overview.md

@@ -8,14 +8,14 @@ SPDX-FileCopyrightText: Copyright the Vortex contributors
 ## What we're building
 
 A replacement for the current `bench.vortex.dev` site. The new
-stack is a **single Rust binary** that owns a **DuckDB database**
-on local disk and serves the website plus an `/api/ingest` route.
-CI eventually POSTs new benchmark results there. There is no
-separate ingester service, no S3 coordination layer for writes, no
-client-side WASM.
+stack is a **single Rust binary** (axum + maud + duckdb-rs) that
+owns a **DuckDB database** on local disk and serves the website
+plus an `/api/ingest` route. CI eventually POSTs new benchmark
+results there. There is no separate ingester service, no S3
+coordination layer for writes, no client-side WASM.
 
-HTTP framework, templating engine, and module layout are the
-server agent's call.
+The server crate is `vortex-bench-server` at
+`benchmarks-website/server/`.
 
 ## Phasing
 
@@ -98,6 +98,7 @@ alpha; they come back in phase 2.
 ## Status of v2 during alpha
 
 v2 stays in production untouched. Do not edit
-`benchmarks-website/server.js` or `benchmarks-website/src/`. v3
-lives alongside under `benchmarks-website/` in a new Cargo crate
-(path is the server agent's call).
+`benchmarks-website/server.js`, `benchmarks-website/src/`, or any
+other v2 files at `benchmarks-website/` top level. v3 lives in the
+sibling subdirectory at `benchmarks-website/server/`
+(`vortex-bench-server` crate).

benchmarks-website/planning/AGENTS.md

@@ -11,12 +11,13 @@ detail belongs in component plans.
 ## What you're working on
 
 The **alpha** of v3 of `bench.vortex.dev`. Target: a single Rust
-binary with **DuckDB on local disk**. The smallest end-to-end loop
-that proves the design.
+binary (axum + maud + duckdb-rs) with **DuckDB on local disk**.
+The smallest end-to-end loop that proves the design.
 
-The v2 site at `benchmarks-website/` is in production and stays
-running unchanged. v3 lives alongside in a new crate under
-`benchmarks-website/` (path is the server agent's call).
+The v2 site (top-level files in `benchmarks-website/`:
+`server.js`, `src/`, `package.json`, etc.) is in production and
+stays running unchanged. v3 lives alongside in
+`vortex-bench-server` at `benchmarks-website/server/`.
 
 Anything not listed in [`README.md`](./README.md) under
 "Components" is **deferred**. See [`deferred.md`](./deferred.md).
@@ -43,8 +44,8 @@ You **don't** need to read other components' plans.
 See the root [`CLAUDE.md`](/CLAUDE.md) for Rust style, test layout,
 and CI norms. Project-specific:
 
-- New crates go under `benchmarks-website/`. Add to root
-  `Cargo.toml` workspace members.
+- The v3 server crate lives at `benchmarks-website/server/` and is
+  registered in the root `Cargo.toml` `members` list.
 - All commits need a `Signed-off-by:` trailer.
 - Run `cargo +nightly fmt --all` and narrow clippy on what you
   changed.
@@ -70,10 +71,8 @@ and CI norms. Project-specific:
 | Branch | Purpose |
 |---|---|
 | `develop` | Live v2 site. Don't break. |
-| `claude/review-benchmarks-redesign-BO3la` | This planning branch. |
-| `claude/benchmarks-v3-<component>` | Per-workstream feature branches. |
-
-Component branches start from `develop`.
+| `ct/benchmarks-v3` | Integration branch carrying the planning commit + landed component PRs. All component branches start here. |
+| `claude/benchmarks-v3-<component>` | Per-workstream feature branches, each branched from `ct/benchmarks-v3` and PR'd back to it. |
 
 ## How to update this file
 

benchmarks-website/planning/README.md

@@ -40,9 +40,11 @@ worked on in parallel**.
 ## Working branches
 
 - `develop` - the v2 site, in production. **Do not touch.**
-- `claude/review-benchmarks-redesign-BO3la` - this planning branch.
-- Component branches above - one per workstream, branched from
-  `develop`.
+- `ct/benchmarks-v3` - the integration branch carrying the
+  planning commit and any landed component PRs. All component
+  branches start here.
+- Component branches (one per workstream, see "Components" above),
+  each branched from `ct/benchmarks-v3` and PR'd back to it.
 
 ## What this plan is not
 

benchmarks-website/planning/decisions.md

@@ -72,15 +72,18 @@ decisions deliberately stay open until we get there - see
   `/api/groups` as opaque strings and feeds them back unmodified
   into `/api/chart/:slug`. The server picks the slug format.
 
-## Recommended (not pinned)
+## In use (locked in by the server PR)
 
-These are starting points, not contracts. If the server agent has
-a stronger preference, change them.
+These were "recommended" before the server PR landed; they are now
+the actual stack in `benchmarks-website/server/Cargo.toml`. The
+web-ui agent inherits them by working in the same crate.
 
 - HTTP framework: `axum`.
-- Compile-time HTML templates: `maud` (`askama` is fine).
-- DuckDB driver: `duckdb-rs`. Pin a version that supports
-  `INSERT ... ON CONFLICT (...) DO UPDATE`.
+- Compile-time HTML templates: `maud`.
+- DuckDB driver: `duckdb-rs`, version pinned in the server crate's
+  `Cargo.toml`.
+- Snapshot tests: `insta` (workspace dep).
+- Logging: `tracing` (workspace dep).
 
 ## Open