chore: version packages — 0.1.2 (adapter route-span fix)

packages/next/CHANGELOG.md

@@ -1,5 +1,21 @@
 # @tindalabs/blindspot-next
 
+## 0.1.2
+
+### Patch Changes
+
+- 2003457: Fix: in-route activity (clicks, fetch, errors, form submits) now nests under the
+  navigation span instead of orphaning into its own root trace.
+
+  The Vue, Svelte, and Next.js (pages-router) integrations cleared the route span
+  in a step separate from re-creating it — Vue/Svelte in a `beforeEach` /
+  `beforeNavigate` guard, the Next pages-router on `routeChangeStart` — leaving a
+  window where the active context was root. Any span started in that window (and
+  intermittently the navigation-triggering click) became a standalone root trace.
+  The clear and re-create now happen atomically when the new route span is
+  established (`afterEach` / `afterNavigate` / `routeChangeComplete`), so a route
+  span is active at all times — matching the React and Next app-router adapters.
+
 ## 0.1.1
 
 ### Patch Changes

packages/next/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tindalabs/blindspot-next",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "description": "Blindspot — Next.js integration supporting both App Router and Pages Router for server-rendered and hybrid applications.",
   "keywords": [
     "opentelemetry",

packages/svelte/CHANGELOG.md

@@ -1,5 +1,21 @@
 # @tindalabs/blindspot-svelte
 
+## 0.1.2
+
+### Patch Changes
+
+- 2003457: Fix: in-route activity (clicks, fetch, errors, form submits) now nests under the
+  navigation span instead of orphaning into its own root trace.
+
+  The Vue, Svelte, and Next.js (pages-router) integrations cleared the route span
+  in a step separate from re-creating it — Vue/Svelte in a `beforeEach` /
+  `beforeNavigate` guard, the Next pages-router on `routeChangeStart` — leaving a
+  window where the active context was root. Any span started in that window (and
+  intermittently the navigation-triggering click) became a standalone root trace.
+  The clear and re-create now happen atomically when the new route span is
+  established (`afterEach` / `afterNavigate` / `routeChangeComplete`), so a route
+  span is active at all times — matching the React and Next app-router adapters.
+
 ## 0.1.1
 
 ### Patch Changes

packages/svelte/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tindalabs/blindspot-svelte",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "description": "Blindspot — Svelte and SvelteKit integration with stores and lifecycle hooks for automatic telemetry.",
   "keywords": [
     "opentelemetry",

packages/vue/CHANGELOG.md

@@ -1,5 +1,21 @@
 # @tindalabs/blindspot-vue
 
+## 0.1.2
+
+### Patch Changes
+
+- 2003457: Fix: in-route activity (clicks, fetch, errors, form submits) now nests under the
+  navigation span instead of orphaning into its own root trace.
+
+  The Vue, Svelte, and Next.js (pages-router) integrations cleared the route span
+  in a step separate from re-creating it — Vue/Svelte in a `beforeEach` /
+  `beforeNavigate` guard, the Next pages-router on `routeChangeStart` — leaving a
+  window where the active context was root. Any span started in that window (and
+  intermittently the navigation-triggering click) became a standalone root trace.
+  The clear and re-create now happen atomically when the new route span is
+  established (`afterEach` / `afterNavigate` / `routeChangeComplete`), so a route
+  span is active at all times — matching the React and Next app-router adapters.
+
 ## 0.1.1
 
 ### Patch Changes

packages/vue/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tindalabs/blindspot-vue",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "description": "Blindspot — Vue 3 integration. BlindspotPlugin and useBlindspot composable for Vue 3 and Vue Router.",
   "keywords": [
     "opentelemetry",