@akanjs/cli 3.0.0-alpha.103 → 3.0.0-alpha.104

package/.build-stamp

@@ -1 +1 @@
-708d95c2692df8b7a0bdb905802d48d38352e0305215030af6c3d6aa468a9460
+dd9f0e268907504c3c7608ed05e6f95752b6eb2dbfa2f31b3c69c451ff7806d9

package/{abstractCompactor-byytxs22.js → abstractCompactor-mjh5ppsq.js}

@@ -2,7 +2,7 @@
 import"./index-q0y2jq9j.js";
 import {
   AiSession
-} from "./index-c69j78kk.js";
+} from "./index-kn1h7p1x.js";
 import {
   AbstractDoc
 } from "./index-meh558jy.js";

package/{agent.command-v1a4746v.js → agent.command-d2gfxfck.js}

@@ -2,17 +2,17 @@
 import {
   Workspace,
   command
-} from "./index-znynzt5w.js";
+} from "./index-mak3cd28.js";
 import"./index-q0y2jq9j.js";
-import"./index-qsq3q8fy.js";
+import"./index-2tv3fdx4.js";
 import"./index-6wwzs1bc.js";
 import"./index-by5gpp8x.js";
-import"./index-fc1bh0a7.js";
-import"./index-gtmz74tj.js";
+import"./index-gyd220p2.js";
+import"./index-ktb5njgy.js";
 import"./index-h7yw2z9n.js";
 import {
   AgentScript
-} from "./index-29sxqfaw.js";
+} from "./index-ne2qy0nk.js";
 
 // pkgs/@akanjs/cli/agent/agent.command.ts
 class AgentCommand extends command("agent", [AgentScript], ({ public: target }) => ({

package/{application.command-fzdcnzhg.js → application.command-xgphqs7k.js}

@@ -6,19 +6,19 @@ import {
   Exec,
   Workspace,
   command
-} from "./index-znynzt5w.js";
+} from "./index-mak3cd28.js";
 import"./index-q0y2jq9j.js";
-import"./index-qsq3q8fy.js";
+import"./index-2tv3fdx4.js";
 import"./index-6wwzs1bc.js";
 import {
   ApplicationScript
-} from "./index-zz5jyd94.js";
-import"./index-gq44bqjt.js";
+} from "./index-yecdrt9a.js";
+import"./index-259dsnz3.js";
 import"./index-hwkygn9s.js";
 import {
   AbstractDoc
 } from "./index-meh558jy.js";
-import"./index-5svjba73.js";
+import"./index-j9yhg404.js";
 import {
   getMobileTargetChoices
 } from "./index-47pj3aee.js";

package/{applicationBuildRunner-s4gsk728.js → applicationBuildRunner-3d5q1yn7.js}

@@ -1,14 +1,14 @@
 // @bun
 import {
   Spinner
-} from "./index-qsq3q8fy.js";
+} from "./index-2tv3fdx4.js";
 import {
   AllRoutesBuilder,
   CsrArtifactBuilder,
   FontPruner,
   precompressArtifacts,
   SsrBaseArtifactBuilder
-} from "./index-p5neav9b.js";
+} from "./index-0vh9rgxz.js";
 import"./index-w8kmx1b6.js";
 import"./index-q0y2jq9j.js";
 import"./index-hwkygn9s.js";

package/{applicationReleasePackager-28v9vbzk.js → applicationReleasePackager-4yasxwv9.js}

@@ -4,7 +4,7 @@ import {
 } from "./index-q0y2jq9j.js";
 import {
   Spinner
-} from "./index-qsq3q8fy.js";
+} from "./index-2tv3fdx4.js";
 
 // pkgs/@akanjs/devkit/applicationReleasePackager.ts
 import { cp, mkdir, rm } from "fs/promises";

package/buildBatch.proc.js

@@ -2,7 +2,7 @@
 import {
   WorkspaceExecutor,
   AppExecutor
-} from "./index-qsq3q8fy.js";
+} from "./index-2tv3fdx4.js";
 import"./index-q0y2jq9j.js";
 import"./index-6wwzs1bc.js";
 import {
@@ -11,7 +11,7 @@ import {
   CsrArtifactBuilder,
   FontOptimizer,
   SsrBaseArtifactBuilder
-} from "./index-p5neav9b.js";
+} from "./index-0vh9rgxz.js";
 import"./index-w8kmx1b6.js";
 import"./index-hwkygn9s.js";
 import"./index-n68jx79w.js";

package/{capacitorApp-8d6d4zkm.js → capacitorApp-36rbr858.js}

