interlatch 0.25.0__tar.gz → 0.26.0__tar.gz

{interlatch-0.25.0 → interlatch-0.26.0}/CHANGELOG.md

@@ -3,6 +3,15 @@
 <!-- Don't add lines here: a pull request puts its line in a new file in changelog.d/ (see changelog.d/README.md),
      and each release moves the files it took into a dated section below. -->
 
+## 0.25.0 (2026-10-15)
+
+- **Innerlatch:** the Party, the Leaderboard, the Arena and their Google sign-in moved out of the dashboard into
+  Innerlatch, an area of its own drawn in violet. The door icon at the bottom of the rail brings up a large door: click
+  it to go through, or, signed out, sign in with Google and it opens by itself. Leaving, it shuts behind you. The
+  Journey strip leads the Party page instead of Home, the Arena is a page of its own, and old `#/party` and
+  `#/leaderboard` links still open. **Settings › Appearance › The door** hides the icon
+  ([Party](docs/party.md#getting-there)).
+
 ## 0.24.1 (2026-10-15)
 
 - **OpenCode is a source:** `interlatch connect opencode` (or the Sources page) records OpenCode sessions, from the

{interlatch-0.25.0 → interlatch-0.26.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: interlatch
-Version: 0.25.0
+Version: 0.26.0
 Summary: Shared memory for your coding agents: records every session (Claude Code, Codex, Copilot, Bob, Antigravity, OpenCode) locally and keeps what they learned, each lesson linked to the session it came from.
 Project-URL: Homepage, https://interlatch.com
 Project-URL: Documentation, https://interlatch.com/docs/
@@ -186,7 +186,8 @@ milliseconds; analysis runs later in the background.
 
 **Do I need Claude Code?** No. Analysis runs through Claude Code, Codex or IBM Bob, or a model provider's API with your
 own key: Anthropic, Amazon Bedrock, OpenAI, Azure OpenAI, OpenRouter, any OpenAI-compatible server, or Ollama on your own
-computer. Pick one in **Status › Analysis** or with `interlatch config set analysis.backend <name>`
+computer. Pick one when you run `interlatch install`, in **Status › Analysis**, or with
+`interlatch config set analysis.backend <name>`
 ([Model providers](https://github.com/Chatixia-AI/interlatch/blob/main/docs/analysis.md#model-providers)). Recording and browsing work either way; with none set up,
 sessions are archived and wait in the analysis queue.
 

{interlatch-0.25.0 → interlatch-0.26.0}/README.md

@@ -151,7 +151,8 @@ milliseconds; analysis runs later in the background.
 
 **Do I need Claude Code?** No. Analysis runs through Claude Code, Codex or IBM Bob, or a model provider's API with your
 own key: Anthropic, Amazon Bedrock, OpenAI, Azure OpenAI, OpenRouter, any OpenAI-compatible server, or Ollama on your own
-computer. Pick one in **Status › Analysis** or with `interlatch config set analysis.backend <name>`
+computer. Pick one when you run `interlatch install`, in **Status › Analysis**, or with
+`interlatch config set analysis.backend <name>`
 ([Model providers](docs/analysis.md#model-providers)). Recording and browsing work either way; with none set up,
 sessions are archived and wait in the analysis queue.
 

interlatch-0.26.0/changelog.d/adventure.md

@@ -0,0 +1,5 @@
+- **Adventure:** a new page in Innerlatch puts every lesson that counts on a pixel world map, one region per attribute
+  and one territory per roadmap module, fogged where no lesson reached yet. Click a monster for a turn-based battle
+  (Attack, Skill, Defend, Run) led by the agent that taught it; a win marks it cleared, and battles never change
+  levels. The Party page keeps the characters and quests, and a lesson link anywhere in Innerlatch now opens the lesson
+  in a window over the page instead of leaving for the dashboard ([Party](docs/party.md#adventure)).

interlatch-0.26.0/changelog.d/group-page.md

@@ -0,0 +1,7 @@
+- **A group's page:** **Analyze** on a project group's heading on the Projects page (or **The whole group** in the
+  sidebar) reads the group's projects as one big project. It shows each project's share of the group's time, cost and
+  knowledge, what waits on you across all of them, where their last sessions left off, each folder in git, their
+  roadmaps and their work week by week, with every item named by its project. A **Map** draws the projects and the
+  services and platforms they use, hand-drawn, with the ones they share easy to spot and an Excalidraw download; Usage
+  charts each project's time week by week. Each project's knowledge base and architecture sketch sit beside the
+  others, and the glossary terms the projects share come first ([Project groups](docs/dashboard.md#project-groups)).

interlatch-0.26.0/changelog.d/hub-join-http-client.md

@@ -0,0 +1,2 @@
+- **Joining a hub works again:** `interlatch hub join` no longer stops with "module 'http' has no attribute 'client'"
+  on a fresh install.

interlatch-0.26.0/changelog.d/install-choose-analyzer.md

@@ -0,0 +1,4 @@
+- **Choose what analyzes sessions at install:** `interlatch install` now lists every choice (Claude Code, Codex,
+  IBM Bob and the model providers' APIs, Ollama included) with whether each is ready, and sets up the one you pick:
+  its endpoint, API key and model, then one test call. `--backend <name>` chooses without asking
+  ([Install](docs/install.md#command-line)).

interlatch-0.26.0/changelog.d/town-and-gear.md

@@ -0,0 +1,5 @@
+- **Towns and gear:** each Adventure region has a town whose shop sells gear for its roadmap modules (a weapon, armor
+  and charm per module, in three tiers that open as your agents reach Lv 1, 3 and 5 in that skill) and battle supplies.
+  A lesson's first win pays gold and may drop loot of its kind; battles gain an **Item** command, and each agent
+  wears three slots, changed on its page or in the new **Bag**. Gear only changes battle numbers, never levels
+  ([Party](docs/party.md#towns-and-gear)).

{interlatch-0.25.0 → interlatch-0.26.0}/docs/cli.md

@@ -4,7 +4,7 @@
 
 | Command | |
 | --- | --- |
-| `interlatch install [--yes] [--analyze all\|N\|later] [--[no-]notify-updates] [--[no-]menu-bar] [--dry-run]` | Setup: lists the agents found, asks which to record, imports them, offers to analyze them now with progress (which builds the Glossary and the Map), starts the dashboard, and on macOS asks once whether to show [the menu-bar icon](install.md#the-menu-bar-icon) (off unless you say yes) ([Install](install.md#command-line)) |
+| `interlatch install [--yes] [--backend NAME] [--analyze all\|N\|later] [--[no-]notify-updates] [--[no-]menu-bar] [--dry-run]` | Setup: asks what analyzes sessions (`--backend` answers it: a coding agent or a [model provider](analysis.md#model-providers), set up on the spot), lists the agents found, asks which to record, imports them, offers to analyze them now with progress (which builds the Glossary and the Map), starts the dashboard, and on macOS asks once whether to show [the menu-bar icon](install.md#the-menu-bar-icon) (off unless you say yes) ([Install](install.md#command-line)) |
 | `interlatch app` | The desktop app (window + menu bar); needs the `app` extra |
 | `interlatch ui [--open] [--menu-bar]` | Dashboard (also always running at :11524 after install; if it is, `interlatch ui` says so and `--open` opens it). On macOS the one that runs at login also shows [the menu-bar icon](install.md#the-menu-bar-icon) if you turned it on at install; `--menu-bar`/`--no-menu-bar` overrides that. Sessions, Knowledge, Projects and Glossary switch between Cards and List (a sortable table; click a row for details), remembered per page |
 | `interlatch sessions [-p project] [--since 7d]` | List sessions |

{interlatch-0.25.0 → interlatch-0.26.0}/docs/dashboard.md

@@ -141,7 +141,7 @@ as on a session's page.
 ## Project groups
 
 Put related projects under one heading, such as **Aktio** for every Aktio repository, on the Projects page and in
-its sidebar. Groups are one level deep, and only change how projects are listed: each project keeps its own
+its sidebar, and read them as one on the group's page. Groups are one level deep: each project keeps its own
 sessions, knowledge base and hub sharing.
 
 - **Make one:** **New group** on the Projects page, or **New group…** in a project's group menu (the folder button on
@@ -157,7 +157,21 @@ sessions, knowledge base and hub sharing.
   projects; they go back to what the other groups' rules say.
 - Each group folds away, on the page and in the sidebar, and stays folded in that browser. On **Sessions**, the project
   filter lists projects under their groups, with **All of *group*** to see every session in a group. A project's page
-  shows its group in the breadcrumb.
+  shows its group in the breadcrumb, which opens the group's page.
+- **The group's page:** **Analyze** on a group's heading (or **The whole group** in the sidebar) reads its projects as
+  one big project. **By project** puts them side by side with each one's share of the group's active time, its
+  sessions, estimated cost, knowledge and when it was last worked on. Below come the project page's cards over all of
+  them, each item named by its project: **Needs you** (each folder's uncommitted and unpushed work, and the decisions
+  each project's last sessions left open), **Where you left off**, **The folders now**, each project's roadmap file,
+  the backlog and **Week by week**. **Map** draws the projects and the services and platforms they use, hand-drawn
+  like an architecture sketch: a service many lines meet (a Langfuse, a database, a cloud) is one the projects share,
+  and dashed arcs are the links the [Systems map](#systems-map) found between the projects themselves (one edits the
+  other's files, or its glossary names it). Click a part or a line to see where it was found, in manifests or in the
+  commands sessions ran, and **Excalidraw** downloads it to edit. **Knowledge bases** shows each project's own side by
+  side, with each one's architecture sketch where it has one (nothing is written for the group as a whole), and the
+  glossary terms more than one project uses first. The Knowledge, Sessions, Artifacts and Usage tabs cover every
+  project in the group; Usage adds each project's active time week by week and the group's activity calendar. As on a
+  project's page, git and roadmap files are read only when you open the page on this computer.
 
 Groups are kept in this computer's archive and never go to a hub. On a hub with people, admins see and change the
 hub's groups; someone limited to some projects sees none. On a computer that sends to a hub, a whole group can be

{interlatch-0.25.0 → interlatch-0.26.0}/docs/faq.md

@@ -20,7 +20,8 @@ Claude Desktop, Cursor, Windsurf and Gemini CLI aren't recorded, but they can us
 
 **Do I need Claude Code?** No. Analysis runs through Claude Code, Codex or IBM Bob, or a model provider's API with
 your own key: Anthropic, Amazon Bedrock, OpenAI, Azure OpenAI, OpenRouter, any OpenAI-compatible server, or Ollama on
-your own computer. Pick one in **Status › Analysis** or with `interlatch config set analysis.backend <name>`
+your own computer. Pick one when you run `interlatch install`, in **Status › Analysis**, or with
+`interlatch config set analysis.backend <name>`
 ([Model providers](analysis.md#model-providers)). Recording and browsing work either way; with none set up, sessions
 are archived and wait in the analysis queue.
 

{interlatch-0.25.0 → interlatch-0.26.0}/docs/install.md

@@ -2,7 +2,7 @@
 
 [← Interlatch](../README.md) · [Docs index](README.md)
 
-Interlatch runs on macOS and [Windows](#windows) and needs something to analyze sessions: a logged-in [Claude Code](https://claude.com/claude-code) (`claude`) or [Codex](https://github.com/openai/codex) (`codex`), IBM Bob with a Bob API key, or a model provider's API with your own key ([Model providers](analysis.md#model-providers)). Setup uses Claude Code when it is installed and offers Codex when it is not; switch any time in **Status › Analysis** or with `interlatch config set analysis.backend codex`. There are two ways to run it; both use the same data in `~/.interlatch` and can coexist.
+Interlatch runs on macOS and [Windows](#windows) and needs something to analyze sessions: a logged-in [Claude Code](https://claude.com/claude-code) (`claude`) or [Codex](https://github.com/openai/codex) (`codex`), IBM Bob with a Bob API key, or a model provider's API with your own key ([Model providers](analysis.md#model-providers)). Setup lists them all and asks which to use (Claude Code when it is installed, unless you pick another); switch any time in **Status › Analysis**, with `interlatch install --backend <name>` or with `interlatch config set analysis.backend <name>`. There are two ways to run it; both use the same data in `~/.interlatch` and can coexist.
 
 Interlatch was called Chronicle. To update from Chronicle, see [Moving from Chronicle](moving-from-chronicle.md).
 
@@ -52,8 +52,15 @@ run `uv tool install --python 3.13 .` in it.
 
 `interlatch install` (also `interlatch setup`) walks through setup:
 
-1. Checks the agent that analyzes sessions (Claude Code by default). If it is missing and Codex is installed, offers
-   to analyze with Codex instead; with neither, sessions are recorded but not analyzed until one is installed.
+1. Asks what analyzes sessions. It lists every choice with whether it is ready: Claude Code, Codex and IBM Bob
+   (through your own login and plan), and the model providers' APIs (Anthropic, Amazon Bedrock, OpenAI, Azure
+   OpenAI, OpenRouter, Ollama on this computer, any OpenAI-compatible server). Enter keeps the one marked (Claude
+   Code when it is installed). Pick one that isn't set up and it asks for what it still needs (an endpoint, an API
+   key, kept in `~/.interlatch/provider-keys.json` readable by you only, and a model, with the ones the provider
+   offers listed), then offers one small test call. Leave a question blank to go back to the list. Asked on the
+   first install only, and again while the chosen one can't run; `--backend <name>` answers without asking (and,
+   without a terminal, says which `interlatch config` commands finish setting it up). With nothing ready,
+   sessions are recorded but not analyzed until one is set up.
 2. Lists the coding agents on this Mac (Claude Code, Codex, GitHub Copilot, IBM Bob, Google Antigravity, OpenCode) and the MCP-only clients it
    finds (Claude Desktop, Cursor, Windsurf, Gemini CLI), with how many sessions each has on disk.
 3. Asks, for each one found and not yet connected, whether to record it (default yes), and whether to give each
@@ -67,8 +74,9 @@ run `uv tool install --python 3.13 .` in it.
    agents run; `--no-launchd --no-ui` turns them off. With the background sync on, it also asks once whether to
    show a desktop notification when a new version of Interlatch is out (`--notify-updates` or
    `--no-notify-updates` answers without asking).
-6. Explains analysis: each past session is read through your Claude Code (or Codex) login, which counts toward
-   your plan's usage (or through IBM Bob or the model provider you chose), and the knowledge it yields builds each
+6. Explains analysis: each past session is read through your Claude Code, Codex or IBM Bob login, which counts
+   toward your plan's usage (or through the model provider you chose, billed to your key, or Ollama on this
+   computer), and the knowledge it yields builds each
    project's knowledge base, then the **Glossary**, then the **Map**. Until sessions are analyzed, those two stay empty. It says how many sessions are waiting and how
    long the background takes over them (6 every 15 minutes), then asks whether to analyze them now with a
    progress bar per stage (sessions, knowledge bases, glossary, map themes): all of them, or the newest 20 for a

{interlatch-0.25.0 → interlatch-0.26.0}/docs/ja/dashboard.md

@@ -89,7 +89,7 @@ git の行とロードマップのファイルは、フォルダーがあるコ
 ## プロジェクトのグループ
 
 関連するプロジェクトを、Aktio のリポジトリをまとめた **Aktio** のように 1 つの見出しの下に置けます（プロジェクトページとそのサイドバー）。
-グループは 1 階層だけで、変わるのはプロジェクトの並び方だけです。各プロジェクトのセッション、ナレッジベース、ハブでの共有はそのままです。
+グループのページでは、それらを 1 つのプロジェクトとして見られます。グループは 1 階層だけで、各プロジェクトのセッション、ナレッジベース、ハブでの共有はそのままです。
 
 - **作る：** プロジェクトページの **New group**、またはプロジェクトのグループメニュー（カードのフォルダーのボタン、一覧では行の末尾）の
   **New group…**。入れるプロジェクトにチェックを付けると、それらが共有するフォルダーをフォルダーのルールとして提案し（コンピューターごとに 1 つ。
@@ -101,7 +101,19 @@ git の行とロードマップのファイルは、フォルダーがあるコ
 - グループの見出しの **Edit** で、名前、ルール、プロジェクトの変更や削除ができます。グループを削除してもプロジェクトは残り、
   ほかのグループのルールどおりの場所に戻ります。
 - グループはページでもサイドバーでも折りたため、そのブラウザーでは折りたたんだままになります。**Sessions** のプロジェクトの絞り込みでは
-  プロジェクトがグループごとに並び、**All of *グループ*** でグループのすべてのセッションを表示できます。プロジェクトのページでは、パンくずリストにグループが出ます。
+  プロジェクトがグループごとに並び、**All of *グループ*** でグループのすべてのセッションを表示できます。プロジェクトのページでは、パンくずリストにグループが出て、
+  そこからグループのページを開けます。
+- **グループのページ：** グループの見出しの **Analyze**（サイドバーでは **The whole group**）で、グループのプロジェクトを 1 つの大きなプロジェクトとして見られます。
+  **By project** ではプロジェクトを並べ、グループのアクティブ時間に占める割合、セッション数、推定費用、ナレッジ、最後に作業した日を示します。その下には
+  プロジェクトのページと同じカードがすべてのプロジェクトをまとめて並び、各項目にプロジェクト名が付きます：**Needs you**（各フォルダーのコミット・プッシュしていない作業と、
+  各プロジェクトの最近のセッションが残した判断）、**Where you left off**、**The folders now**、各プロジェクトのロードマップ、バックログ、**Week by week**。
+  **Map** では、プロジェクトと使っているサービス・プラットフォームを構成図と同じ手描き風で描きます。多くの線が集まるサービス（Langfuse、データベース、クラウドなど）は
+  プロジェクト間で共有しているもので、点線の弧は[システムマップ](#システムマップ)がプロジェクト同士の間に見つけたつながり（相手のファイルを編集した、用語集が相手の名前を挙げている）です。
+  要素や線をクリックすると、マニフェストやセッションで実行したコマンドのどこで見つかったかを表示し、**Excalidraw** で編集用にダウンロードできます。
+  **Knowledge bases** では各プロジェクトのナレッジベースを、構成図があればそれも含めて並べて表示し（グループ全体のために何かを書き起こすことはしません）、
+  複数のプロジェクトで使う用語集の用語を先に示します。Knowledge、Sessions、Artifacts、Usage のタブはグループのすべてのプロジェクトを対象にし、
+  Usage には各プロジェクトの週ごとのアクティブ時間とグループのアクティビティカレンダーが加わります。プロジェクトのページと同じく、git とロードマップのファイルは
+  このコンピューターでページを開いたときだけ読みます。
 
 グループはこのコンピューターのアーカイブに保存され、ハブには送られません。人を登録したハブでは管理者がハブのグループを見て変更でき、
 一部のプロジェクトだけを見られる人にはグループは表示されません。ハブに送っているコンピューターでは、グループ全体をハブの 1 つの

{interlatch-0.25.0 → interlatch-0.26.0}/docs/ja/party.md

@@ -14,11 +14,12 @@ Claude Code、Codex、GitHub Copilot、IBM Bob、Google Antigravity、OpenCode
 サインインしていなければ扉には鍵がかかっていて、Google でのサインインを求められ、済めばひとりでに開きます。いったん入れば、
 ページを再読み込みしても出るまで中にいます。
 
-中では、レールに Innerlatch のセクション（**パーティー**、**リーダーボード**、**アリーナ**）が並びます。
+中では、レールに Innerlatch のセクション（**パーティー**、**冒険**、**リーダーボード**、**アリーナ**）が並びます。
 レールの下の扉（**Interlatch に戻る**）でもとのページに戻り、扉は背後で閉まります。リーダーボードとアリーナが出るのは、Interlatch を動かしているコンピューターだけです。専用のハブや、
 一部のプロジェクトに限られたハブの人には出ません。
 
-パーティーのアドレスは `#/innerlatch` です。以前の `#/party` や `#/leaderboard` のリンクもそのまま使え、Innerlatch のどのアドレスもまず扉を通ります。扉のアイコンを隠すには、
+パーティーのアドレスは `#/innerlatch` です。以前の `#/party` や `#/leaderboard` のリンクもそのまま使え、Innerlatch のどのアドレスもまず扉を通ります。Innerlatch の中で教訓のリンクを押すと、教訓がページの上のウィンドウに開き、
+ロードマップのモジュールと、事例なら場面・問い・答えが出ます。**Interlatch でセッションを開く**でダッシュボードのセッションのページに移ります。扉のアイコンを隠すには、
 **設定 › 外観 › 扉**を**非表示**にします（このブラウザーだけ）。Innerlatch はアドレスから開けます。
 
 ## サインイン
@@ -55,16 +56,34 @@ Innerlatch の扉は、Google でサインインするまで開きません。
 クラスが変わったとき、あなたがクエストを完了したときです。各エージェントのレベルの推移もグラフで見られます。1 つの教訓で
 いくつものスキルが上がったときは 1 行にまとめます。加入、レベル、クラス、クエストはすべて残り、スキルアップは新しい 120 件が残ります。
 
-## パーティーのページの旅
-
-サインインすると、**パーティー**のページの上部で放置ゲームのようにパーティーが進みます。6 人のキャラクターは、今週いちばんレベルを上げた
-スキル領域に合わせたブループリントの景色を歩き、今週の教訓と戦います。教訓 1 件が 1 体のモンスターで（修正はバグの Glitch、
-落とし穴は Mal の壺、など）、その教訓を生んだセッションのエージェントが倒し、得た経験値が表示されます。1 週間をウェーブごとに
-繰り返し、実際のレベルアップの時点ではバナーが出ます。証拠の候補があるメインクエストのマイルストーンは最後にボスとして現れ、
-クエストを完了にするまで倒せません。モンスターにポインターを置くと教訓が、クリックするとセッションが開きます。右上のボタンで
-折りたためます。見えないときは止まり、アニメーションをオフにすると静止画になります（**設定 › 外観**）。
-サインインする前から、パーティーのページではサインインのカードの上に今週の教訓が灰色で並び、パーティーが眠っている間も待っています。
-ポインターを置くと教訓が、クリックするとそのセッションが開きます。
+## 冒険
+
+**冒険**は、数えられる教訓をすべて載せたワールドマップです。6 つの属性がそれぞれ地方になり（技巧は鍛冶の町、データは湖と運河、
+運用は山とサーバーの塔、守護は城壁と砦、秘術は魔法使いの塔、伝承は図書館のある古い森）、ロードマップのモジュールはその地方の
+領地になります。教訓は、いちばんよく当てはまるモジュールの領地に、種類ごとのモンスターとして立っています（修正はバグの
+Glitch、落とし穴は Mal、など）。まだ教訓が届いていない領地は霧に包まれています。パーティーはいちばん新しい教訓を学んだ場所に
+立ち、メインクエストのマイルストーンはボスとして地方の門を守ります。ドラッグで見回し、スクロールかピンチで拡大縮小し、
+ミニマップやサイドバーの地方で移動します。**リスト**では同じ遭遇を一覧にして、地方、種類、エージェントで絞り込めます。
+
+モンスターをクリックすると、ターン制の戦闘になります。その教訓を学んだエージェントが先頭に立ち、ほかに最大 2 人が加わります。
+毎ターン**たたかう**、**スキル**（教訓のロードマップのモジュールのひとつ。そのエージェントのレベルが高いほど強い）、**ぼうぎょ**、
+**にげる**から選びます。モンスターの強さは教訓の経験値と信頼の段階で決まります。勝つと遭遇はクリア済みになり、マップの旗に
+変わります（このパーティーのアーカイブに記録されます）。負けても**もう一度**でサイコロを振り直せます。戦闘でレベルや経験値が
+変わることはありません。それらは教訓からだけ得られます。ボスとも戦えますが、倒れるのは**クエスト**でそのマイルストーンを
+完了にしたときだけです。
+
+## 町と装備
+
+マップの各地方には**町**があります（冒険のサイドバーにも並びます）。町の店では、その地方のロードマップのモジュールに合わせた
+**装備**を売っています。モジュールごとに武器、防具、お守りがあり、それぞれ 3 段階です。エージェントのだれかがそのスキルで
+Lv 1 に達すると I 段階、Lv 3 で II 段階、Lv 5 で III 段階が店に並びます。買えるものは、エージェントの教訓が実際に扱っている
+範囲に沿って増えていきます。どの町でも戦闘用の**道具**（ポーション、エーテル、フェニックスの尾、煙玉）を売っています。
+
+**ゴールド**は、教訓ごとの最初の勝利で手に入ります（定着した教訓や確立した教訓ほど多く、同じ教訓では二度と手に入らず、
+ボスからは出ません）。最初の勝利では、教訓の種類に応じた**戦利品**（修正からはパッチ、判断からは ADR の巻物など）が
+落ちることもあります。道具と戦利品は戦闘の**どうぐ**コマンドで使います。エージェントはそれぞれ武器、防具、お守りの 3 つを
+身につけます。エージェントのページか**バッグ**で付け替え、バッグでは要らないものを売れます。装備で変わるのは戦闘の数値だけで、
+レベルや経験値は教訓からだけ得られます。
 
 ## アリーナ
 

{interlatch-0.25.0 → interlatch-0.26.0}/docs/party.md

@@ -14,13 +14,15 @@ the rail brings up a large door: click it to go through. Innerlatch opens only t
 out, the door is locked and asks you to sign in with Google, then opens by itself once you have. Once through, you stay
 in until you leave, even if you reload the page.
 
-Inside, the rail shows Innerlatch's sections: **Party**, **Leaderboard** and **Arena**, and the door at the bottom of
+Inside, the rail shows Innerlatch's sections: **Party**, **Adventure**, **Leaderboard** and **Arena**, and the door at the bottom of
 the rail (**Back to Interlatch**) leads back to the page you came from, and the door shuts behind you. The Leaderboard
 and the Arena show only on the computer that runs Interlatch: not on a dedicated hub, and not for hub people limited to
 some projects.
 
 The Party's address is `#/innerlatch`; old `#/party` and `#/leaderboard` links still work, and every address in
-Innerlatch meets the door first. To hide the door icon, set **Settings › Appearance › The door** to **Hidden** (this
+Innerlatch meets the door first. A lesson link anywhere in Innerlatch opens the lesson in a window over the page, with
+its roadmap modules and, for a case file, the scene, question and answer; **Open the session in Interlatch** leaves for
+the dashboard's session page. To hide the door icon, set **Settings › Appearance › The door** to **Hidden** (this
 browser only). Innerlatch still opens from its address.
 
 ## Signing in
@@ -62,17 +64,36 @@ person's review before a milestone counts.
 and when you completed a quest, with a chart of each agent's level over time. A lesson that lifted several skills at
 once is one line. Every join, level, class and quest stays on the list; of the skill-ups, the newest 120 do.
 
-## The journey on the Party page
-
-Once you're signed in, the top of the **Party** page shows your party on the move, in the style of an idle game. The six
-characters walk across a blueprint landscape that matches the skill area they levelled most this week, and fight this
-week's lessons: each lesson is a monster (a fix is Glitch the bug, a gotcha is Mal's pot, and so on), beaten by the
-agent whose session taught it, for the XP it earned. The week replays wave by wave; when it passes one of your real
-level-ups, a banner says so. Main-quest milestones with possible evidence stand at the end as bosses the party can't
-beat until you mark the quest done. Point at a monster to see its lesson, click it to open the session, and fold the
-strip away with the button in its corner. It pauses when it's out of sight, and stays still when animations are off
-(**Settings › Appearance**). Before you sign in, the Party page already shows this week's lessons in grey above the
-sign-in card, waiting while your party sleeps; point at one to see it, click it to open its session.
+## Adventure
+
+**Adventure** is a world map with every lesson that counts on it. Each of the six attributes is a region (Craft a forge
+town, Data lakes and canals, Ops mountains and server towers, Guard walls and a keep, Arcana a wizard tower, Lore an old
+forest with a library), and each roadmap module is a territory in its region. Every lesson stands in the territory of
+its best-matching module as a monster of its kind (a fix is Glitch the bug, a gotcha is Mal, and so on). Territories no
+lesson has reached yet lie under fog. Your party stands where the newest lesson was learned, and the main quest's
+milestones guard their region's gate as bosses. Drag to look around, scroll or pinch to zoom, and use the minimap or the
+sidebar's regions to jump; **List** shows the same encounters as a list you can filter by region, kind and agent.
+
+Click a monster to battle it, turn by turn: the agent that taught the lesson leads, with up to two others. Each turn
+choose **Attack**, **Skill** (one of the lesson's roadmap modules, stronger the higher that agent's level in it),
+**Defend** or **Run**; the monster's strength comes from the lesson's XP and trust stage. Win, and the encounter is
+cleared: it becomes a flag on the map, kept in your archive for this party. Lose, and **Retry** rolls new dice.
+Battles never change levels or XP: those come only from the lessons. A boss can be fought, but it only falls when you
+mark its milestone done under **Quests**.
+
+## Towns and gear
+
+Each region has a **town** on the map (also listed in the Adventure sidebar). Its shop sells **gear** for that region's
+roadmap modules: a weapon, an armor and a charm for each module, in three tiers. A piece opens in the shop when one of
+your agents reaches its level in that skill: Lv 1 for tier I, Lv 3 for tier II, Lv 5 for tier III. So what you can buy
+follows what your agents' lessons actually cover. Every town also sells **supplies** for battles: Potion, Ether,
+Phoenix Down and Smoke Bomb.
+
+**Gold** comes from the first win over each lesson (more for an established or canonical one; never again for the same
+lesson, and bosses pay none). A first win can also drop **loot** of the lesson's kind, such as a Patch from a fix or an
+ADR Scroll from a decision. Use supplies and loot from the **Item** command in a battle. Each agent wears three slots
+(weapon, armor, charm): change them on the agent's page or in the **Bag**, where you can also sell what you don't need.
+Gear only changes battle numbers: levels and XP still come from lessons alone.
 
 ## The arena
 

{interlatch-0.25.0 → interlatch-0.26.0}/src/interlatch/analysis/runners/api.py

@@ -288,14 +288,20 @@ class ApiRunner(Runner):
             return "entra" if _tool("az") else ""
         return "" if self.spec.needs_key else "none"
 
+    def missing(self) -> list[str]:
+        """What it still needs before it can run, of "endpoint", "model" and "key" (in that order)."""
+        return [what for what, have in (("endpoint", self.base_url), ("model", self._models()[0]),
+                                        ("key", self._credentials())) if not have]
+
     def unavailable_reason(self) -> str:
         from ...core.i18n import tr
 
-        if not self.base_url:
+        missing = self.missing()
+        if "endpoint" in missing:
             return tr("{label}: set its endpoint (providers.{name}.base_url)", label=self.label, name=self.name)
-        if not self._models()[0]:
+        if "model" in missing:
             return tr("{label}: choose a model (providers.{name}.model)", label=self.label, name=self.name)
-        if not self._credentials():
+        if "key" in missing:
             return tr("{label}: add an API key", label=self.label)
         return ""
 

{interlatch-0.25.0 → interlatch-0.26.0}/src/interlatch/analysis/runners/base.py

@@ -144,5 +144,11 @@ class Runner:
         res.data = data
         return res
 
+    def check(self) -> LLMResult:
+        """One small call with the main model: do the endpoint, the key and the model work? Raises LLMError."""
+        return self.run('Reply with {"ok": true}.', {"type": "object", "properties": {"ok": {"type": "boolean"}},
+                                                     "required": ["ok"]},
+                        system="You check that a connection works.", effort="low", timeout=120)
+
 
 CLAUDE_MODEL = re.compile(r"^(claude|sonnet|opus|haiku|fable)", re.I)

{interlatch-0.25.0 → interlatch-0.26.0}/src/interlatch/artifacts/queries.py

@@ -55,17 +55,20 @@ def status_of(row: dict, local_machine: str | None = None) -> str:
     return "present" if _HASHES[key] == row["sha256"] else "changed"
 
 
-def query(conn, *, kind: str | None = None, project: str | None = None, agent: str | None = None, q: str | None = None,
-          session_id: str | None = None, local_machine: str | None = None) -> tuple[list[dict], dict[str, int]]:
+def query(conn, *, kind: str | None = None, project: str | list[str] | None = None, agent: str | None = None,
+          q: str | None = None, session_id: str | None = None,
+          local_machine: str | None = None) -> tuple[list[dict], dict[str, int]]:
     """Artifacts newest first, with where each stands now, and the count of each kind (before the kind filter).
-    Across sessions the same file, link or commit is one item (its latest version) that knows how many sessions made it."""
+    Across sessions the same file, link or commit is one item (its latest version) that knows how many sessions made it.
+    project: one project's path, or a group's paths (a list)."""
     where, params = [], []
     if session_id:
         where.append("a.session_id = ?")
         params.append(session_id)
     if project:
-        where.append("s.project_path = ?")
-        params.append(project)
+        paths = [project] if isinstance(project, str) else project
+        where.append(f"s.project_path IN ({','.join('?' * len(paths))})")
+        params += paths
     if agent:
         where.append("s.agent = ?")
         params.append(agent)

{interlatch-0.25.0 → interlatch-0.26.0}/src/interlatch/core/i18n/ja.py

@@ -356,6 +356,29 @@ JA: dict[str, str] = {
     "sign in to see your party": "パーティーを見るにはサインインしてください",
     "no such quest": "そのクエストはありません",
     "no such track": "そのトラックはありません",
+    "no such lesson": "その教訓はありません",
+    # ---- the Town & gear (bag.py)
+    "no such item": "その道具はありません",
+    "this isn't sold here": "これはここでは売っていません",
+    "this is still locked: the party's skill in its module isn't high enough yet":
+        "まだロックされています。そのモジュールでのパーティーのスキルがまだ足りません",
+    "not enough gold": "ゴールドが足りません",
+    "you can carry at most 99 of each item": "同じ道具は 99 個までしか持てません",
+    "the number must be a whole number from 1 to 99": "数は 1 から 99 までの整数にしてください",
+    "you don't have that": "それを持っていません",
+    "you don't have that many": "そんなに持っていません",
+    "take it off before selling it": "売る前に装備を外してください",
+    "no such agent": "そのエージェントはいません",
+    "no such slot": "その装備欄はありません",
+    "that doesn't go in this slot": "それはこの装備欄には付けられません",
+    "only consumables and loot can be used": "使えるのは消耗品と戦利品だけです",
+    "none left": "もう残っていません",
+    "{tier} {noun} of {module}": "{tier}の{noun}（{module}）",
+    "+{atk} attack, and +{skill} to the {module} skill, in battle only": "攻撃 +{atk}、{module} のスキル +{skill}（戦闘中のみ）",
+    "+{hp} HP, and {cut}% less damage taken, in battle only": "HP +{hp}、受けるダメージ {cut}% 減（戦闘中のみ）",
+    "+{mp} MP, and +{skill} to the {module} skill, in battle only": "MP +{mp}、{module} のスキル +{skill}（戦闘中のみ）",
+    "Lv {level} in {module}": "{module} で Lv {level}",
+    "{name} town": "{name}の町",
     "this computer is not a hub": "このコンピューターはハブではありません",
     "Could not sign in": "サインインできませんでした",
     "Ask an admin of this hub for a new invite, or open the hub's dashboard again from your own Interlatch "