SayantanCode · SayantanCode · Jul 26, 2026 · Jul 26, 2026
diff --git a/.changeset/pre.json b/.changeset/pre.json
@@ -19,6 +19,7 @@
     "csp-connect-src-and-stale-error-banner",
     "deprecated-tag-and-server-side-lock",
     "exclude-test-helpers-from-server-package",
+    "fix-readme-stale-package-links",
     "flows-modal-viewer-controls",
     "header-toolbar-overflow",
     "import-missing-contact-license-tos",

diff --git a/packages/ast/CHANGELOG.md b/packages/ast/CHANGELOG.md
@@ -1,5 +1,27 @@
 # @vayo/ast
 
+## 0.1.1-beta.2
+
+### Patch Changes
+
+- 5ad2159: Fixed every package README still linking to the old, never-actually-published
+  bare `vayo` npm package name (npm rejected it as a first-publish
+  typosquat — see the CLI rename changeset) instead of the real
+  `@vayo-hq/cli`. Also fixed `@vayo-hq/db-mongo`'s README claiming "most people
+  never call this directly," which contradicted the `createAdapter`/
+  `runMigrations` wiring snippet every other doc (and `vayo init`'s own printed
+  next steps) shows being called directly in a real project. Root README's
+  "Using Vayo" section no longer describes the pre-publish tarball workflow —
+  all 9 packages are live on npm now, so it gives the real, verified
+  `npm install ...@beta` command instead. Every install example across the
+  repo now explicit about the `@beta` tag rather than relying on `latest`,
+  since `latest` only moves when explicitly re-tagged during this prerelease
+  period (discovered live: the very first publish grabbed `latest`
+  automatically and every subsequent `--tag beta` publish left it pointing at
+  an old, broken version).
+- Updated dependencies [5ad2159]
+  - @vayo-hq/types@0.1.1-beta.2
+
 ## 0.1.1-beta.1
 
 ### 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.1",
+  "version": "0.1.1-beta.2",
   "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,28 @@
 # @vayo/capture-express
 
+## 0.1.1-beta.2
+
+### Patch Changes
+
+- 5ad2159: Fixed every package README still linking to the old, never-actually-published
+  bare `vayo` npm package name (npm rejected it as a first-publish
+  typosquat — see the CLI rename changeset) instead of the real
+  `@vayo-hq/cli`. Also fixed `@vayo-hq/db-mongo`'s README claiming "most people
+  never call this directly," which contradicted the `createAdapter`/
+  `runMigrations` wiring snippet every other doc (and `vayo init`'s own printed
+  next steps) shows being called directly in a real project. Root README's
+  "Using Vayo" section no longer describes the pre-publish tarball workflow —
+  all 9 packages are live on npm now, so it gives the real, verified
+  `npm install ...@beta` command instead. Every install example across the
+  repo now explicit about the `@beta` tag rather than relying on `latest`,
+  since `latest` only moves when explicitly re-tagged during this prerelease
+  period (discovered live: the very first publish grabbed `latest`
+  automatically and every subsequent `--tag beta` publish left it pointing at
+  an old, broken version).
+- Updated dependencies [5ad2159]
+  - @vayo-hq/types@0.1.1-beta.2
+  - @vayo-hq/schema-engine@0.1.1-beta.2
+
 ## 0.1.1-beta.1
 
 ### 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.1",
+  "version": "0.1.1-beta.2",
   "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,32 @@
 # vayo
 