@@ -2,8 +2,8 @@
 import {
   isPlaceholderAppId2,
   CapacitorApp2
-} from "./index-1yxtbmbj.js";
-import"./index-qsq3q8fy.js";
+} from "./index-wt7qrtd4.js";
+import"./index-2tv3fdx4.js";
 import"./index-6wwzs1bc.js";
 import"./index-q0y2jq9j.js";
 export {

package/{cloud.command-wygy2z05.js → cloud.command-abgkk73f.js}

@@ -2,23 +2,23 @@
 import"./index-q0y2jq9j.js";
 import {
   GlobalConfig
-} from "./index-c69j78kk.js";
+} from "./index-kn1h7p1x.js";
 import {
   Workspace,
   command
-} from "./index-znynzt5w.js";
-import"./index-qsq3q8fy.js";
+} from "./index-mak3cd28.js";
+import"./index-2tv3fdx4.js";
 import"./index-6wwzs1bc.js";
-import"./index-zz5jyd94.js";
-import"./index-gq44bqjt.js";
+import"./index-yecdrt9a.js";
+import"./index-259dsnz3.js";
 import"./index-hwkygn9s.js";
 import"./index-kcxmv48c.js";
-import"./index-7d6vny25.js";
-import"./index-zxgr3s8s.js";
+import"./index-ws5e0j51.js";
+import"./index-yw4xj7pa.js";
 import {
   CloudScript
-} from "./index-yks023mb.js";
-import"./index-5svjba73.js";
+} from "./index-4c9ykbfq.js";
+import"./index-j9yhg404.js";
 
 // pkgs/@akanjs/cli/cloud/cloud.command.ts
 var localRegistryUrl = () => process.env.AKAN_NPM_REGISTRY ?? "http://127.0.0.1:4873";

package/{context.command-4vdt1aqq.js → context.command-ez8a0zyz.js}

@@ -2,25 +2,25 @@
 import {
   Workspace,
   command
-} from "./index-znynzt5w.js";
+} from "./index-mak3cd28.js";
 import"./index-q0y2jq9j.js";
-import"./index-qsq3q8fy.js";
+import"./index-2tv3fdx4.js";
 import"./index-6wwzs1bc.js";
 import"./index-by5gpp8x.js";
-import"./index-fc1bh0a7.js";
-import"./index-gtmz74tj.js";
+import"./index-gyd220p2.js";
+import"./index-ktb5njgy.js";
 import {
   ContextScript
-} from "./index-yza7zkpt.js";
-import"./index-1yxtbmbj.js";
+} from "./index-600zhnve.js";
+import"./index-wt7qrtd4.js";
 import"./index-h7yw2z9n.js";
