@mesh-tech/mesh-cli 0.24.0 → 0.24.1

package/dist/build-info.json

@@ -1,4 +1,4 @@
 {
-  "commit": "0c1c4206e",
-  "builtAt": "2026-09-15T18:29:19.953Z"
+  "commit": "8aff693d3",
+  "builtAt": "2026-09-15T19:25:45.158Z"
 }

package/dist/src/commands/app-check.js

@@ -553,7 +553,7 @@ function docsAudienceUngrantable(text, decl, args, docs, httpText) {
     const docsAuth = objectLiteralOf(docs.get("auth"), text);
     const clientExpr = (docsAuth ? topLevelProperties(docsAuth).get("clientId") : undefined) ??
         (httpText ? topLevelProperties(objectLiteralOf(topLevelProperties(httpText).get("auth"), text) ?? "{}").get("clientId") : undefined);
-    const clientRoot = clientExpr ? /^([A-Za-z_$][\w$]*)\.applications\./.exec(clientExpr.trim())?.[1] : undefined;
+    const clientRoot = clientExpr ? /^([A-Za-z_$][\w$]*)\.(?:clientIds|applications)\./.exec(clientExpr.trim())?.[1] : undefined;
     const identity = (clientRoot ? identities.find((id) => id.binding === clientRoot) : undefined) ??
         (identities.length === 1 ? identities[0] : undefined);
     if (!identity)

package/fragments/base/index.ts.hbs

@@ -102,7 +102,9 @@ const worker = new mesh.apps.TemporalWorker("worker", {
 
 // =============================================================================
 // Docs — the API's reference site, built by the platform from the spec and
-// the guides in docs/pages/. A docs site has no hostname of its own: here it
+// the guides in docs/pages/ (this README is its landing page — `landingPage`
+// names another file, or `false` — and every guide is listed after it, in
+// path order). A docs site has no hostname of its own: here it
 // is reachable under `mesh dev`, and it is published by being read inside
 // the Hub. To publish it, declare the API as a `mesh.apps.AppApiSurface`
 // whose `docs` block builds this same site (`docs: { spec, pages }`) — the

package/fragments/service/docs/pages/getting-started.md.hbs

@@ -5,8 +5,10 @@ title: Getting started
 # Getting started with the {{titleCase name}} API
 
 Guides for this API live in `docs/pages/` as Markdown and are published next to
-the reference generated from `api/openapi.json`. Add a page per topic; the
-platform builds the site on every deploy. Keep pages as `.md`, not `.mdx`: a
+the reference generated from `api/openapi.json`. Add a page per topic — each
+is listed in the sidebar after the README landing page, in path order, under
+the `title` in its front matter; the platform builds the site on every deploy.
+Keep pages as `.md`, not `.mdx`: a
 site an API surface declares is also read inside the Hub (the docs door),
 which serves data, never code — an `.mdx` page fails that deploy.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mesh-tech/mesh-cli",
-  "version": "0.24.0",
+  "version": "0.24.1",
   "description": "CLI for Mesh platform development utilities",
   "type": "module",
   "license": "UNLICENSED",
@@ -42,7 +42,7 @@
   },
   "devDependencies": {
     "@mesh-tech/agent-contracts": "0.2.0",
-    "@mesh-tech/tsconfig": "2.12.0",
+    "@mesh-tech/tsconfig": "2.13.0",
     "@mesh-tech/workflow-viz": "0.3.0",
     "@tanstack/intent": "^0.3.6",
     "@types/node": "^20.0.0",