chore: version packages → v0.16.1

ornn-api/CHANGELOG.md

@@ -1,5 +1,11 @@
 # ornn-api
 
+## 0.16.1
+
+### Patch Changes
+
+- [#1217](https://github.com/ChronoAIProject/Ornn/pull/1217) [`54f0cb4`](https://github.com/ChronoAIProject/Ornn/commit/54f0cb4397d8d26d43f03af73ca1259e53875187) Thanks [@chronoai-shining](https://github.com/chronoai-shining)! - Fix every URL published in the OpenAPI document ([#1213](https://github.com/ChronoAIProject/Ornn/issues/1213)). `GET /api/v1/openapi.json` is the contract agent developers read first — NyxID renders it on the ornn-api service page — and none of it resolved. Paths were published under `/api/*` while the router has served `/api/v1/*` since the version cut in [#101](https://github.com/ChronoAIProject/Ornn/issues/101), so following the spec produced 404s. `servers[0].url` was hardcoded to `http://localhost:3802`, a host no client can reach; it now comes from `ORNN_API_BASE_URL` (the same var ornn-web already uses to reach the API), falling back to `http://localhost:${PORT}` when unset. `info.version` was frozen at `"2.0.0"` and now reports the real package version. Four `/admin/categories` and `/admin/tags` paths documenting eight operations that exist nowhere in the codebase are removed, along with the five Zod schemas that only fed them. A new contract test boots the app and checks every documented path+method against Hono's live route table, so a spec entry that names a route the API does not serve now fails CI instead of shipping.
+
 ## 0.16.0
 
 ### Minor Changes

ornn-api/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ornn-api",
-  "version": "0.16.0",
+  "version": "0.16.1",
   "private": true,
   "type": "module",
   "scripts": {

ornn-web/CHANGELOG.md

@@ -1,5 +1,7 @@
 # ornn-web
 
+## 0.16.1
+
 ## 0.16.0
 
 ### Minor Changes

ornn-web/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ornn-web",
-  "version": "0.16.0",
+  "version": "0.16.1",
   "private": true,
   "type": "module",
   "scripts": {