@akanjs/cli 3.0.0-beta.0 → 3.0.0-beta.2

package/.build-stamp

@@ -1 +1 @@
-65f8fdc9a4ad5e1054cf5bf3782626283fa2a2f9fc4e3079e0619ce0b60a4641
+91f5ad2ee63550b2ce4eee3fe99b7d2f064b37381641718bf796f2f31987b905

package/guidelines/agentRule/agentRule.instruction.md

@@ -72,9 +72,22 @@ apps and libs never import it directly (`no-import-external-library`) — everyt
   fills whichever adaptor holds `LlmAdaptorRole`, reaching it as the `llmOption` use. The settings are the role's
   rather than one provider's, so they survive a swap. **DeepSeek is the built-in default** (`deepseek-v4-flash` at
   `https://api.deepseek.com`); with no `apiKey` the app still boots and the chat answers `llmUnavailable`. Swap
-  providers the way middleware is applied: `option.applyAdaptor(LlmAdaptorRole, ClaudeLlm)`, where the
-  implementation is an `adapt()` class in a `srvkit/` implementing `LlmAdaptor.chat(request, onDelta?)` — ignore
-  `onDelta` and the chat still answers whole.
+  providers the way middleware is applied: `option.applyAdaptor(LlmAdaptorRole, AnthropicLlm)`. An app may still
+  write its own — an `adapt()` class in a `srvkit/` implementing `LlmAdaptor.chat(request, onDelta?)`, where
+  ignoring `onDelta` still answers whole — but for vision it no longer has to.
+- **Three providers ship, and only two of them read a picture.** `DeepseekLlm` is the default and declares no
+  `accepts`, which is a fact about its API rather than a gap. `OpenaiLlm` speaks the same chat-completions dialect
+  — `OpenaiDialect`, shared between them so a protocol fix lands once — against `https://api.openai.com/v1` and
+  declares `{ image: true }`, sending an image as a content part. `AnthropicLlm` is the Messages API and declares
+  `{ image: true, document: true }`; it is its own file rather than a branch, because the system prompt is a field
+  and not a message, tool calls and results are content blocks, the results ride in a *user* turn, roles must
+  alternate — so two wire turns that map to one role are merged — and `max_tokens` is required. **Both new ones
+  require `model`**: a default would age into a 404, and worse, it would decide the vision claim for the app.
+- **`accepts` is answered per model, through `option.setLlm({ accepts })`.** An adaptor answers for an API and one
+  API serves models that differ, so the override rides beside the `model` it is a fact about. It is not a table
+  the framework keeps: a table is a claim about models that ship after it, and getting this wrong is the worst
+  failure available — a provider handed bytes it cannot decode either refuses the turn or accepts it having seen
+  nothing, and the model then answers confidently about a file it never read.
 - **An adaptor answers `null` for "not configured" and *throws* for a refusal it can explain.** The two are
   different things to be told: collapsing both into `null`, the way the adapter convention otherwise reads, left a
   user reading `llmUnavailable` — "no model is configured" — about a conversation that had merely outgrown the
@@ -92,8 +105,11 @@ apps and libs never import it directly (`no-import-external-library`) — everyt
   prompt. **What the provider cannot read is replaced by a note naming the file**, never dropped: an attachment the
   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. Persisting keeps each
+  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. Swap in `OpenaiLlm` or `AnthropicLlm` and the same image
+  arrives as an image. `accepts.document` is one boolean over every non-image type, so an adaptor whose API has a
+  block for only some of them — Anthropic's `document` is PDF and nothing else — names the rest in the text rather
+  than dropping them, which is the wire's own rule applied at the one layer that knows which blocks exist. 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

package/guidelines/conventions/conventions.instruction.md

@@ -696,7 +696,9 @@ what every developer must know even when not building one.
   every tool runs in the caller's own browser session, gated by guards and the approval card. Its guard is
   `AgentRelayAccess`, which refuses every call until the app names a guard of its own —
   `option.setAgentAccess(SignedIn)`. **The LLM is configured in `option.ts`, never through the environment**
-  (`option.setLlm({ apiKey, model, host })`).
+  (`option.setLlm({ apiKey, model, host })`). Three providers ship — `DeepseekLlm` (the default, text only),
+  `OpenaiLlm` and `AnthropicLlm` (both read images) — and swapping one in is
+  `option.applyAdaptor(LlmAdaptorRole, AnthropicLlm)`.
 - **Declare the tool beside the control that already does it**, never as a separate surface:
   `st.tool("x").desc("…").arg("id", ID).exec(fn)` returns the callable to hand to `onClick` — one handler for the
   person and the agent. Publish it only where the screen already renders the control; a falsy name declares the

package/package.json

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