+## 0.1.1-beta.2
+
+### Patch Changes
+
+- 5ad2159: Fixed every package README still linking to the old, never-actually-published
+  bare `vayo` npm package name (npm rejected it as a first-publish
+  typosquat — see the CLI rename changeset) instead of the real
+  `@vayo-hq/cli`. Also fixed `@vayo-hq/db-mongo`'s README claiming "most people
+  never call this directly," which contradicted the `createAdapter`/
+  `runMigrations` wiring snippet every other doc (and `vayo init`'s own printed
+  next steps) shows being called directly in a real project. Root README's
+  "Using Vayo" section no longer describes the pre-publish tarball workflow —
+  all 9 packages are live on npm now, so it gives the real, verified
+  `npm install ...@beta` command instead. Every install example across the
+  repo now explicit about the `@beta` tag rather than relying on `latest`,
+  since `latest` only moves when explicitly re-tagged during this prerelease
+  period (discovered live: the very first publish grabbed `latest`
+  automatically and every subsequent `--tag beta` publish left it pointing at
+  an old, broken version).
+- Updated dependencies [5ad2159]
+  - @vayo-hq/types@0.1.1-beta.2
+  - @vayo-hq/ast@0.1.1-beta.2
+  - @vayo-hq/schema-engine@0.1.1-beta.2
+  - @vayo-hq/openapi-compiler@0.1.1-beta.2
+  - @vayo-hq/db-mongo@0.1.1-beta.2
+  - @vayo-hq/server@0.1.1-beta.2
+
 ## 0.1.1-beta.1
 
 ### 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.1",
+  "version": "0.1.1-beta.2",
   "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,28 @@
 # @vayo/db-mongo
 
+## 0.1.1-beta.2
+
+### Patch Changes
+
+- 5ad2159: Fixed every package README still linking to the old, never-actually-published
+  bare `vayo` npm package name (npm rejected it as a first-publish
+  typosquat — see the CLI rename changeset) instead of the real
+  `@vayo-hq/cli`. Also fixed `@vayo-hq/db-mongo`'s README claiming "most people
+  never call this directly," which contradicted the `createAdapter`/
+  `runMigrations` wiring snippet every other doc (and `vayo init`'s own printed
+  next steps) shows being called directly in a real project. Root README's
+  "Using Vayo" section no longer describes the pre-publish tarball workflow —
+  all 9 packages are live on npm now, so it gives the real, verified
+  `npm install ...@beta` command instead. Every install example across the
+  repo now explicit about the `@beta` tag rather than relying on `latest`,
+  since `latest` only moves when explicitly re-tagged during this prerelease
+  period (discovered live: the very first publish grabbed `latest`
+  automatically and every subsequent `--tag beta` publish left it pointing at
+  an old, broken version).
+- Updated dependencies [5ad2159]
+  - @vayo-hq/types@0.1.1-beta.2
+  - @vayo-hq/schema-engine@0.1.1-beta.2
+
 ## 0.1.1-beta.1
 
 ### 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.1",
+  "version": "0.1.1-beta.2",
   "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,28 @@
 # @vayo/openapi-compiler
 
+## 0.1.1-beta.2
+
+### Patch Changes
+
+- 5ad2159: Fixed every package README still linking to the old, never-actually-published
+  bare `vayo` npm package name (npm rejected it as a first-publish
+  typosquat — see the CLI rename changeset) instead of the real
+  `@vayo-hq/cli`. Also fixed `@vayo-hq/db-mongo`'s README claiming "most people
+  never call this directly," which contradicted the `createAdapter`/
+  `runMigrations` wiring snippet every other doc (and `vayo init`'s own printed
+  next steps) shows being called directly in a real project. Root README's
+  "Using Vayo" section no longer describes the pre-publish tarball workflow —
+  all 9 packages are live on npm now, so it gives the real, verified
+  `npm install ...@beta` command instead. Every install example across the
+  repo now explicit about the `@beta` tag rather than relying on `latest`,
+  since `latest` only moves when explicitly re-tagged during this prerelease
+  period (discovered live: the very first publish grabbed `latest`
+  automatically and every subsequent `--tag beta` publish left it pointing at
+  an old, broken version).
+- Updated dependencies [5ad2159]
+  - @vayo-hq/types@0.1.1-beta.2
+  - @vayo-hq/schema-engine@0.1.1-beta.2
+
 ## 0.1.1-beta.1
 
 ### 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.1",
+  "version": "0.1.1-beta.2",
   "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,27 @@
 # @vayo/schema-engine
 