-import"./index-0amdxycf.js";
-import"./index-srdssqj7.js";
-import"./index-c69j78kk.js";
-import"./index-zmjppp25.js";
-import"./index-hyywke0f.js";
-import"./index-qkk27bk6.js";
-import"./index-8p8p0cf8.js";
+import"./index-fz5q3gd7.js";
+import"./index-7737gxcp.js";
+import"./index-kn1h7p1x.js";
+import"./index-8pm30m73.js";
+import"./index-pnqbkf5p.js";
+import"./index-4edzf1gr.js";
+import"./index-rwg2aa4f.js";
 
 // pkgs/@akanjs/cli/context/context.command.ts
 class ContextCommand extends command("context", [ContextScript], ({ public: target }) => ({

package/{devTui-qnf1txdz.js → devTui-70cjjtaw.js}

@@ -4,7 +4,7 @@ import {
   plainTextOf,
   HOST_SOURCE,
   DevLogBuffer
-} from "./index-zz5jyd94.js";
+} from "./index-yecdrt9a.js";
 
 // pkgs/@akanjs/cli/application/devTui.tsx
 import { render } from "ink";

package/{devTuiView-yzct2cq6.js → devTuiView-71wnkjft.js}

@@ -1,7 +1,7 @@
 // @bun
 // pkgs/@akanjs/cli/application/devTuiView.ts
 var createDevTuiView = async (supervisor) => {
-  const { DevTui } = await import("./devTui-qnf1txdz.js");
+  const { DevTui } = await import("./devTui-70cjjtaw.js");
   return new DevTui(supervisor);
 };
 export {

package/{guideline.command-p92dq6ts.js → guideline.command-xmqwx8zm.js}

@@ -4,11 +4,11 @@ import {
   runner,
   script,
   command
-} from "./index-znynzt5w.js";
+} from "./index-mak3cd28.js";
 import {
   FileSys
 } from "./index-q0y2jq9j.js";
-import"./index-qsq3q8fy.js";
+import"./index-2tv3fdx4.js";
 import {
   getDirname2
 } from "./index-6wwzs1bc.js";
@@ -17,7 +17,7 @@ import {
 } from "./index-h7yw2z9n.js";
 import {
   AiSession
-} from "./index-c69j78kk.js";
+} from "./index-kn1h7p1x.js";
 
 // pkgs/@akanjs/cli/guideline/guideline.script.ts
 import { Logger } from "akanjs/common";
@@ -135,9 +135,11 @@ Request: ${updateRequest}
   async requestCreateDocumentPage(page) {
     const writePath = this.#resolveDocsPagePath(page);
     if (!await this.workspace.exists(writePath))
-      await this.workspace.writeFile(writePath, `export default function Page() {
+      await this.workspace.writeFile(writePath, `import { page } from "akanjs/client";
+
+export default page().render(() => {
   return <div>No Content</div>;
-}
+});
 `);
     const instruction = await Prompter.getInstruction(this.name);
     const pageContent = await this.workspace.getLocalFile(writePath);
@@ -178,9 +180,11 @@ Please return only the file result in the following format for easy parsing.
   async requestUpdateDocumentPage(page, updateRequest) {
     const writePath = this.#resolveDocsPagePath(page);
     if (!await this.workspace.exists(writePath))
-      await this.workspace.writeFile(writePath, `export default function Page() {
+      await this.workspace.writeFile(writePath, `import { page } from "akanjs/client";
+
+export default page().render(() => {
   return <div>No Content</div>;
-}
+});
 `);
     const instruction = await Prompter.getInstruction(this.name);
     const pageContent = await this.workspace.getLocalFile(writePath);

package/guidelines/agentRule/agentRule.instruction.md

@@ -93,8 +93,7 @@ apps and libs never import it directly (`no-import-external-library`) — everyt
   model never saw is one it answers about from the filename. An adaptor declares `accepts: { image, document }` and
   `AgentService.readable` degrades the rest, so a text-only provider needs no attachment code at all — DeepSeek
   declares none, which is why an image against the default provider is refused out loud while an extracted PDF
-  works, `text` being readable by every model there is. **A `prompt()`'s `Msg.image` is the same wire shape** and
-  reaches the chat as an attachment rather than the literal `[image]` it used to become. Persisting keeps each
+  works, `text` being readable by every model there is. Persisting keeps each
   attachment's name and drops its content: web storage is a few megabytes, one screenshot fills a chunk of it, and
   a save that fails is silent — so keeping the bytes would quietly stop keeping the transcript.
   **The ceilings are the message's, not the file's**: 4 MB per file, 8 MB and five files per message, and the same
@@ -372,18 +371,11 @@ apps and libs never import it directly (`no-import-external-library`) — everyt
   useless to a model — that is cheaper than every tool learning to avoid it.
 
 ## Slash Commands And The Transcript
-- **`prompt()` endpoints double as the chat's slash commands.** There is no listing endpoint — the client reads
-  its own serialized signals — so a prompt's dictionary `.desc()` is what the menu shows, and its guards are
-  enforced by the prompt's own GET at call time. Arguments are positional and whitespace-separated, and quoting
-  is how a sentence stays one of them (`/reviewTask t1 "look at the totals"`) — a prompt taking a single `String`
-  is the common case, and an unquoted sentence would fill its second parameter with the second word.
-- **The chat answers six slash commands of its own**, listed in the same `/` menu ahead of the prompts:
-  `/new` (`/clear`), `/retry`, `/compact`, `/copy`, `/help` and `/tools`. An app writes none of them and cannot add
-  one — the extension point for a product's own command is a `prompt()` endpoint, which is guarded and server-side.
-  **A built-in wins a name collision with a prompt of the same name**, the mirror image of the tool rule: a
-  component's `st.tool` shadows a built-in it means to replace, but no library's prompt may take `/new` away from
-  the user who typed it — so a shadowed prompt is dropped from the menu rather than listed twice. `/new` and
-  `/copy` are also dispatched *before* the is-a-turn-running check **and before the question card takes the
+- **The `/` menu is the chat's own.** An app's prompts are `page().prompt()` declarations served over MCP to
+  external agents; a browser chat lists none of them, so the menu holds the six built-in commands and nothing else.
+- **The chat answers six slash commands of its own**: `/new` (`/clear`), `/retry`, `/compact`, `/copy`, `/help` and
+  `/tools`. An app writes none of them and cannot add one — a workflow a person invokes by name belongs to MCP, as
+  a `page().prompt()`, where it is guarded by the page it opens. `/new` and `/copy` are dispatched *before* the is-a-turn-running check **and before the question card takes the
   composer**, because mid-turn is exactly when they are reached for and a question the agent asked is the middle
   of a turn like any other — answered as text, `/new` would have reached the model as the user's decision.
   `/new` therefore aborts the turn it is clearing and waits for it to wind down, since the loop clears its own

package/guidelines/conventions/conventions.instruction.md

@@ -651,7 +651,7 @@ it.
   (`@libs/shared/srvkit`). Never sniff `aud` through a cast.
 - **The refusals are fail-closed**: a declared `mcp: false`, an endpoint with no `guards`, a mutation with no real
   guard, `pubsub` and `message`, an `Any` or `Upload` return, a file upload, a required `Any` argument, and the
-  generated `light<Model>` read. A `prompt` also refuses a list argument and any `Any` argument. **Every refusal
+  generated `light<Model>` read. An `enumOf` argument is checked against its values on every path. **Every refusal
   is named in the boot log**, along with every published entry missing a dictionary `.desc()` — an agent picks a
   tool by its description.
 - A refused endpoint answers the *same* "unknown tool" as one that does not exist, and a guard's refusal is
@@ -659,10 +659,14 @@ it.
 - **A `field.visual` field is stripped from every MCP result** and from the readable schema so the two agree.
 - **A structured result ships twice by default** — as `structuredContent` and as the same JSON in the text block.
   `option.setMcp({ legacyTextBlock: false })` leaves a pointer there instead.
-- **`prompt()`** is invoked by the *user* as a slash command, never chosen by the model. `exec` returns
-  `PromptMessage[]` built with `Msg.user` / `Msg.assistant` / `Msg.resource` / `Msg.image`; an embedded payload is
-  masked by the model you name, and one whose `hidden`/`secret` fields are populated with no model named is
-  refused. It is also mounted as a plain HTTP `GET` whether or not MCP is enabled, so guard it like any other read.
+- **A prompt is a screen: `page().prompt(name, description)`.** There is no `prompt()` on `endpoint()`.
+  `prompts/get` runs the page's body in the RSC worker under the caller's token — nothing is rendered — and answers
+  the description, one `resource` per `fetch.*` the page made (masked by the endpoint's return model, addressed by
+  its `akan://` uri, one document once whatever shapes read it) and the published tools of the modules it fetched
+  from, minus what is already attached; lists — only lists — are cut to `promptBudget`. A guard refusing a query
+  inside the body reads as the screen refusing the account, the same way a redirect does. A
+  required argument left out answers a pointer to the `<model>List…` tool, never a guess. The description is the
+  only instruction, in English — `<Agent.Guide>` never reaches MCP, and the in-page chat lists no page prompts.
 
 Full contract — configuration, wire behaviour, resource URIs, OAuth metadata, protocol revisions, and
 `McpProgress.report`: `get_guideline` with `mcpRule`, or `akan guideline show mcpRule`.
@@ -794,39 +798,50 @@ shape, so `cascade` never means "related" — it means one of exactly these:
 - Reserved `_*.tsx` route filenames are limited to `_index.tsx`, `_layout.tsx`, and `_overrides.tsx`; do not add files like `_Component.tsx` or `_helper.tsx`.
 - Page filenames must not start with an uppercase letter. Move helper components like `Component.tsx` to app `ui`, `common`, or `lib` instead.
 - Dynamic segments use `[id]`; route groups use directories like `(user)`, `(public)`, `(tab)`, or `(detail)`.
-- Page modules should usually export `default`, `pageConfig`, `head`, `generateHead`, or `Loading`.
+- **A route file exports one thing**: `export default page()…render(…)` for a page, `layout()…render(…)` for a
+  `_layout.tsx`, `rootLayout()…render(…)` for the app's (or a basePath's) root `_layout.tsx`. Every route setting
+  is a stage of the chain — `.param()`, `.search()`, `.config()`, `.head()` / `.metadata()`, `.loading()`;
+  `.notFound()` / `.error()` on a layout; `.fonts()` / `.theme()` / `.manifest()` / `.reconnect()` / `.wsConnect()`
+  / `.layoutStyle()` / `.gaTrackingId()` on the root layout; `.prompt()` on a page. A named export beside the chain,
+  or `page()` in a `_layout.tsx`, fails the build.
+- **A page names every `[x]` segment of its path with `.param("x", Type)`** and reads a query key only through
+  `.search("k", Type)`. Values arrive typed — `ID`/`String` → string, `Int`/`Float` → number, `Boolean`, `Date` →
+  Dayjs, an `enumOf` class → its union, `[T]` → array — a path value the type refuses answers not-found, and a
+  search value that fails is dropped. A layout may declare a subset. Names are string literals: `akan sync` reads
+  them off the source and refuses a `[projectId]` folder whose page declares no `.param("projectId")`. `lang` is
+  never declared: every route sits under `/:lang`, and the locale segment reaches every stage as `lang`.
 - `_overrides.tsx` is a logic-free UI-override manifest: imports plus a single `export default override({ Slot: AppComponent })` (from `akanjs/ui`), no `"use client"`. It re-skins framework `akanjs/ui` components for its route subtree; nested manifests merge over ancestors slot-by-slot (closest wins). See the UI Customization reference for the slot list.
-- Prefer `export default function Page` or `export default async function Page` for page components.
+- The legacy shape — `export default async function Page` beside `pageConfig` / `head` / `Loading` exports — still
+  loads and logs one deprecation warning per file at boot. Migrate with the `workspaceRecipes` recipe "Migrating
+  `page/` to the route chain"; new files are never written in it.
 - `libs/<lib>/page` follows the same rules and ships routes to apps that opt in with `syncPageLibs` in `akan.config.ts`: `true` takes every lib dep that has a `page` folder, an array takes the libs listed, `false` (the default) syncs nothing.
 - `akan sync` links those routes into `apps/<app>/page/(libs)/(<lib>)` — once per basePath when the app declares subRoutes. The folder is generated and gitignored; edit the lib source, never the link.
 - Both path segments are route groups, so a lib route mounts at its own path (`libs/<lib>/page/login/_index.tsx` serves `/login`). Two synced routes that resolve to the same pattern are a sync-time error.
-- `export const pageConfig = { devOnly: true }` keeps a route out of `akan build` while it keeps serving under `akan start` and keeps being typechecked. On a `_layout.tsx` it excludes every route under that directory too. Write it as a literal `true`/`false` — the build reads it off the source without evaluating the module.
+- `.config({ devOnly: true })` keeps a route out of `akan build` while it keeps serving under `akan start` and keeps being typechecked. On a `_layout.tsx` it excludes every route under that directory too. Write it as a literal `true`/`false` — the build reads it off the source without evaluating the module.
 - Before changing route behavior, check `pkgs/akanjs/server/routeTreeBuilder.ts` and nearby routes for the expected pattern.
 
 ### Page Body Shape
 
 ```tsx
-interface PageProps {
-  params: { orgId: string };
-}
-
-export default async function Page({ params }: PageProps) {
-  const { l } = usePage();
-  getSelf({ unauthorize: "/signin" });
-  const { orgId } = params;
-  const [{ org }, { taskInitInOrg }] = await Promise.all([fetch.viewOrg(orgId), fetch.initTaskInOrg(orgId)]);
-  return <Task.Zone.Card init={taskInitInOrg} prefix={`/org/${orgId}`} />;
-}
-
-export const pageConfig = { transition: "stack" } satisfies PageConfig;
+export default page()
+  .param("orgId", ID)
+  .config({ transition: "stack" })
+  .render(async ({ orgId }) => {
+    const { l } = usePage();
+    getSelf({ unauthorize: "/signin" });
+    const [{ org }, { taskInitInOrg }] = await Promise.all([fetch.viewOrg(orgId), fetch.initTaskInOrg(orgId)]);
+    return <Task.Zone.Card init={taskInitInOrg} prefix={`/org/${orgId}`} />;
+  });
 ```
 
-- There is no `loader=` / `render=` page prop. Pages are `export default async function Page`.
-- Declare `interface PageProps { params: {...}; searchParams?: {...} }` immediately above the default export.
-- Body order: `usePage()`, auth, destructure params, fetch, return.
+- There is no `loader=` / `render=` page prop and no `PageProps` interface: the chain declares the arguments and
+  `.render()` receives them flat, typed, with `lang` on every route and `children` added for a layout.
+- Body order inside `.render()`: `usePage()`, auth, fetch, return.
 - Run independent fetches through `Promise.all`, even when there is only one.
 - Gate auth at `_layout.tsx`; repeating `getSelf({ unauthorize: "/signin" })` in the page is fine and common.
-- Keep `async` even when nothing is awaited — it marks a real server page.
+- `async` on the render callback only when the body awaits; the callback is not a React component, so it takes no
+  name and no return type.
+- Publish a screen to agents with `.prompt(name, description)` — see MCP Exposure.
 - No `useState`, no `useEffect`, and no comments in page files.
 
 ## Akan Sync Conventions (`apps/**`, `libs/**`)

package/guidelines/mcpRule/mcpRule.instruction.md

@@ -73,7 +73,7 @@ export const option = new AkanOption<ModulesOptions>().setMcp({
 ```
 
 ```typescript
-// <model>.signal.ts — every one of these is an MCP tool or prompt, with no `mcp:` option anywhere
+// <model>.signal.ts — every one of these is an MCP tool, with no `mcp:` option anywhere
 export class TaskSlice extends slice(
   srv.task,
   { guards: { root: Admin, get: SignedIn, cru: SignedIn } },
@@ -86,21 +86,26 @@ export class TaskSlice extends slice(
   }),
 ) {}
 
-export class TaskEndpoint extends endpoint(srv.task, ({ mutation, prompt }) => ({
+export class TaskEndpoint extends endpoint(srv.task, ({ mutation }) => ({
   startTask: mutation(cnst.Task, { guards: [SignedIn] })
     .param("taskId", ID)
     .exec(async function (taskId) {
       return await this.taskService.startTask(taskId);
     }),
-  reviewTask: prompt({ guards: [SignedIn] })
-    .param("taskId", ID)
-    .exec(async function (taskId) {
-      const task = await this.taskService.getTask(taskId);
-      return [Msg.user(`Review this task and suggest next steps.`), Msg.resource(`akan://task/${taskId}`, task)];
-    }),
 })) {}
 ```
 
+```tsx
+// page/task/[taskId]/_index.tsx — the screen, published to agents as the prompt `reviewTask`
+export default page()
+  .param("taskId", ID, { desc: "The task to review." })
+  .prompt("reviewTask", "Review this task and suggest next steps.")
+  .render(async ({ taskId }) => {
+    const { taskView } = await fetch.viewTask(taskId);
+    return <Task.Zone.View view={taskView} />;
+  });
+```
+
 ## Refusals And Wire Behaviour
 - **`mcp: false` is read first**, because it is the one answer nobody had to derive — somebody stated it. Its
   reason says "HTTP still serves it", because that is the sentence that stops the next reader treating it as a lock.
@@ -111,16 +116,13 @@ export class TaskEndpoint extends endpoint(srv.task, ({ mutation, prompt }) => (
   **`light<Model>` read** — it returns the same document as `<Model>` under the same guards, in a shape trimmed
   for a page's payload, so publishing both put two entries per model in a listing an agent pays for every turn
   and gave it nothing but the word "light" to choose between them.
-  A `prompt` refuses two more, because its `arguments` is one string per name with no schema beside it: a **list
-  argument**, which could never carry a second value, and **any `Any` argument** — a tool leaves that out of its
-  schema, and a prompt has no schema to leave it out of.
 - **The boot log sizes the catalogue and says which signals it went to** — `MCP catalogue: tools=48 … · listing
   214KB` and `MCP catalogue cost: user 27/71KB · file 6/22KB · …`, heaviest first. Read it before narrowing
   anything: the number is nobody's intuition, because MCP has no shared component section and forbids a `$ref`
   across entries, so **every entry inlines the full schema of every model it mentions** and a listing is re-sent
   whole to every agent that connects, before its first turn. Past 100KB it says so as a `warn`.
-- **Every refusal is named in the boot log**: one `warn` per endpoint plus a `MCP catalogue: tools=… prompts=…`
-  count. Read that line first when a tool you expected is missing — and it is the *only* place the answer exists,
+- **Every refusal is named in the boot log**: one `warn` per endpoint plus a `MCP catalogue: tools=…
+  resourceTemplates=…` count, and a `MCP page prompts: N (…)` line once the RSC worker has listed the pages. Read that line first when a tool you expected is missing — and it is the *only* place the answer exists,
   because there is no absent opt-in to notice. The API explorer badges the same rule per endpoint (`MCP` /
   `MCP refused`), from the same shared implementation the catalogue runs.
 - **An `Any` argument is left out of the published schema** rather than described as `{}` — it tells a model
@@ -146,7 +148,8 @@ export class TaskEndpoint extends endpoint(srv.task, ({ mutation, prompt }) => (
   doubling of what every model-returning tool costs a model. `option.setMcp({ legacyTextBlock: false })` — or
   `AKAN_MCP_LEGACY_TEXT=false` — leaves a one-line pointer in the text block instead, for a deployment whose
   clients read the structured half. A scalar return is unaffected: it has no structured half to point at, so it
-  ships as the value itself either way.
+  ships as the value itself either way. `resources/read` is unaffected too: `ReadResourceResult` has no
+  `structuredContent`, so a resource's text is its only channel and always carries the serialized value.
 - **A request schema asks for a relation's id, and a response schema names a nested model.** `serialize` sends a
   relation field as its id and the server never converts an object back, so publishing the related model's shape
   asked an agent for what the document layer cannot take. On the response side every entry inlines the transitive
@@ -213,9 +216,9 @@ export class TaskEndpoint extends endpoint(srv.task, ({ mutation, prompt }) => (
   which is in force, and warns when it is off.
 - **A `resources/read` uri that does not decode** — a stray `%` — is `Unknown resource`, not a server failure.
 - **A caller's own mistake is reported as one** and never as a server failure: an argument that is missing,
-  unparseable or **undeclared** comes back as `isError` naming it — `additionalProperties: false` travels in the
+  unparseable, outside its `enumOf`, or **undeclared** comes back as `isError` naming it — `additionalProperties: false` travels in the
   published schema and nothing on the wire enforces it — and so does a document that is not there, as
-  `No <model> found for the arguments given.` A `prompt`, having no `isError` to carry a refusal, answers `-32602`.
+  `No <model> found for the arguments given.` A prompt, having no `isError` to carry a refusal, answers `-32602`.
   Only a real failure logs a stack; an agent can drive the rest at will.
 - **Three revisions are spoken**: the modern `2026-07-28` and the legacy `2025-11-25` / `2025-06-18`, which are
   wire-identical over the POST-only surface this implements — a client whose proposal is not listed is told to
@@ -225,7 +228,7 @@ export class TaskEndpoint extends endpoint(srv.task, ({ mutation, prompt }) => (
 - **A modern-era request mirrors `MCP-Protocol-Version` and `Mcp-Method` into headers** (plus `Mcp-Name` when the
   body names one), and one that leaves a mirror out is refused just like one that contradicts the body: a gateway
   rule keyed on a header never fires for the request that omitted it. Legacy requests are not checked. Capabilities
-  are derived from the catalogue, so a server with no prompts does not advertise `prompts`.
+  are derived from the catalogue; `prompts` is advertised when the build serves pages, since prompts are theirs.
 - **An expired, wrongly-audienced or unverifiable bearer token is refused up front**, so an agent is told to
   authenticate rather than that the tool does not exist. The signature is checked through `auth.verify`, which the
   module that mints the tokens supplies (`libs/shared` does, from the app's signing secret); without a verifier the
@@ -313,23 +316,41 @@ delegates to lives in `akanjs/server` (`OAuthAuthorize`, `OAuthToken`, `OAuthReg
   derived fallback is seeded from the app, environment and repo names and forges an admin token for anyone who
   knows them. `AKAN_ALLOW_DERIVED_JWT_SECRET=1` accepts that risk explicitly.
 
-## `prompt()`
-**`prompt()`** is invoked by the *user* — a client renders it as a slash command — not chosen by the model. `exec`
-returns `PromptMessage[]`, or a bare string that is wrapped into one user message; build them with `Msg.user` /
-`Msg.assistant` / `Msg.link` / `Msg.resource` / `Msg.image` / `Msg.imageOf`. It takes `.param()` and `.search()`
-only, because `prompts/get` sends a flat string map. **An embedded payload is masked by the model you name** —
-`Msg.resource(uri, task, { model: cnst.LightTask })`, or `Msg.mask(cnst.LightTask, task)` for one piece of an
-assembly. Taking the model as an argument is what makes a `{ ...doc }` spread maskable, since that and `toJSON()`
-arrive with the class already gone; a value with no model named whose `hidden`/`secret` fields are populated is
-**refused**, one level into a plain object too. **A `prompt` is also mounted as a
-plain HTTP `GET` whether or not you enabled MCP**, because that route is what lets a web UI preview one — and it
-is in your OpenAPI document like any other `GET`, answering the one fixed `PromptMessage[]` shape. MCP exposure
-gates the catalogue, not the surface, so guard it
-like any other read — and a prompt declaring no
-`guards` at all is named in the boot log, while an explicit `[Public]` is a decision and stays quiet. Every `Msg` builder takes
-optional `annotations` last (`audience`, `priority` 0..1, `lastModified`) — give the instruction a high `priority`
-and its attachments a low one, or a client with a full window drops blocks by position and keeps the attachment
-over the ask.
+## Page Prompts — `page().prompt()`
+**A prompt is a screen.** There is no `prompt()` on `endpoint()`: the page file declares it —
+`page().param("projectId", ID, { desc: "The project to brief." }).prompt("briefProjectTickets", "Brief the ticket
+board of one project.").render(…)` — and that is the whole surface. `prompts/list` is every page carrying
+`.prompt()`; its `.param()` stages are the required arguments and its `.search()` stages the optional ones, a list
+argument is comma-separated on the wire and its description says so, and an `ID`/`Int`/`enumOf` value is checked by
+the page's own declaration. **`prompts/get` runs the page's body** — root layouts, layouts, then the page's
+`.render()` — in the RSC worker under the caller's bearer token, the way a tab would open it. Nothing is rendered:
+the JSX comes back as an element tree nobody walks, no client component runs, and the screen's data footprint is
+exactly the `fetch.*` queries its body made, with the arguments it made them with. The answer is the description as
+the first message (priority 1), one embedded `resource` per query masked by that endpoint's return model and
+addressed by the `akan://` uri the tool answers to (`akan://<toolKey>?args` for a custom read) — one document read
+in two shapes, a layout's `project` beside the page's `lightProject`, travels once as the larger — and a closing
+`Tools for this screen: …` line naming the published tools of the modules the screen fetched from, minus the reads
+whose answers are attached above and filtered to what this caller may see — which is how a model reading a ticket
+board is handed the ticket tools and not three hundred. Lists are cut to `promptBudget` (60,000 characters;
+`option.setMcp({ promptBudget })`, `AKAN_MCP_PROMPT_BUDGET`), largest first, and the cut is said: `Attached the
+first 20 of 341 rows of \`ticketListInProject\`; call it for the rest.` Only lists are cut — a single document rides
+whole, so the budget is what the lists are trimmed to fit under, not a ceiling a screen of large documents cannot
+pass. A layout's own queries (a project selector's `projectListInOrg`) are part of every screen under it and are
+attached too. **No argument fallback**: a required argument left out answers one message — `No projectId was named for
+"briefProjectTickets". Find it with \`projectListBySearch\`, then run this prompt again with projectId=<id>.` —
+and runs nothing, because a prompt cannot re-run itself and context filled in on a guess would never be used. A
+page that redirects (`getSelf({ unauthorize })`), or whose `fetch.*` a guard refuses with 401/403, answers the 401
+credential challenge when the call carried no token and `This screen is not available to the signed-in account.`
+when it did — the same sentence for both, so a refused id is never confirmed to exist; `router.notFound()` and a
+404 from a query are `No screen exists for these arguments.`; anything else the body throws is `The page failed to
+load.`, with the cause in the server log only. **The description is the only instruction.** `<Agent.Guide>` is for the in-page agent, whose
+levers are the screen's controls, and is never read here, where the levers are the API — so write the description
+in English, in the API's vocabulary, and put a computed rule (the legal status transitions) into it as a static
+table the model combines with the attached state. Names match `^[A-Za-z0-9_-]{1,64}$` and are unique across pages;
+two pages claiming one name fail the listing. An API-only build (`web: false`) publishes no prompts, and the
+in-page chat lists none of them: its `/` menu is its six built-in commands. Pick which screens to publish by this
+rule: a page taking no arguments is the most useful prompt, since MCP has no completion — one taking an id is for
+when the id is already in hand.
 
 ## Progress Reporting
 **`McpProgress.report(n, { total, message })`** reports progress from anywhere inside a call, a service or adapter
@@ -399,8 +420,8 @@ the same guards.** What stays closed is closed because no agent has a reason to
 ## Writing `instructions`
 
 `*.abstract.md` and `<Agent.Guide>` never reach an MCP client. Exactly three texts do: `instructions`, every
-published entry's `.desc()`, and a `prompt()`. All three are English, whatever the users speak — the reader is a
-model, and the catalogue is built once in one `language` and cached by clients.
+published entry's `.desc()`, and a page's `.prompt()` description. All three are English, whatever the users speak
+— the reader is a model, and the catalogue is built once in one `language` and cached by clients.
 
 - **`instructions` is the workflow.** Five to eight sentences, in this order: what the app is and what its nouns
   mean; **which tool to call first** and which ids the rest take; how a name becomes an id; what a write confirms
@@ -419,9 +440,10 @@ model, and the catalogue is built once in one `language` and cached by clients.
 - **`.desc()` is the reason to pick one tool** — what it returns and when to use it, two clauses. An id argument's
   `.desc()` names the tool that returns it (`From projectInOrg`). The generated CRUD borrows the model's `.of()`
   label and `.desc()`, which is the only text those entries can carry.
-- **`prompt()` is a workflow the user invokes** as a slash command, not one the model chooses — a weekly report,
-  an onboarding check. Put the ask in `Msg.user` at a high `priority` and the attachments in `Msg.resource` masked
-  by their `Light` model at a low one.
+- **A page prompt is a workflow the user invokes** as a slash command, not one the model chooses — a weekly
+  report, an onboarding check. Its instruction is the `.prompt()` description alone and its attachments are what
+  the screen fetched, masked by their return models — so to change what a prompt hands the model, change what the
+  screen loads, and keep the description to the ask.
 
 ## Verifying An App