@stofone/dsh-agent-roster 0.13.0 → 0.13.1

package/CHANGELOG.md

@@ -4,6 +4,18 @@
 
 ## [Unreleased]
 
+## [0.13.1] - 2026-11-03
+
+### The local rosters are the front page
+
+0.13.0 opened on the library tab. That got the metaphor right and the priority wrong: the rosters you
+already manage are what you come back to every day, and they were one tab away. The panel now lands on
+**Rosters** — local, searchable, with its tag pool — and the library marketplace is the second tab.
+
+- Tab order is `Rosters, Library, Teams, Sources, Health`; the default tab is `rosters` again.
+- Nothing moved between the two: both read the same snapshot, both filter by tag, and the tag pools stay
+  independent (local-only vs everything in view) so neither one silently changes the other's counts.
+
 ## [0.13.0] - 2026-11-03
 
 ### A tab that behaves like a marketplace, not a filter on a list
@@ -615,6 +627,7 @@ point is now one search field above the tabs.
   且所有返回值先过 `lib/json.js#lossless`。
 
 [Unreleased]: https://github.com/dsh-agent-roster/dsh-agent-roster/compare/v0.12.0...main
+[0.13.1]: https://github.com/dsh-agent-roster/dsh-agent-roster/compare/v0.13.0...v0.13.1
 [0.13.0]: https://github.com/dsh-agent-roster/dsh-agent-roster/compare/v0.12.0...v0.13.0
 [0.12.0]: https://github.com/dsh-agent-roster/dsh-agent-roster/compare/v0.11.1...v0.12.0
 [0.11.1]: https://github.com/dsh-agent-roster/dsh-agent-roster/compare/v0.11.0...v0.11.1

package/README.md

@@ -308,8 +308,9 @@ turns into decoration.
 
 ## The library tab: find by capability, not by source
 
-The panel opens on **Library**, which is meant to read like a plugin marketplace: one search field, one row
-of tags, and one list that spans this machine and every subscribed source.
+The panel opens on **Rosters** — the local ones: what you work with every day, its tags and members, ready
+to filter or edit. The second tab is the **Library**, meant to read like a plugin marketplace: one search
+field, one row of tags, and one list that spans this machine and every subscribed source.
 
 ```
 要找什么能力？例：数据质量、发版、代码评审

package/README.zh.md

@@ -294,7 +294,8 @@ node bin/cli.mjs compile --roster examples-orchestration/rosters/core-review \
 
 ## 档案库：按能力找，而不是按来源翻
 
-面板的第一个页签是**档案库**，定位接近一个插件市场：一个搜索框、一排标签、一份横跨本机与所有订阅来源的清单。
+面板的**首屏是本机档案**（第一个页签）：你每天打交道的那些档案、它们的标签与成员，进来就能看见、能筛选、能改。
+第二个页签是**档案库**，定位接近一个插件市场：一个搜索框、一排标签、一份横跨本机与所有订阅来源的清单。
 
 ```
 要找什么能力？例：数据质量、发版、代码评审
@@ -373,8 +374,8 @@ node bin/cli.mjs compile --roster examples-orchestration/rosters/core-review \
 
 | 页签 | 能做什么 |
 |---|---|
+| 档案 | 浏览每个工作区 × 每座档案库，展开成员；**新建 / 编辑 / 复制 / 删除 / 导入 / 导出**档案。编辑器有表单与源码两种模式（源码就是文件原文）；写之前由宿主校验，覆盖已有文件会留一份 `.bak`；顶上有搜索框与标签池 |
 | 档案库 | 按能力找档案：搜索（横跨本机与订阅来源，命中给出处）、标签筛选、按来源聚合或平铺，行内直接打开或拉取 |
-| 档案 | 浏览每个工作区 × 每座档案库，展开成员；**新建 / 编辑 / 复制 / 删除 / 导入 / 导出**档案。编辑器有表单与源码两种模式（源码就是文件原文）；写之前由宿主校验，覆盖已有文件会留一份 `.bak` |
 | 团队 | 读一个配置好的状态目录（默认 `.agent-teams`），列出运行时真正建出来的每个团队：档案、成员档案与模型路由、每个持久化成员是否真的与其档案一致，以及该团队的任务 |
 | 档案源 | 列出订阅的公共 registry 目录，每个 collection 一个「拉取到本机」按钮；可展开先看里面有哪些档案 |
 | 体检 | 把「配置有没有指错」集中一处：目录解析到了哪、状态目录在不在、有多少声明未被确认，以及该改哪个设置 |

package/client.js

@@ -1556,7 +1556,7 @@ window.__ModuleLoader__.load({
     function Panel() {
       useTranslation();
       const library = useLibrary();
-      const [tab, setTab] = useState("catalog");
+      const [tab, setTab] = useState("rosters");
       const [query, setQuery] = useState("");
       const [selectedTags, setSelectedTags] = useState(() => new Set());
       const [settingsOpen, setSettingsOpen] = useState(false);
@@ -1713,8 +1713,8 @@ window.__ModuleLoader__.load({
         "div",
         { className: "rstr-tabs", role: "tablist" },
         [
-          ["catalog", t("panel.tabsCatalog"), null],
           ["rosters", t("panel.tabsRosters"), rosters.length],
+          ["catalog", t("panel.tabsCatalog"), null],
           ["teams", t("panel.tabsTeams"), teams.length],
           ["sources", t("panel.tabsSources"), snapshot?.remote?.collections?.length ?? 0],
           // 只有真正要用户处理的问题才计数：info 只是说明，不该在页签上挂数字。

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@stofone/dsh-agent-roster",
-  "version": "0.13.0",
+  "version": "0.13.1",
   "description": "多 Agent 团队的静态成员档案定义与校验层：档案库在面板里看得见、改得动，团队成员的人设、模型与工具边界固化成可校验、可版本化的文件，并在 dsh-agent-teams 创建成员时把档案桥接给运行时。",
   "type": "module",
   "main": "index.js",