+## 0.1.1-beta.2
+
+### Patch Changes
+
+- 5ad2159: Fixed every package README still linking to the old, never-actually-published
+  bare `vayo` npm package name (npm rejected it as a first-publish
+  typosquat — see the CLI rename changeset) instead of the real
+  `@vayo-hq/cli`. Also fixed `@vayo-hq/db-mongo`'s README claiming "most people
+  never call this directly," which contradicted the `createAdapter`/
+  `runMigrations` wiring snippet every other doc (and `vayo init`'s own printed
+  next steps) shows being called directly in a real project. Root README's
+  "Using Vayo" section no longer describes the pre-publish tarball workflow —
+  all 9 packages are live on npm now, so it gives the real, verified
+  `npm install ...@beta` command instead. Every install example across the
+  repo now explicit about the `@beta` tag rather than relying on `latest`,
+  since `latest` only moves when explicitly re-tagged during this prerelease
+  period (discovered live: the very first publish grabbed `latest`
+  automatically and every subsequent `--tag beta` publish left it pointing at
+  an old, broken version).
+- Updated dependencies [5ad2159]
+  - @vayo-hq/types@0.1.1-beta.2
+
 ## 0.1.1-beta.1
 
 ### 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.1",
+  "version": "0.1.1-beta.2",
   "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,31 @@
 # @vayo/server
 
+## 0.1.1-beta.2
+
+### Patch Changes
+
+- 5ad2159: Fixed every package README still linking to the old, never-actually-published
+  bare `vayo` npm package name (npm rejected it as a first-publish
+  typosquat — see the CLI rename changeset) instead of the real
+  `@vayo-hq/cli`. Also fixed `@vayo-hq/db-mongo`'s README claiming "most people
+  never call this directly," which contradicted the `createAdapter`/
+  `runMigrations` wiring snippet every other doc (and `vayo init`'s own printed
+  next steps) shows being called directly in a real project. Root README's
+  "Using Vayo" section no longer describes the pre-publish tarball workflow —
+  all 9 packages are live on npm now, so it gives the real, verified
+  `npm install ...@beta` command instead. Every install example across the
+  repo now explicit about the `@beta` tag rather than relying on `latest`,
+  since `latest` only moves when explicitly re-tagged during this prerelease
+  period (discovered live: the very first publish grabbed `latest`
+  automatically and every subsequent `--tag beta` publish left it pointing at
+  an old, broken version).
+- Updated dependencies [5ad2159]
+  - @vayo-hq/types@0.1.1-beta.2
+  - @vayo-hq/schema-engine@0.1.1-beta.2
+  - @vayo-hq/openapi-compiler@0.1.1-beta.2
+  - @vayo-hq/db-mongo@0.1.1-beta.2
+  - @vayo-hq/ui@0.1.1-beta.2
+
 ## 0.1.1-beta.1
 
 ### 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.1",
+  "version": "0.1.1-beta.2",
   "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,25 @@
 # @vayo/types
 
+## 0.1.1-beta.2
+
+### Patch Changes
+
+- 5ad2159: Fixed every package README still linking to the old, never-actually-published
+  bare `vayo` npm package name (npm rejected it as a first-publish
+  typosquat — see the CLI rename changeset) instead of the real
+  `@vayo-hq/cli`. Also fixed `@vayo-hq/db-mongo`'s README claiming "most people
+  never call this directly," which contradicted the `createAdapter`/
+  `runMigrations` wiring snippet every other doc (and `vayo init`'s own printed
+  next steps) shows being called directly in a real project. Root README's
+  "Using Vayo" section no longer describes the pre-publish tarball workflow —
+  all 9 packages are live on npm now, so it gives the real, verified
+  `npm install ...@beta` command instead. Every install example across the
+  repo now explicit about the `@beta` tag rather than relying on `latest`,
+  since `latest` only moves when explicitly re-tagged during this prerelease
+  period (discovered live: the very first publish grabbed `latest`
+  automatically and every subsequent `--tag beta` publish left it pointing at
+  an old, broken version).
+
 ## 0.1.1-beta.1
 
 ### 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.1",
+  "version": "0.1.1-beta.2",
   "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,13 @@
 # @vayo/ui
 
+## 0.1.1-beta.2
+
+### Patch Changes
+
+- Updated dependencies [5ad2159]
+  - @vayo-hq/types@0.1.1-beta.2
+  - @vayo-hq/openapi-compiler@0.1.1-beta.2
+
 ## 0.1.1-beta.1
 
 ### 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.1",
+  "version": "0.1.1-beta.2",
   "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": {