@akanjs/cli 3.0.0-alpha.69 → 3.0.0-alpha.70

package/.build-stamp

@@ -1 +1 @@
-f854deee45ba7fb5cde828e62164657386dfc13e55f0b7da760161ad709daa32
+a28e1153bab4e1e1e981a92cbd3a49ffbf5137997da979da9cf3ad9f5d1f54ba

package/guidelines/conventions/conventions.instruction.md

@@ -707,6 +707,9 @@ while guaranteeing that every endpoint added later is invisible to agents until
 - Settings live in the app's `lib/option.ts` — `option.setMcp({ enabled, readOnly, path, version, instructions,
   allowedOrigins, pageSize, language, auth })`, **not `main.ts`**. Every lib's option is read in mount order with
   the app's last, and each field has an `AKAN_MCP_*` env spelling the option overrides.
+- **RFC 9728 metadata is served only once an authorization server is named.** Advertising `bearer_methods_supported`
+  without one makes Cursor (and similar clients) force OAuth. Set `AKAN_MCP_AUTH_SERVERS` when the surface is an
+  OAuth resource; otherwise the well-known document is absent.
 - **The refusals are fail-closed**: a declared `mcp: false`, an endpoint with no `guards`, a mutation with no real guard (`[Public]` is
   having none), `pubsub` and `message`, an `Any` or `Upload` return, a file upload, a required `Any` argument, and
   the generated `light<Model>` read — it is `<Model>` in a smaller shape, so one read never costs two entries of

package/guidelines/mcpRule/mcpRule.instruction.md

@@ -151,11 +151,14 @@ export class TaskEndpoint extends endpoint(srv.task, ({ mutation, prompt }) => (
   and are not configurable. Clients are told to distrust hints; they are never a gate.
 - **`AKAN_MCP_READONLY=true` is the read-only-deployment valve, not the exposure switch.** It drops every mutation
   whatever it declared, and reports each one in the boot log like any other refusal.
-- OAuth resource metadata is published at `/.well-known/oauth-protected-resource` (and at that path plus the mount
-  path, the spelling most clients try first). `AKAN_MCP_AUTH_SERVERS`, `AKAN_MCP_SCOPES`, and `AKAN_MCP_RESOURCE`
-  configure it; `insufficient_scope` is enforced only once `AKAN_MCP_SCOPES` is set. A token carrying no `aud` at
-  all is refused once `AKAN_MCP_AUTH_SERVERS` names an issuer — that issuer mints tokens for its other resources
-  too — and accepted while none is named, because a first-party Akan token is bound by app and environment.
+- **RFC 9728 metadata is published only once `AKAN_MCP_AUTH_SERVERS` names an issuer.** An unprotected resource
+  that still advertises `bearer_methods_supported` is treated by Cursor (and similar clients) as an OAuth
+  mandate, so the well-known document is absent until there is somewhere to obtain a token. When it is served,
+  it lives at `/.well-known/oauth-protected-resource` (and at that path plus the mount path, the spelling most
+  clients try first). `AKAN_MCP_SCOPES` and `AKAN_MCP_RESOURCE` configure the document when it exists;
+  `insufficient_scope` is enforced only once `AKAN_MCP_SCOPES` is set. A token carrying no `aud` at all is
+  refused once an issuer is named — that issuer mints tokens for its other resources too — and accepted while
+  none is named, because a first-party Akan token is bound by app and environment.
 - **The boot log names every published entry with no dictionary `.desc()`.** An agent picks a tool by its
   description, so a missing one is a broken tool. What the framework generates has no text of its own and borrows
   the model's: the generated list reads the `.of()` label, and the base CRUD tools append the model's `.desc()` to

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@akanjs/cli",
-  "version": "3.0.0-alpha.69",
+  "version": "3.0.0-alpha.70",
   "sourceType": "module",
   "type": "module",
   "publishConfig": {
@@ -34,7 +34,7 @@
     "@langchain/openai": "^1.4.6",
     "@tailwindcss/node": "^4.3.0",
     "@trapezedev/project": "^7.1.4",
-    "akanjs": "3.0.0-alpha.69",
+    "akanjs": "3.0.0-alpha.70",
     "chalk": "^5.6.2",
     "commander": "^14.0.3",
     "dayjs": "^1.11.20",