@akanjs/cli 3.1.1-rc.3 → 3.1.1-rc.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/.build-stamp CHANGED
@@ -1 +1 @@
1
- 5bce9c432681dbffde300f2d620f927c20721e6f64af5b6e6f672b5f8618531a
1
+ 1d5ee0aa09810bdd12aeba0494834f6a779e1a36738c336da1a29bcc976e334b
@@ -104,7 +104,10 @@ pages declaring one name never clash, and a registry kept outside the surface re
104
104
  parts, so that is what it answers with no `host` set. A `host` the app named is a gateway the class knows
105
105
  nothing about, and it stays text-only until `option.setLlm({ accepts })` says otherwise — handing bytes to a
106
106
  model that cannot decode them kills the whole turn on a 400, where text-only degrades them to a note the model
107
- can repeat back.
107
+ can repeat back. A `host` naming OpenAI's own endpoint is the default host by hostname, not a gateway, and an
108
+ app's own chat-completions adaptor claims through `OpenaiLlm.acceptsOf(llmOption)` instead of copying the rule —
109
+ a copy that read "any host is a gateway" kept a vision model text-only for an app that spelled out
110
+ `https://api.openai.com/v1`.
108
111
  - **A refusal is `agent.error.llmRequestFailed`, and it names the host** — unless the prompt did not fit. The
109
112
  provider's own sentence rides in `reason` and the hostname in `provider`. `LlmOverflow.refusal(host, status,
110
113
  reason)` builds it, and reads the one refusal a chat can undo — a prompt past the window, recognized from each
@@ -648,7 +651,18 @@ pages declaring one name never clash, and a registry kept outside the surface re
648
651
  page the user left. The reading built-ins (`readScreen`, `readState`, `highlight`, `viewImage`) declare it,
649
652
  because a wait costs 120ms of quiet at the very least and they change nothing a resource holds.
650
653
  New tools and state from a fresh route are still only listed from the next turn: the catalogue is snapshotted
651
- when the turn starts.
654
+ when the turn starts. **So a navigation ends the model's turn, and a name nobody listed is answered with the names
655
+ that exist.** A call is looked up when it runs, so one batched behind `navigate` already reaches the new screen —
656
+ but the model wrote it against the old catalogue, and a screen-scoped name it never saw is one it composed
657
+ (`addBacklogTicketInProject` for `addBacklogTicket`), and refused with a bare `Unknown tool` it composes the next.
658
+ `AgentService.preamble` therefore says that a navigation ends the turn and that names are never guessed, and the
659
+ session answers an unknown name with the tools listed now — saying, when the catalogue moved since the turn's
660
+ list was written, that the call was written against the screen it left and the new one's tools arrive with their
661
+ arguments next turn. `navigate`'s own answer says the same, reports the path the page actually landed on when a
662
+ redirect or the not-found page moved it elsewhere, and a path with no route is refused with the internal links on
663
+ screen (`ScreenTarget.linkedRoutes`) rather than an invitation to compose another. Layout-level tools — a channel
664
+ post, a new wiki page — stay listed across routes, which is why the cross-screen requests that use only them never
665
+ hit this.
652
666
  - **A tool that waits for its own work costs no model turns; one that returns early costs one round trip per
653
667
  look.** The session awaits `run`, so a `.exec` that awaits the store action finishing the job simply makes the
654
668
  turn take that long — and the change report that follows carries whatever landed, so the model needs no second
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@akanjs/cli",
3
- "version": "3.1.1-rc.3",
3
+ "version": "3.1.1-rc.4",
4
4
  "sourceType": "module",
5
5
  "type": "module",
6
6
  "publishConfig": {
@@ -39,7 +39,7 @@
39
39
  "@earendil-works/pi-tui": "1.3.0",
40
40
  "@inquirer/prompts": "^8.7.3",
41
41
  "@tailwindcss/node": "^4.3.3",
42
- "akanjs": "3.1.1-rc.3",
42
+ "akanjs": "3.1.1-rc.4",
43
43
  "chalk": "^6.0.1",
44
44
  "commander": "^15.0.0",
45
45
  "dayjs": "^1.11.23",