docs: clarify pre-first-tag bundled SPA removal in deprecation policy

Document path B: 0.1.0.dev0 has no git tag yet; export_count removal in [Unreleased] is acceptable for bundled SPA+API atomic deploy. Update example table and CHANGELOG wording per review.

Co-authored-by: Cursor <cursoragent@cursor.com>

Author: clean6378-max-it

CHANGELOG.md

@@ -19,6 +19,6 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
 ### Removed
 
-- `export_count` on `GET /api/export/state` — use `last_export_session_count` (deprecated in PR #60 / [deprecation policy](docs/deprecation-policy.md); bundled SPA updated in same release)
+- `export_count` on `GET /api/export/state` — use `last_export_session_count` (deprecated in PR #60; removed before first `v0.1.0` tag per [deprecation policy](docs/deprecation-policy.md) bundled SPA path; SPA updated in same `[Unreleased]` cut)
 
 [Unreleased]: https://github.com/cppalliance/claude-code-chat-browser/compare/f70505982d435f8b1f754cb18c0c9f65609f11b4...HEAD

docs/deprecation-policy.md

@@ -27,11 +27,17 @@ A deprecated field may be removed when:
 
 For fields actively read by the bundled SPA (which does not track an external API version), removal happens no earlier than **two tagged releases** after the release that documented the deprecation in CHANGELOG (for example, deprecated in `0.1.0`, removable from `0.3.0` at earliest when versions advance `0.1.0` → `0.2.0` → `0.3.0`), and no earlier than **14 calendar days** after that deprecation announcement.
 
-## Example (in progress)
+### Bundled SPA + pre-first-tag (path B)
 
-| Field | Endpoint | Status | Replacement |
-|-------|----------|--------|-------------|
-| `export_count` | `GET /api/export/state` | deprecated | `last_export_session_count` |
+Until the first git tag ships (for example while `app.__version__` is `0.1.0.dev0`), the CHANGELOG `[Unreleased]` section is the source of truth — see [Versioning](#versioning) below. The bundled SPA is deployed from the same repo and commit as the API; it does not consume a separately versioned HTTP contract.
+
+For fields **only read by the bundled SPA** (no external integrators on a tagged API yet), an atomic PR that (1) stops reading the field in `static/js/*.js` and (2) removes it from the JSON response is acceptable **before** the first tag, provided deprecation was announced in CHANGELOG and api-reference (PR #60) and removal is recorded under `[Unreleased]`. External integrators who pin a **tagged** release must follow the two-release + 14-day rule above.
+
+## Example (completed — pre-first-tag)
+
+| Field | Endpoint | Status | Replacement | Notes |
+|-------|----------|--------|-------------|-------|
+| `export_count` | `GET /api/export/state` | removed | `last_export_session_count` | Deprecated in PR #60 (`[Unreleased]`); removed in bundled SPA+API PR before first `v0.1.0` tag |
 
 ## Versioning