@avocadostudio-ai/orchestrator-core 0.10.0 → 0.11.1

package/dist/handler/create-orchestrator.js

@@ -556,6 +556,27 @@ export function createOrchestrator(config = {}) {
             }, { cors });
         }
         if (request.method === "POST" && path === "/auth/verify") {
+            /*
+             * A closed mount must not hand out a token.
+             *
+             * `closed` is production with no credential configured, and every route
+             * behind this one answers 401. This one answered `{"ok":true,
+             * "accessToken":"..."}` — to any body, including `{}` and
+             * `{"password":"literally-anything"}`. The token opened nothing: all
+             * three transports (`Authorization: Bearer`, `x-access-token`,
+             * `?accessToken=`) were checked and every one still 401s.
+             *
+             * So it was never a hole, which is exactly what made it expensive. It is
+             * a login that says yes while the system is shut, and the operator who
+             * receives a token and then 401s everywhere has no way to connect the
+             * two. `/auth/status` one route over already reports the truth; this now
+             * reports the same truth, in the same words, with a status code that
+             * says "the server, not your password".
+             */
+            const verifyAuth = resolveAuth(config.auth);
+            if (verifyAuth.mode === "closed") {
+                return jsonResponse({ ok: false, error: "unavailable", reason: CLOSED_HINT }, { status: 503, cors });
+            }
             if (!isAccessGateEnabled()) {
                 // Open by choice, or gated by something other than a password. Hand back
                 // a token anyway so the client's code path is identical either way; if a
@@ -967,10 +988,19 @@ export function createOrchestrator(config = {}) {
                 }
             };
             if (!runtime.adapter?.onPublish) {
+                /*
+                 * Two audiences, and they had been given the same sentence. `reason` is
+                 * for whatever called the API; `message` is what the editor prints as
+                 * the summary under a green tick, so a first-run user read the words
+                 * "adapter has no onPublish; publish is a no-op" as the report on the
+                 * button they had just pressed.
+                 */
                 const reason = "adapter has no onPublish; publish is a no-op";
+                const message = "Nothing was written — this site's content adapter is read-only. Your edits are " +
+                    "still here as a draft; to publish them, give the adapter somewhere to write.";
                 record(true, "Nothing written — the adapter has no onPublish");
                 return jsonResponse({
-                    ...publishEnvelope(body.session, slugs, reason),
+                    ...publishEnvelope(body.session, slugs, message),
                     ok: true,
                     written: false,
                     count: pages.length,

package/dist/publish/targets/site-contract.js

@@ -71,7 +71,21 @@ export class SiteContractPublishTarget {
                     status: "failed",
                     session,
                     slugs,
-                    reason: siteResult.error ?? "site publish failed"
+                    /*
+                     * `reason` first, and it is not a nicety.
+                     *
+                     * Every refusal this route can produce puts the machine-readable
+                     * verdict in `error` and the sentence a human can act on in
+                     * `reason` — "refused" / "this publish would remove every page…",
+                     * "unauthorized" / "set PUBLISH_TOKEN…". Reading only `error` threw
+                     * the second half away, so the editor showed a user the word
+                     * "unauthorized" and nothing about the variable that fixes it, and
+                     * would have shown "refused" with nothing about `allowDelete`.
+                     *
+                     * A guard whose explanation never reaches the person who tripped it
+                     * is the same failure as the one `CLOSED_HINT` exists to prevent.
+                     */
+                    reason: siteResult.reason ?? siteResult.error ?? "site publish failed"
                 }
             };
         }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@avocadostudio-ai/orchestrator-core",
-  "version": "0.10.0",
+  "version": "0.11.1",
   "type": "module",
   "exports": {
     "./package.json": "./package.json",
@@ -22,8 +22,8 @@
     "openai": "^4.87.1",
     "sharp": "^0.35.4",
     "zod": "^4.3.6",
-    "@avocadostudio-ai/shared": "^0.10.0",
-    "@avocadostudio-ai/migration-sdk": "^0.10.0"
+    "@avocadostudio-ai/migration-sdk": "^0.11.1",
+    "@avocadostudio-ai/shared": "^0.11.1"
   },
   "devDependencies": {
     "@anthropic-ai/claude-agent-sdk": "^0.3.220",