SayantanCode · SayantanCode · Jul 26, 2026 · Jul 26, 2026
diff --git a/.changeset/pre.json b/.changeset/pre.json
@@ -15,6 +15,7 @@
   },
   "changesets": [
     "auth-versions-settings-polish",
+    "bounded-concurrency-and-loading-state",
     "clear-stale-error-on-create-delete-success",
     "csp-connect-src-and-stale-error-banner",
     "deprecated-tag-and-server-side-lock",
@@ -34,6 +35,7 @@
     "same-port-embedding-visibility",
     "stale-endpoint-detection",
     "swagger-parity-and-security-hardening",
-    "update-package-readmes"
+    "update-package-readmes",
+    "version-switcher-and-environments-fixes"
   ]
 }
diff --git a/packages/ast/CHANGELOG.md b/packages/ast/CHANGELOG.md
@@ -1,5 +1,11 @@
 # @vayo/ast
 
+## 0.1.1-beta.3
+
+### Patch Changes
+
+- @vayo-hq/types@0.1.1-beta.3
+
 ## 0.1.1-beta.2
 
 ### Patch Changes

diff --git a/packages/ast/package.json b/packages/ast/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@vayo-hq/ast",
-  "version": "0.1.1-beta.2",
+  "version": "0.1.1-beta.3",
   "license": "MIT",
   "description": "Static analysis pass: express-list-endpoints + ts-morph. Produces route/middleware/scope metadata to merge with runtime capture.",
   "repository": {

diff --git a/packages/capture-express/CHANGELOG.md b/packages/capture-express/CHANGELOG.md
@@ -1,5 +1,13 @@
 # @vayo/capture-express
 
+## 0.1.1-beta.3
+
+### Patch Changes
+
+- Updated dependencies [54d83dd]
+  - @vayo-hq/schema-engine@0.1.1-beta.3
+  - @vayo-hq/types@0.1.1-beta.3
+
 ## 0.1.1-beta.2
 
 ### Patch Changes

diff --git a/packages/capture-express/package.json b/packages/capture-express/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@vayo-hq/capture-express",
-  "version": "0.1.1-beta.2",
+  "version": "0.1.1-beta.3",
   "license": "MIT",
   "description": "Express middleware: captures real traffic, redacts sensitive fields, hands samples to @vayo-hq/schema-engine. The only Vayo package allowed to import Express types.",
   "repository": {

diff --git a/packages/cli/CHANGELOG.md b/packages/cli/CHANGELOG.md
@@ -1,5 +1,38 @@
 # vayo
 
+## 0.1.1-beta.3
+
+### Patch Changes
+
+- 54d83dd: Fixed two real issues found while running `vayo scan`/`vayo export`/the docs
+  UI against a real, large production API (600+ endpoints):
+
+  - `vayo scan`'s route-merge loop and `vayo export`/`vayo diff`'s per-endpoint
+    override/example/test-script lookups (and the identical logic in
+    `@vayo-hq/server`'s `GET /api/spec`/`GET /api/diff`) ran one DB round-trip
+    at a time in a sequential `for...of` loop — safe, but measured taking
+    minutes against a real remote MongoDB cluster at this scale, easily
+    mistaken for a hang. Added `mapWithConcurrency` to `@vayo-hq/schema-engine`
+    (bounded-concurrency `Promise.all`, 20 at a time — fast without firing
+    hundreds of simultaneous connections at the database) and switched every
+    one of these call sites to it.
+  - The docs UI's sidebar and main pane rendered "No endpoints yet"/"No
+    endpoints captured yet" immediately on load, before the first spec/folders
+    fetch had actually resolved — indistinguishable from a project with
+    nothing captured. A large real API can take several real seconds to
+    answer (see above), so this was a visible false-empty flash every time.
+    `DocsApp` now tracks whether the initial fetch is still pending and shows
+    "Loading endpoints…" instead, in the sidebar (`FolderTree`), the main pane,
+    and Full Docs mode (`FullDocView`).
+
+- Updated dependencies [54d83dd]
+  - @vayo-hq/schema-engine@0.1.1-beta.3
+  - @vayo-hq/server@0.1.1-beta.3
+  - @vayo-hq/db-mongo@0.1.1-beta.3
+  - @vayo-hq/openapi-compiler@0.1.1-beta.3
+  - @vayo-hq/types@0.1.1-beta.3
+  - @vayo-hq/ast@0.1.1-beta.3
+
 ## 0.1.1-beta.2
 
 ### Patch Changes

diff --git a/packages/cli/package.json b/packages/cli/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@vayo-hq/cli",
-  "version": "0.1.1-beta.2",
+  "version": "0.1.1-beta.3",
   "license": "MIT",
   "description": "npx vayo init / scan / export",
   "repository": {

diff --git a/packages/db-mongo/CHANGELOG.md b/packages/db-mongo/CHANGELOG.md
@@ -1,5 +1,13 @@
 # @vayo/db-mongo
 
+## 0.1.1-beta.3
+
+### Patch Changes
+
+- Updated dependencies [54d83dd]
+  - @vayo-hq/schema-engine@0.1.1-beta.3
+  - @vayo-hq/types@0.1.1-beta.3
+
 ## 0.1.1-beta.2
 
 ### Patch Changes

diff --git a/packages/db-mongo/package.json b/packages/db-mongo/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@vayo-hq/db-mongo",
-  "version": "0.1.1-beta.2",
+  "version": "0.1.1-beta.3",
   "license": "MIT",
   "description": "MongoDB implementation of VayoDbAdapter (native driver, not Mongoose) plus vayo init migrations. Implements the BYODB layer.",
   "repository": {

diff --git a/packages/openapi-compiler/CHANGELOG.md b/packages/openapi-compiler/CHANGELOG.md
@@ -1,5 +1,13 @@
 # @vayo/openapi-compiler
 
+## 0.1.1-beta.3
+
+### Patch Changes
+
+- Updated dependencies [54d83dd]
+  - @vayo-hq/schema-engine@0.1.1-beta.3
+  - @vayo-hq/types@0.1.1-beta.3
+
 ## 0.1.1-beta.2
 
 ### Patch Changes

diff --git a/packages/openapi-compiler/package.json b/packages/openapi-compiler/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@vayo-hq/openapi-compiler",
-  "version": "0.1.1-beta.2",
+  "version": "0.1.1-beta.3",
   "license": "MIT",
   "description": "Compiles resolved endpoints into a valid OpenAPI 3.1 document with x-vayo-* extensions. Validates via @apidevtools/swagger-parser before ever returning a document.",
   "repository": {

diff --git a/packages/schema-engine/CHANGELOG.md b/packages/schema-engine/CHANGELOG.md
@@ -1,5 +1,31 @@
 # @vayo/schema-engine
 
+## 0.1.1-beta.3
+
+### Patch Changes
+
+- 54d83dd: Fixed two real issues found while running `vayo scan`/`vayo export`/the docs
+  UI against a real, large production API (600+ endpoints):
+
+  - `vayo scan`'s route-merge loop and `vayo export`/`vayo diff`'s per-endpoint
+    override/example/test-script lookups (and the identical logic in
+    `@vayo-hq/server`'s `GET /api/spec`/`GET /api/diff`) ran one DB round-trip
+    at a time in a sequential `for...of` loop — safe, but measured taking
+    minutes against a real remote MongoDB cluster at this scale, easily
+    mistaken for a hang. Added `mapWithConcurrency` to `@vayo-hq/schema-engine`
+    (bounded-concurrency `Promise.all`, 20 at a time — fast without firing
+    hundreds of simultaneous connections at the database) and switched every
+    one of these call sites to it.
+  - The docs UI's sidebar and main pane rendered "No endpoints yet"/"No
+    endpoints captured yet" immediately on load, before the first spec/folders
+    fetch had actually resolved — indistinguishable from a project with
+    nothing captured. A large real API can take several real seconds to
+    answer (see above), so this was a visible false-empty flash every time.
+    `DocsApp` now tracks whether the initial fetch is still pending and shows
+    "Loading endpoints…" instead, in the sidebar (`FolderTree`), the main pane,
+    and Full Docs mode (`FullDocView`).
+  - @vayo-hq/types@0.1.1-beta.3
+
 ## 0.1.1-beta.2
 
 ### Patch Changes

diff --git a/packages/schema-engine/package.json b/packages/schema-engine/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@vayo-hq/schema-engine",
-  "version": "0.1.1-beta.2",
+  "version": "0.1.1-beta.3",
   "license": "MIT",
   "description": "Framework-agnostic schema inference/merge (genson-js) and the pure override-resolution function. No Express, no MongoDB.",
   "repository": {

diff --git a/packages/server/CHANGELOG.md b/packages/server/CHANGELOG.md
@@ -1,5 +1,38 @@
 # @vayo/server
 
+## 0.1.1-beta.3
+
+### Patch Changes
+
+- 54d83dd: Fixed two real issues found while running `vayo scan`/`vayo export`/the docs
+  UI against a real, large production API (600+ endpoints):
+
+  - `vayo scan`'s route-merge loop and `vayo export`/`vayo diff`'s per-endpoint
+    override/example/test-script lookups (and the identical logic in
+    `@vayo-hq/server`'s `GET /api/spec`/`GET /api/diff`) ran one DB round-trip
+    at a time in a sequential `for...of` loop — safe, but measured taking
+    minutes against a real remote MongoDB cluster at this scale, easily
+    mistaken for a hang. Added `mapWithConcurrency` to `@vayo-hq/schema-engine`
+    (bounded-concurrency `Promise.all`, 20 at a time — fast without firing
+    hundreds of simultaneous connections at the database) and switched every
+    one of these call sites to it.
+  - The docs UI's sidebar and main pane rendered "No endpoints yet"/"No
+    endpoints captured yet" immediately on load, before the first spec/folders
+    fetch had actually resolved — indistinguishable from a project with
+    nothing captured. A large real API can take several real seconds to
+    answer (see above), so this was a visible false-empty flash every time.
+    `DocsApp` now tracks whether the initial fetch is still pending and shows
+    "Loading endpoints…" instead, in the sidebar (`FolderTree`), the main pane,
+    and Full Docs mode (`FullDocView`).
+
+- Updated dependencies [54d83dd]
+- Updated dependencies [05b01a2]
+  - @vayo-hq/schema-engine@0.1.1-beta.3
+  - @vayo-hq/ui@0.1.1-beta.3
+  - @vayo-hq/db-mongo@0.1.1-beta.3
+  - @vayo-hq/openapi-compiler@0.1.1-beta.3
+  - @vayo-hq/types@0.1.1-beta.3
+
 ## 0.1.1-beta.2
 
 ### Patch Changes

diff --git a/packages/server/package.json b/packages/server/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@vayo-hq/server",
-  "version": "0.1.1-beta.2",
+  "version": "0.1.1-beta.3",
   "license": "MIT",
   "description": "REST API + Socket.IO gateway + static UI hosting. Every mutating route is role-checked server-side (docs/05-security.md).",
   "repository": {

diff --git a/packages/types/CHANGELOG.md b/packages/types/CHANGELOG.md
@@ -1,5 +1,7 @@
 # @vayo/types
 
+## 0.1.1-beta.3
+
 ## 0.1.1-beta.2
 
 ### Patch Changes

diff --git a/packages/types/package.json b/packages/types/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@vayo-hq/types",
-  "version": "0.1.1-beta.2",
+  "version": "0.1.1-beta.3",
   "license": "MIT",
   "description": "Shared TypeScript interfaces for Vayo. No runtime code, no dependencies on any other Vayo package.",
   "repository": {

diff --git a/packages/ui/CHANGELOG.md b/packages/ui/CHANGELOG.md
@@ -1,5 +1,60 @@
 # @vayo/ui
 
+## 0.1.1-beta.3
+
+### Patch Changes
+
+- 54d83dd: Fixed two real issues found while running `vayo scan`/`vayo export`/the docs
+  UI against a real, large production API (600+ endpoints):
+
+  - `vayo scan`'s route-merge loop and `vayo export`/`vayo diff`'s per-endpoint
+    override/example/test-script lookups (and the identical logic in
+    `@vayo-hq/server`'s `GET /api/spec`/`GET /api/diff`) ran one DB round-trip
+    at a time in a sequential `for...of` loop — safe, but measured taking
+    minutes against a real remote MongoDB cluster at this scale, easily
+    mistaken for a hang. Added `mapWithConcurrency` to `@vayo-hq/schema-engine`
+    (bounded-concurrency `Promise.all`, 20 at a time — fast without firing
+    hundreds of simultaneous connections at the database) and switched every
+    one of these call sites to it.
+  - The docs UI's sidebar and main pane rendered "No endpoints yet"/"No
+    endpoints captured yet" immediately on load, before the first spec/folders
+    fetch had actually resolved — indistinguishable from a project with
+    nothing captured. A large real API can take several real seconds to
+    answer (see above), so this was a visible false-empty flash every time.
+    `DocsApp` now tracks whether the initial fetch is still pending and shows
+    "Loading endpoints…" instead, in the sidebar (`FolderTree`), the main pane,
+    and Full Docs mode (`FullDocView`).
+
+- 05b01a2: Fixed three more real issues found while using the docs UI against a real
+  production API:
+
+  - **The active version could get permanently stuck on "Unversioned."** The
+    very first endpoint ever captured resolves to a default version key
+    (schema-engine's `resolveVersion` fallback — usually "v1") before anyone
+    has explicitly created that version via "Manage versions…" — real data
+    exists under it, but no `ApiVersionDoc` does yet, so it never appeared as
+    a selectable option in the version switcher. Once a user switched to
+    "Unversioned" (always listed, unconditionally), there was no way back
+    short of manually creating a version with that exact name.
+    `VersionSwitcher` now always surfaces the app's default version key as a
+    selectable option when it isn't a real stored version yet.
+  - **Switching versions could leave the previous version's tree/content on
+    screen** for however long the new version's spec/folders fetch took —
+    genuinely indistinguishable from the switch having silently failed,
+    especially on a large real API where that fetch can take several real
+    seconds. The loading state added previously only covered the very first
+    load; it's now also cleared and re-armed on every version switch.
+  - **The Environments modal allowed duplicate names and double-submission.**
+    Nothing disabled the Save button while a create/update request was in
+    flight, so a double-click read the same identical form state twice and
+    created two duplicate environments; the form also never reset after a
+    successful creation. Added a `saving` state that disables Save/Delete/
+    Close and shows "Saving…" during the request, resets the form after a
+    successful creation, and added a duplicate-name check that surfaces a
+    clear inline error instead of silently allowing it.
+  - @vayo-hq/openapi-compiler@0.1.1-beta.3
+  - @vayo-hq/types@0.1.1-beta.3
+
 ## 0.1.1-beta.2
 
 ### Patch Changes

diff --git a/packages/ui/package.json b/packages/ui/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@vayo-hq/ui",
-  "version": "0.1.1-beta.2",
+  "version": "0.1.1-beta.3",
   "license": "MIT",
   "description": "Schema-driven React docs UI. Five tabs per endpoint: Details, Flowmap, History, Team Chat, Try It Now (docs/08-packages-and-repo-structure.md).",
   "repository": {