@akanjs/cli 2.3.11-rc.1 → 2.3.11-rc.10

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@akanjs/cli",
-  "version": "2.3.11-rc.1",
+  "version": "2.3.11-rc.10",
   "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": "2.3.11-rc.1",
+    "akanjs": "2.3.11-rc.10",
     "chalk": "^5.6.2",
     "commander": "^14.0.3",
     "daisyui": "5.5.23",

package/templates/appSample/lib/task/Task.Zone.tsx

@@ -4,12 +4,10 @@ export default function getContent(scanInfo: AppInfo | LibInfo | null, dict: { a
   return {
     filename: "Task.Zone.tsx",
     content: `"use client";
-import { Task, usePage } from "@apps/${dict.appName}/client";
+import { type cnst, Task, usePage } from "@apps/${dict.appName}/client";
 import type { ClientInit, ClientView } from "akanjs/fetch";
 import { Link, Load } from "akanjs/ui";
 
-import * as cnst from "../cnst";
-
 // ===== Task.Zone.tsx =====
 // Convention: lib/<module>/ — PascalCase .tsx, Zone suffix = composition layer between pages and UI.
 // Zone components use Load.Units / Load.View from akanjs/ui — the framework convention for data-bound zones.

package/templates/appSample/lib/task/task.service.ts

@@ -10,7 +10,7 @@ import * as db from "../db";
 // Convention: <module>.service.ts — business logic orchestration for a database module.
 // Extends serve(db.<module>, depsCallback) from akanjs/service — binds to the DB model, receives DI deps.
 // Auto-generated by akan sync (do not write manually):
-//   getTask(id), createModel(data), updateModel(id, data), removeModel(id),
+//   getTask(id), createTask(data), updateTask(id, data), removeTask(id),
 //   listByStatus(status), searchDocs(text), and all filter+query methods from document.ts.
 // Manual below: lifecycle hooks, custom business logic methods.
 // Registered by akan sync into srv.ts barrel.

package/templates/crudPages/[__model__Id]/edit/page.tsx

@@ -10,14 +10,14 @@ export default function getContent(scanInfo: AppInfo | LibInfo | null, dict: Dic
     filename: "_index.tsx",
     content: `
 import { Load } from "akanjs/ui";
-import { fetch, usePage, ${dict.Model} } from "${dict.appName}/client";
+import { fetch, usePage, ${dict.Model} } from "@apps/${dict.appName}/client";
 import type { PageConfig } from "akanjs/client";
 
 interface PageProps {
   params: { ${dict.model}Id: string };
 }
 
-export default function Page({ params }: PageProps) {
+export default async function Page({ params }: PageProps) {
   const { l } = usePage();
   const { ${dict.model}Id } = params;
   const { ${dict.model}, ${dict.model}Edit } = await fetch.edit${dict.Model}(${dict.model}Id);

package/templates/crudPages/[__model__Id]/page.tsx

@@ -9,8 +9,8 @@ export default function getContent(scanInfo: AppInfo | LibInfo | null, dict: Dic
   return {
     filename: "_index.tsx",
     content: `
-import { ${dict.Model}, fetch, usePage } from "${dict.appName}/client";
-import { Link, Load } from "akanjs/ui";
+import { ${dict.Model}, fetch, usePage } from "@apps/${dict.appName}/client";
+import { Link } from "akanjs/ui";
 import type { PageConfig } from "akanjs/client";
 
 interface PageProps {
@@ -29,7 +29,7 @@ export async function generateHead({ params }: PageProps) {
     </>
   );
 }
-export default function Page({ params }: PageProps) {
+export default async function Page({ params }: PageProps) {
   const { l } = usePage();
   const { ${dict.model}Id } = params;
   const { ${dict.model}, ${dict.model}View } = await fetch.view${dict.Model}(${dict.model}Id);

package/templates/crudPages/page.tsx

@@ -10,10 +10,10 @@ export default function getContent(scanInfo: AppInfo | LibInfo | null, dict: Dic
     filename: "_index.tsx",
     content: `
 import { ${dict.Model}, fetch, usePage } from "@apps/${dict.appName}/client";
-import { Link, Load } from "akanjs/ui";
+import { Link } from "akanjs/ui";
 import type { PageConfig } from "akanjs/client";
 
-export default function Page() {
+export default async function Page() {
   const { l } = usePage();
   const { ${dict.model}InitInPublic } = await fetch.init${dict.Model}InPublic();
   return (

package/templates/crudSinglePage/page.tsx

@@ -10,10 +10,10 @@ export default function getContent(scanInfo: AppInfo | LibInfo | null, dict: Dic
     filename: "_index.tsx",
     content: `
 import type { PageConfig } from "akanjs/client";
-import { Load, Model } from "akanjs/ui";
-import { ${dict.Model}, type cnst, fetch, usePage } from "@apps/${dict.appName}/client";
+import { Model } from "akanjs/ui";
+import { ${dict.Model}, fetch, usePage } from "@apps/${dict.appName}/client";
 
-export default function Page() {
+export default async function Page() {
   const { l } = usePage();
   const { ${dict.model}InitInPublic } = await fetch.init${dict.Model}InPublic();
   return (

package/templates/module/__Model__.Template.tsx

@@ -11,7 +11,7 @@ export default function getContent(scanInfo: AppInfo | LibInfo | null, dict: Dic
     content: `
 "use client";
 import { Field, Layout } from "akanjs/ui";
-import { cnst, st, usePage } from "@${scanInfo?.type ?? "apps"}/${dict.sysName}/client";
+import { st, usePage } from "@${scanInfo?.type ?? "apps"}/${dict.sysName}/client";
 
 interface GeneralProps {
   className?: string;
@@ -23,10 +23,9 @@ export const General = ({ className }: GeneralProps) => {
   return (
     <Layout.Template className={className}>
       <Field.Text
-        label={l("${dict.model}.id")}
-        desc={l("${dict.model}.id.desc")}
-        value={${dict.model}Form.id}
-        onChange={st.do.setIdOn${dict.Model}}
+        label={l("${dict.model}.name")}
+        value={${dict.model}Form.name}
+        onChange={st.do.setNameOn${dict.Model}}
       />
     </Layout.Template>
   );

package/templates/module/__Model__.Unit.tsx

@@ -17,7 +17,7 @@ export const Card = ({ ${dict.model}, href }: ModelProps<"${dict.model}", cnst.L
   const { l } = usePage();
   return (
     <Link href={href} className="w-full">
-      <div>{l("${dict.model}.id")}:{${dict.model}.id}</div>
+      <div>{l("${dict.model}.name")}: {${dict.model}.name}</div>
     </Link>
   );
 };

package/templates/module/__Model__.View.tsx

@@ -20,7 +20,7 @@ export const General = ({ className, ${dict.model} }: GeneralProps) => {
   const { l } = usePage();
   return (
     <div className={clsx("w-full", className)}>
-      <div>{l("${dict.model}.id")}: {${dict.model}.id}</div>
+      <div>{l("${dict.model}.name")}: {${dict.model}.name}</div>
     </div>
   );
 };

package/templates/module/__Model__.Zone.tsx

@@ -11,7 +11,9 @@ export default function getContent(scanInfo: AppInfo | LibInfo | null, dict: Dic
     content: `
 "use client";
 import { Load } from "akanjs/ui";
-import { cnst, ${dict.Model} } from "@${scanInfo?.type ?? "apps"}/${dict.sysName}/client";
+// Alias the domain namespace so the Card/View exports below never collide with the model name
+// (a model literally named "card" or "view" would otherwise shadow this import).
+import { type cnst, ${dict.Model} as ${dict.Model}Domain } from "@${scanInfo?.type ?? "apps"}/${dict.sysName}/client";
 import type { ClientInit, ClientView, SliceMeta } from "akanjs/fetch";
 
 interface CardProps {
@@ -25,7 +27,7 @@ export const Card = ({ className, init, slice }: CardProps) => {
       className={className}
       init={init}
       renderItem={(${dict.model}) => (
-        <${dict.Model}.Unit.Card key={${dict.model}.id} href={\`/${dict.model}/\${${dict.model}.id}\`} ${dict.model}={${dict.model}} />
+        <${dict.Model}Domain.Unit.Card key={${dict.model}.id} href={\`/${dict.model}/\${${dict.model}.id}\`} ${dict.model}={${dict.model}} />
       )}
     />
   );
@@ -36,7 +38,7 @@ interface ViewProps {
   view: ClientView<"${dict.model}", cnst.${dict.Model}>;
 }
 export const View = ({ view }: ViewProps) => {
-  return <Load.View view={view} renderView={(${dict.model}) => <${dict.Model}.View.General ${dict.model}={${dict.model}} />} />;
+  return <Load.View view={view} renderView={(${dict.model}) => <${dict.Model}Domain.View.General ${dict.model}={${dict.model}} />} />;
 };
 `,
   };

package/templates/module/__model__.constant.ts

@@ -10,11 +10,12 @@ export default function getContent(scanInfo: AppInfo | LibInfo | null, dict: Dic
 import { via } from "akanjs/constant";
 
 export class ${dict.Model}Input extends via((field) => ({
+  name: field(String),
 })) {}
 
 export class ${dict.Model}Object extends via(${dict.Model}Input, (field) => ({})) {}
 
-export class Light${dict.Model} extends via(${dict.Model}Object, [] as const, (resolve) => ({})) {}
+export class Light${dict.Model} extends via(${dict.Model}Object, ["name"] as const, (resolve) => ({})) {}
 
 export class ${dict.Model} extends via(${dict.Model}Object, Light${dict.Model}, (resolve) => ({})) {}
 

package/templates/module/__model__.dictionary.ts

@@ -24,7 +24,9 @@ export const dictionary = modelDictionary(["en", "ko"])
   .of((t) =>
     t(["${modelLabelEn}", "${modelLabelKo}"]).desc(["${modelDescEn}", "${modelDescKo}"])
   )
-  .model<${dict.Model}>((t) => ({}))
+  .model<${dict.Model}>((t) => ({
+    name: t(["Name", "이름"]),
+  }))
   .insight<${dict.Model}Insight>((t) => ({}))
   .slice<${dict.Model}Slice>((fn) => ({
     inPublic: fn(["${dict.Model} In Public", "${dict.Model} 공개"]).arg((t) => ({})),

package/templates/workspaceRoot/.cursor/rules/akan.mdc.template

@@ -1,38 +1,9 @@
 ---
-description: Akan.js workspace conventions for coding agents
+description: Akan workspace agent guide
 alwaysApply: true
 ---
 
-# Akan.js Workspace Rules
+Follow the workspace agent guide, which is the single source of truth for Akan conventions,
+generated-file rules, and the MCP workflow policy.
 
-- Keep edits inside the established Akan structure: `apps/<app>`, `libs/<lib>`, `pkgs/*`, and `infra`.
-- Pages live under `apps/<app>/page`; index routes use `_index.tsx`, and nested layouts use `_layout.tsx`.
-- Database domain modules live under `lib/<model>`.
-- Service modules live under `lib/_<service>`.
-- Scalar modules live under `lib/__scalar/<scalar>`.
-- Module abstracts live beside module code as `<model>.abstract.md`, `<service>.abstract.md`, or
-  `<scalar>.abstract.md`. Read them before changing module behavior.
-- Do not hand-edit generated Akan files such as `akan.app.json`, `client.ts`, `server.ts`, generated facet indexes,
-  `lib/cnst.ts`, `lib/dict.ts`, `lib/db.ts`, `lib/srv.ts`, `lib/st.ts`, `lib/sig.ts`, `lib/useClient.ts`, or
-  `lib/useServer.ts`.
-- Prefer Akan MCP workflows before direct source edits: use `akan mcp --mode plan` for workflow discovery and
-  planning, then `akan mcp --mode apply` only for allowlisted apply, validation, and repair tools.
-- If `plan_workflow` returns `planPath` or `next.tool=apply_workflow`, call `apply_workflow({ planPath })` before
-  editing source files directly.
-- After `apply_workflow`, run `run_validation` with `validationTarget` when present; otherwise use `applyReportPath`.
-- Direct source edits are denied when an allowlisted Akan workflow or repair tool can perform the change.
-- Direct edits are fallback only after `list_workflows`/`explain_workflow` show no matching workflow, or after
-  `apply_workflow` reports unsupported/no-op/failed diagnostics that require manual action.
-- For compound requests, split the request into workflows and apply each `planPath` in order, such as `create-module`
-  followed by `add-field`.
-- If generated output is stale or broken, update the owning source file and run `akan repair generated` or
-  `akan sync <app-or-lib>` instead of patching generated files.
-- For new domain behavior, inspect sibling `constant`, `dictionary`, `signal`, `document`, `service`, `store`, and UI
-  module files before changing shape.
-- Update `*.abstract.md` when business invariants, workflows, or public behavior change. Do not update it for
-  formatting-only, import-only, or style-only changes.
-- Respect server/client import boundaries. Use `akanjs/server` only in server-side code and `akanjs/client` only in
-  client/page runtime code.
-- Treat `AKAN_PUBLIC_*` env vars as public values. Do not store secrets in them.
-- Verify changes with the smallest relevant command: `akan lint <target>`, `akan test <target>`, or
-  `akan build <app-name>`.
+@AGENTS.md

package/templates/workspaceRoot/.cursor/rules/application-test-commands.mdc.template

@@ -10,7 +10,7 @@ alwaysApply: true
 - To test a built artifact locally, run it from the generated app directory with the required Akan runtime environment variables.
 
 ```bash
-cd dist/apps/<appName> && USE_AKANJS_PKGS=true AKAN_PUBLIC_REPO_NAME=akansoft AKAN_PUBLIC_SERVE_DOMAIN="akamir.com" AKAN_PUBLIC_APP_NAME=seon AKAN_PUBLIC_ENV=local AKAN_PUBLIC_OPERATION_MODE=local SERVER_MODE=federation AKAN_PUBLIC_BASE_PATHS=neul,apptest,seon bun main.js
+cd dist/apps/<appName> && USE_AKANJS_PKGS=true AKAN_PUBLIC_REPO_NAME=akansoft AKAN_PUBLIC_SERVE_DOMAIN="akanjs.com" AKAN_PUBLIC_APP_NAME=seon AKAN_PUBLIC_ENV=local AKAN_PUBLIC_OPERATION_MODE=local SERVER_MODE=federation AKAN_PUBLIC_BASE_PATHS=operator,office,homepage bun main.js
 ```
 
 - Adjust `<appName>`, `AKAN_PUBLIC_APP_NAME`, and `AKAN_PUBLIC_BASE_PATHS` to match the app being tested.

package/templates/workspaceRoot/.cursor/rules/typescript-imports.mdc.template

@@ -9,5 +9,5 @@ alwaysApply: false
 - Use Bun and ESM assumptions from the root `tsconfig.json`.
 - Prefer path aliases over deep relative imports when crossing package boundaries.
 - Use `akanjs/*` for framework facets, `@apps/*` for apps, `@libs/*` for shared libs, and `@contract/*` for contract code.
-- Respect existing client/server entrypoints such as `@libs/shared/client`, `@libs/shared/server`, `@apps/puffinplace/client`, and `@apps/puffinplace/server`.
+- Respect existing client/server entrypoints such as `@libs/shared/client`, `@libs/shared/server`, `@apps/<% appName %>/client`, and `@apps/<% appName %>/server`.
 - Let Biome organize imports instead of manually reshuffling unrelated imports.

package/templates/workspaceRoot/.gitignore.template

@@ -67,7 +67,9 @@ local.properties
 **/public/fallback-*.js
 **/public/libs
 **/private/libs
+**/public/firebase-messaging-sw.js
 
+**/android/keystore.properties
 **/vendor/bundle/
 **/ios/App/App/public
 **/ios/App/App/Podfile.lock
@@ -118,4 +120,5 @@ libs/*/client.ts
 libs/*/server.ts
 libs/*/index.ts
 **/.akan
-**/bun.lock
+**/bun.lock
+**/tsconfig.tsbuildinfo

package/templates/workspaceRoot/AGENTS.md.template

@@ -28,7 +28,6 @@ Common generated files include:
 - `*/lib/cnst.ts`
 - `*/lib/db.ts`
 - `*/lib/dict.ts`
-- `*/lib/option.ts`
 - `*/lib/sig.ts`
 - `*/lib/srv.ts`
 - `*/lib/st.ts`
@@ -87,7 +86,8 @@ When adding a new database-backed domain module (e.g., product, user):
 
 ```bash
 # 1. Scaffold the module with Akan CLI (creates constant, service, signal, store, document files)
-akan create-module <module-name> --app <%= appName %>
+# The target app/lib is a POSITIONAL argument, not a --app flag.
+akan create-module <module-name> <%= appName %>
 
 # 2. Start dev server with HMR and type checking at http://localhost:8282
 akan start <%= appName %>
@@ -111,15 +111,41 @@ akan test <%= appName %>
 akan build <%= appName %>
 ```
 
+**Verify endpoints with signal tests, not raw HTTP.** The canonical way to check a query/mutation/slice
+contract is an in-memory signal test (`<model>.signal.test.ts`), using the test fetch harness
+(`getOrSetupSignalTestFetch`) — it is fast, needs no running server, and exercises `fetch.*`, `view/edit/merge<Model>`,
+and slice `init`/`list`/`insight` directly. Prefer it over `curl`: the dev gateway locale-prefixes routes (`/en/...`),
+so hand-rolled HTTP calls against a raw path can redirect unexpectedly. See `akan test <%= appName %>`.
+
 ### Other Frequently Used Commands
 
 ```bash
-akan create-scalar <scalar-name> --app <%= appName %>    # Add a scalar module (lib/__scalar/<scalar-name>/)
-akan create-service <service-name> --app <%= appName %>       # Add a service module (lib/_<service-name>/)
+akan create-scalar <scalar-name> <%= appName %>          # Add a scalar module (lib/__scalar/<scalar-name>/)
+akan create-service <service-name> <%= appName %>        # Add a service module (lib/_<service-name>/)
 akan test <%= appName %>                             # Run the test code (lib/*/*.signal.test.ts or others)
 akan lint <%= appName %>                             # Lint only (no typecheck)
 ```
 
+**CLI argument conventions.** Two argument styles, and mixing them up is a common mistake:
+
+- Scaffolding and whole-app commands take the target app/lib as a **positional** argument, not a flag:
+
+  ```bash
+  akan create-module photo <%= appName %>
+  akan create-scalar money <%= appName %>
+  akan create-service billing <%= appName %>
+  akan sync <%= appName %>
+  ```
+
+- Only the source-limited field commands use `--app`/`--module` flags:
+
+  ```bash
+  akan add-field --app <%= appName %> --module photo --field width --type Int
+  akan add-enum-field --app <%= appName %> --module photo --field status --values draft,active
+  ```
+
+Passing `--app` to `create-module` is not recognized, and the target app will not resolve.
+
 For the default generated app, start with:
 
 ```bash
@@ -130,6 +156,11 @@ akan start <%= appName %>
 
 Almost every Akan.js change follows this pattern. **Missing sync or repair is the #1 cause of agent confusion.**
 
+> **If the Akan MCP tools are not connected in your agent, skip straight to the CLI-only fallback below.**
+> `akan mcp --mode plan/apply` starts a stdio MCP server that only works when your agent is wired to it as an
+> MCP client. When those `list_workflows` / `plan_workflow` / `apply_workflow` tools are not available, the CLI
+> commands are a fully supported, first-class path — you are not losing any capability by using them.
+
 1. **Plan** — Ask the Akan MCP server for the workflow first.
    ```
    akan mcp --mode plan
@@ -171,12 +202,31 @@ Almost every Akan.js change follows this pattern. **Missing sync or repair is th
 
    If `akan sync` gives errors, try:
    - `akan build <%= appName %>` — full rebuild catches type errors sync may miss
-   - Re-run `akan create-module <name> --app <%= appName %>` if the scaffold is corrupted
+   - Re-run `akan create-module <name> <%= appName %>` if the scaffold is corrupted
 
 For compound natural-language requests, split the request into workflows and apply each artifact in order. For example,
 "create a project module and add a budget field" should run `create-module` plan/apply first, then `add-field`
 plan/apply, then validation/doctor on the returned `validationTarget`.
 
+### CLI-Only Fallback (MCP Not Connected)
+
+When the Akan MCP tools are not loaded, run the CLI commands directly. Each MCP tool maps 1:1 to a CLI command,
+and the CLI emits the same structured report via `--format json`:
+
+| MCP tool | CLI-only equivalent |
+|----------|---------------------|
+| `list_workflows` | `akan workflow list` |
+| `explain_workflow <name>` | `akan workflow explain <name>` |
+| `plan_workflow <name> ...` | `akan workflow plan <name> ... --format json --out <planPath>` |
+| `apply_workflow { planPath }` | `akan workflow apply <planPath> --format json` (add `--dry-run` to preview) |
+| `run_validation { validationTarget }` | `akan doctor --strict --format json` (or `akan typecheck <%= appName %>`) |
+| `repair_generated` / `repair_imports` / `repair_module_shape` | `akan repair generated\|imports\|module-shape --app <%= appName %> --format json` |
+
+The scaffolding primitives (`akan create-module`, `akan create-scalar`, `akan create-service`, `akan add-field`,
+`akan add-enum-field`) are the same primitives the workflows call, so `create-module <name> <%= appName %>` followed
+by `akan sync <%= appName %>` is equivalent to running the `create-module` workflow. Direct source edits remain the
+final fallback when no CLI command covers the change.
+
 ## Quick Decision Matrix — "Where do I put this code?"
 
 | You want to... | Create in... | Run after... |
@@ -185,6 +235,7 @@ plan/apply, then validation/doctor on the returned `validationTarget`.
 | Add a pure workflow / integration (e.g., Payment, Email) | `lib/_<service>/` → service, signal, store, dictionary, abstract | `akan sync <name>` |
 | Add a reusable value type (e.g., Address, WorkHistory) | `lib/__scalar/<type>/` → constant, dictionary, abstract | `akan sync <name>` |
 | Create a new URL-visitable page | `page/` → `_index.tsx`, `_layout.tsx`, `[param]/_index.tsx` | Rebuild (akan start auto-detects) |
+| Change the app color theme / design tokens | `apps/<app>/page/styles.css` → edit the daisyUI `@plugin "daisyui/theme"` blocks (`light`/`dark`, the `--color-*` variables) | akan start hot-reloads |
 | Add a form or reusable UI component | `ui/` → PascalCase `.tsx` with `"use client"` if needed | `akan sync <name>` |
 | Add a React hook or browser helper | `webkit/` → camelCase `.ts` with `"use client"` | `akan sync <name>` |
 | Add a server-only guard, middleware, or adaptor | `srvkit/` → PascalCase `.ts` | `akan sync <name>` |
@@ -202,6 +253,7 @@ plan/apply, then validation/doctor on the returned `validationTarget`.
 | Skip running `akan sync` after deleting a file | Deleted files remain referenced in barrel exports, causing import errors everywhere. | Run `akan sync <name>` after every file add, remove, or rename |
 | Use "use client" or `useState`/`useEffect` in pages/*.tsx, *.Unit.tsx, and *.View.tsx files | Server code cannot use React hooks. Wrap in a separate `"use client"` component. | Move hook logic to `webkit/` or a `"use client"` UI component |
 | Use `<a>` tag for internal navigation between pages | Akan.js uses `<Link>` from `akanjs/ui` for client-side navigation — avoids full page reloads. | `import { Link } from "akanjs/ui"` and use `<Link href="/task">...</Link>` |
+| Name a custom `Endpoint`/`Slice` like a generated CRUD op — `create<Model>`, `update<Model>`, `remove<Model>`, `view<Model>`, `edit<Model>`, `merge<Model>` | These names are already auto-generated. A collision can pass sync/typecheck/build and only fail at runtime. | Pick a distinct verb, e.g. `startTask`/`archiveTask`, never `createTask` for a custom endpoint |
 
 ## Generated File Tracker (Quick Reference)
 
@@ -212,7 +264,6 @@ These files are regenerated by `akan sync` and overwritten on every sync. **Do n
 | `*/lib/cnst.ts` | All `*/lib/*/**.constant.ts` | Barrel for all constants |
 | `*/lib/db.ts` | All `*/lib/<model>/*.document.ts` | Barrel for all document models |
 | `*/lib/dict.ts` | All `*/lib/*/**.dictionary.ts` | Barrel for all dictionaries |
-| `*/lib/option.ts` | Generated option helpers | Option helper entry |
 | `*/lib/sig.ts` | All `*/lib/**/**.signal.ts` | Barrel for all signals |
 | `*/lib/srv.ts` | All `*/lib/**/**.service.ts` | Barrel for all services |
 | `*/lib/st.ts` | All `*/lib/**/**.store.ts` | Barrel for all stores |
@@ -289,7 +340,13 @@ const form = st.use.taskForm();
 
 ### Recipe 2: Injecting a Dependency into a Service
 
-Two patterns: injecting an **adapter** (external client) or injecting another **module's service**.
+Three patterns: injecting an **external adapter** (`use<>()`), another **module's service** (`service<>()`),
+or a **predefined framework adapter** (`plug()`). A field named `<refName>Service` resolves to the service
+registered under `<refName>` — the `Service`/`Signal` suffix is required and stripped to derive the lookup key.
+
+> `apps/<app>/lib/option.ts` is a **user-owned** file scaffolded once — edit it to register adapters/DI. Unlike the
+> barrels (`cnst.ts`, `db.ts`, `srv.ts`, …) it is **not** overwritten by `akan sync`, so your `.use(...)` registrations
+> are safe.
 
 **A. Adapter injection via `use<>()` (for external clients / global singletons)**
 
@@ -332,18 +389,51 @@ export class TaskService extends serve(db.task, ({ service }) => ({
 }
 ```
 
+**C. Predefined framework adapter injection via `plug()` (storage, cache, queue, schedule, …)**
+
+Akan ships predefined adapter roles from `akanjs/service`: `StorageAdaptorRole`, `CacheAdaptorRole`,
+`QueueAdaptorRole`, `ScheduleAdaptorRole`, `DatabaseAdaptorRole`, `WebsocketAdaptorRole`,
+`LoggingAdaptorRole`, `CompressAdaptorRole`. `plug()` injects the concrete adapter bound to that role (the
+default `StorageAdaptor` binding is `BlobStorage`). `plug()` also accepts a concrete adapter class directly.
+
+```typescript
+// In <model>.service.ts — inject the framework storage adapter by role
+import { plug, serve, StorageAdaptorRole } from "akanjs/service";
+
+export class TaskService extends serve(db.task, ({ plug }) => ({
+  storage: plug(StorageAdaptorRole),
+})) {
+  async attach(taskId: string, path: string, localPath: string) {
+    // BlobStorage returns a URL under blobStorage.urlPrefix (default "/api/localFile/getBlob").
+    return await this.storage.uploadDataFromLocal({ path, localPath });
+  }
+}
+```
+
+For a custom adapter class (not a predefined role), pass the class itself, e.g. `ipfsApi: plug(IpfsApi)`
+(see `libs/shared/lib/file/file.service.ts`). Injecting a file/image field is usually simpler than calling
+storage directly: declare `image: field(File).optional()` (or `images: field([File])`) on the model and let the
+store's generated `upload<Field>On<Model>(fileList)` action handle the upload.
+
 ---
 
 ### Recipe 3: Creating and Using a Slice
 
 A Slice is a named, filtered data view. Add file entries and connect from a page.
 
+> **Silent failure — a slice `exec` must return a query descriptor, never an executed list.**
+> Return `this.taskService.queryByStatuses(...)` (the `query<Filter>` builder), **not**
+> `this.taskService.listByStatuses(...)` / `listBy...(...)` (which returns a `Promise<Doc[]>`).
+> Returning an array type-checks but throws at runtime during insight aggregation with the opaque
+> `Error: Unknown document field path: 0`. If you see that error, your slice is returning a list, not a query.
+
 ```typescript
 // 1. apps/<app>/lib/<model>/<model>.signal.ts — Define the slice
 export class TaskSlice extends slice(srv.task, (init) => ({
   inTodo: init()
     .search("statuses", [cnst.TaskStatus])
     .exec(function (statuses?) {
+      // ✅ query<Filter> — a query descriptor.  ❌ listByStatuses(...) returns an array and fails at runtime.
       return this.taskService.queryByStatuses(statuses ?? ["todo", "inProgress"]);
     }),
 })) {}
@@ -522,6 +612,41 @@ For each business question, follow this chain:
 | What client state is shared? | `store.ts` — `store()` with auto-generated form/insight state + custom actions |
 | What should users see? | `View.tsx` + `Zone.tsx` (detail/container), `Template.tsx` (forms), `Unit.tsx` (cards), `Util.tsx` (buttons) |
 
+## Modeling & Query Gotchas
+
+A short list of things the type system does not always catch:
+
+- **Slices return a query, not a list.** A slice `exec` must return `this.<model>Service.query<Filter>(...)`, never
+  a `list<Filter>(...)` / `listBy...(...)` array. Returning an array type-checks but fails at runtime with
+  `Unknown document field path: 0`. (See Recipe 3.)
+- **Custom endpoint names must not collide with generated CRUD.** `create/update/remove/view/edit/merge<Model>`
+  already exist. A collision can build green and fail only at runtime — pick a distinct verb.
+- **Numbers are `Int` or `Float`, never `Number`.** `field(Number)` / `.body("x", Number)` fail to typecheck. Use
+  `Int` for counts, `Float` for decimals.
+- **Array fields use `field([T])`.** e.g. `tags: field([String])`, `images: field([File])` — not `field(String)` with
+  a suffix.
+- **Reading a secret field needs an explicit select.** `field(...).secret()` values (e.g. `passwordHash`) are stripped
+  from query results by default. Fetch them with `{ select: { <field>: true } }`, e.g.
+  `this.userModel.pickById(id, { select: { passwordHash: true } })`.
+
+## Current User, Guards & Auth-Gated Pages
+
+Built-in user authentication (session / JWT / password hashing) ships as a separate Akan auth library, not in the
+core framework. The core framework gives you the composition points below; wire the auth library through them.
+
+- **Guards** attach at the signal declaration, not per-method:
+  `endpoint(srv.task, { guards: { root: SignedIn } }, ({ mutation }) => ({...}))` or
+  `slice(srv.task, { guards: { root: SignedIn, get: Public, cru: Public } }, ...)`. `Public` always allows; other
+  guards implement the `Guard` interface in `srvkit/` (server-only) and read the request context.
+- **Read the current user inside a custom endpoint** by injecting an `InternalArg` with `.with(...)`:
+  `mutation(cnst.Task).with(CurrentUserId).exec(async function (currentUserId) { ... })`. The `Guard` /
+  `InternalArg` helpers live in `srvkit/` and read `context.getHttpContext().req.user`.
+- **Auto-generated CRUD and `serve()` service methods / lifecycle hooks do not receive session context.** If an
+  operation needs the acting user, expose a custom endpoint that takes it via `.with(CurrentUserId)` — never trust a
+  client-supplied user id.
+- **SSR auth-gated pages: guard at the layout.** Check the session in the `_layout.tsx` loader and redirect when it is
+  absent, so nested pages never render for signed-out users.
+
 ## Auto-Generated API Reference
 
 akan sync automatically generates APIs across all layers. Only write custom logic — never hand-write what the framework generates.
@@ -545,7 +670,7 @@ akan sync automatically generates APIs across all layers. Only write custom logi
 |---------------|-------------|
 | `this.<model>Model` | Auto-injected model adaptor |
 | `get<Model>(id)`, `load<Model>(id)` | Single document lookup |
-| `createModel(data)`, `updateModel(id, data)`, `removeModel(id)` | CRUD operations |
+| `create<Model>(data)`, `update<Model>(id, data)`, `remove<Model>(id)` | CRUD operations — named after the model, e.g. `createTask`/`updateTask`/`removeTask` (there is no literal `createModel`) |
 | `list<Query>(args)`, `find<Query>(args)`, `pick<Query>(args)` | Filter-based queries |
 | `exists<Query>(args)`, `count<Query>(args)`, `insight<Query>(args)` | Filter-based helpers |
 | `_preCreate`, `_postCreate`, `_preUpdate`, `_postUpdate`, `_preRemove`, `_postRemove` | Lifecycle hooks (override to add logic) |
@@ -576,3 +701,13 @@ akan sync automatically generates APIs across all layers. Only write custom logi
 | `insight[Query](args)`, `query[Query](args)` | Insight and raw query |
 
 **Rule**: Define `Filter` with `.query()` conditions in `document.ts`. akan sync auto-generates all 10 query helper methods per filter. Write `Document` chain methods only for state transitions with validation.
+
+## Generated Context
+
+The section below is regenerated by `akan agent install` (run `bun run setup:agent`). It lists this
+workspace's apps, generated files, validation commands, and framework guide. Edit anything outside the
+markers freely; content between them is overwritten on the next install.
+
+<!-- akan:agent:start -->
+<!-- Populated by `akan agent install`. Run `bun run setup:agent` to refresh. -->
+<!-- akan:agent:end -->

package/templates/workspaceRoot/biome.json.template

@@ -50,7 +50,8 @@
       "!!**/dist",
       "!!**/.akan",
       "!!**/dump",
-      "!!**/local"
+      "!!**/local",
+      "!!**/ios/DerivedData"
     ]
   },
   "formatter": {
@@ -131,6 +132,20 @@
     }
   },
   "overrides": [
+    {
+      "includes": [
+        "apps/**/*.ts",
+        "apps/**/*.tsx",
+        "libs/**/*.ts",
+        "libs/**/*.tsx",
+        "!**/*.test.ts",
+        "!**/*.test.tsx",
+        "!**/*.spec.ts",
+        "!**/*.spec.tsx",
+        "!**/common/**"
+      ],
+      "plugins": ["./node_modules/@akanjs/devkit/lint/no-throw-raw-error.grit"]
+    },
     {
       "includes": ["**/page/**/*.ts", "**/page/**/*.tsx", "**/*.Unit.tsx", "**/*.View.tsx"],
       "plugins": [
@@ -146,6 +161,10 @@
       "includes": ["**/*.constant.ts", "**/*.document.ts", "**/*.service.ts", "**/*.store.ts"],
       "plugins": ["./node_modules/@akanjs/devkit/lint/no-js-private-class-method.grit"]
     },
+    {
+      "includes": ["**/*.signal.ts"],
+      "plugins": ["./node_modules/@akanjs/devkit/lint/no-redeclare-predefined-endpoint.grit"]
+    },
     {
       "includes": [
         "**/*.constant.ts",

package/templates/workspaceRoot/docs/GENERATED.md.template

@@ -17,7 +17,6 @@ sync or build can overwrite local changes.
 | `apps/*/lib/cnst.ts` | Re-exports constants and model shapes from module `*.constant.ts` files. |
 | `apps/*/lib/db.ts` | Re-exports database models from module `*.document.ts` files. |
 | `apps/*/lib/dict.ts` | Re-exports dictionaries from module `*.dictionary.ts` files. |
-| `apps/*/lib/option.ts` | Re-exports generated option helpers. |
 | `apps/*/lib/srv.ts` | Re-exports services from module `*.service.ts` files. |
 | `apps/*/lib/sig.ts` | Re-exports endpoints, slices, and internals from module `*.signal.ts` files. |
 | `apps/*/lib/st.ts` | Re-exports stores from module `*.store.ts` files. |

package/templates/workspaceRoot/package.json.template

@@ -13,9 +13,9 @@
     "agent:setup": "akan agent install all --force",
     "agent:doctor": "akan doctor --strict --format json",
     "agent:context": "akan context --format json",
-    "agent:mcp:readonly": "akan mcp-install cursor --mode readonly --force",
-    "agent:mcp:plan": "akan mcp-install cursor --mode plan --force",
-    "agent:mcp:apply": "akan mcp-install cursor --mode apply --force",
+    "agent:mcp:readonly": "akan mcp-install all --mode readonly --force",
+    "agent:mcp:plan": "akan mcp-install all --mode plan --force",
+    "agent:mcp:apply": "akan mcp-install all --mode apply --force",
     "agent:workflows": "akan workflow list",
     "agent:sample:context": "akan context --format markdown --app <%= appName %> --module project",
     "agent:sample:service": "akan create-service billing <%= appName %> --format json",