@kukonce/dsh-loomy 0.0.0-stage → 0.3.2

package/CHANGELOG.md

@@ -0,0 +1,125 @@
+# Changelog
+
+## 0.3.2 — 2026-11-14
+
+版本号发布：README 加了积分胶囊的效果图（docs/pill-composer.png），代码与 0.3.1 完全一致。
+
+## 0.3.1 — 2026-11-13
+
+> 发布：npm `@kukonce/dsh-loomy@0.3.1`（`dsh plugin add @kukonce/dsh-loomy`）。
+
+### Fixed — the pill now tracks what chat actually spends
+
+The pill read the grant ledger, which freezes the daily pot at claim time (5000 at
+the 00:00-style boot claim) and never moves while the user chats — so after a
+morning of conversations it still said 5000 when the real remaining was, say, 4521.
+The settings card was never wrong because its 刷新积分 button reads the server live.
+
+- The gateway's final accounting frame carries `points_consumed`; the adapter now
+  books it into a per-day, per-account spend file (`usage.json`, 0600) the moment
+  the frame arrives — including a mid-stream abort, since the gateway bills what
+  it already sent. `/state` projects the claim's balance minus today's recorded
+  spend, clamped so a stale spend file can never show a negative pot.
+- Every live server read is now a sync point, not just a display: the panel's
+  刷新积分 button, `/loomy status` and `/loomy credits` re-anchor the ledger to what
+  the server answered and forget the recorded spend (which that answer already
+  includes). Each claim — boot, midnight, manual — does the same, so any drift
+  (points spent outside this process) self-corrects within a day.
+- The anchor records the local day key, matching `grantedToday` and the projection's
+  day match; the server's `dailyCycleDate` can roll minutes off local midnight.
+
+### Changed — the pill now says 每日赠送积分
+
+The pill's label (and the popover title) used the generic 「积分」; it now uses the
+official client's copy, 「每日赠送积分」 ("Daily gift points" in English), which is
+what the number actually is.
+
+## 0.3.0 — 2026-11-13
+
+### Added — a points pill beside the model picker
+
+When the conversation is pointed at a Loomy model, a small pill now sits to the right
+of the composer (the same spot `dsh-connect-modelscope-token-plan` uses): a traffic-light
+dot, the daily balance left over all signed-in accounts, and whether today's 5000 has
+been claimed. Clicking it opens a per-account breakdown — daily / quota and available
+balance for each account — plus the read time.
+
+- The pill mounts only while the selected model's provider is `@loomy/dsh-loomy/*`;
+  switching to any other provider unmounts it, and an unmounted pill makes no requests.
+- It polls the panel's `/state` every 30 seconds. That endpoint reads local ledgers only
+  — no upstream call — so the pill is free; a live balance refresh still lives on the
+  settings card's 刷新积分 button. After three silent cycles the pill marks its numbers
+  stale instead of silently keeping them.
+- Read failures keep the last reading on screen (marked stale) rather than blanking the
+  pill; "—" means nothing has been read yet, which is a different fact from 0.
+- The pill carries its own stylesheet and `--lo-*` custom properties: the settings card's
+  `<style>` does not reach the conversation screen.
+
+## 0.2.0 — 2026-11-13
+
+### Fixed — the desktop import no longer reaches across local users
+
+On Windows the Loomy desktop client keeps its session in
+`C:\Users\Public\Loomy\<sha256(username)[:12]>\userData\auth-session.json`. That is
+inside `C:\Users\Public`, a directory every local account shares, and 0.1.0 walked all
+of `C:\Users\Public\Loomy\*` and adopted the most recently updated session. On a machine
+with more than one user, that can be somebody else's account.
+
+- Only this user's own directory is read: the hash derived from the current username, plus
+  the per-user Electron default under `%APPDATA%`. Nothing enumerates the shared root.
+- A directory may still be named explicitly (`/loomy import <directory>`); that is a
+  decision the user makes, not a guess the plugin makes.
+- The import no longer runs by itself on first start. `/loomy import` and the panel
+  button do the same work on request; a fresh install with no account just says how to
+  sign in. (Silent adoption of a desktop login was the other half of the same problem.)
+- `docs/verify/live-check.mjs` probes the same narrowed locations, so a verification run
+  cannot quietly depend on a session the plugin itself would refuse to read.
+
+The daily credit claim is unchanged: it still runs at startup and at local midnight, and
+only ever for accounts the user signed in.
+
+## 0.1.0 — 2026-11-11
+
+First release.
+
+### Accounts
+
+- SMS login through iFlytek CAccount (HMAC-SHA1 signed requests).
+- Adopt the login the Loomy desktop app already has, by reading its `auth-session.json`
+  (Windows relocates it to `C:\Users\Public\Loomy\<sha256(username)[:12]>\userData\`, so
+  the directory is discovered rather than guessed).
+- Multiple accounts; each becomes its own provider route `@loomy/dsh-loomy/<id>`.
+- A dead session is recorded and surfaced as "登录已失效" instead of failing silently.
+
+### Credits
+
+- Reads the two pots separately: 每日赠送 (daily, 5000/day) and 长期 (permanent).
+- Renews the daily pot through `POST /api/v1/points/first-login` — the call the official
+  client makes on login, which resets the per-`dailyCycleDate` quota idempotently. Runs at
+  startup and at local midnight.
+- Onboarding tasks (a separate one-time 10,000-point pool) are listed but **never** claimed
+  automatically, because that is a resource the user may want to spend deliberately.
+
+### Models
+
+- Live per-account catalog from `GET /api/v1/models`.
+- Generation models (`type: image`) are listed but excluded from the chat picker: they share
+  the chat URL and answer 404 to it.
+- Reasoning levels come from the catalog, falling back to the standard five when a model
+  declares none (`auto` does) — an incomplete set makes the harness reject the model
+  outright with `UNSUPPORTED_REASONING_EFFORT`.
+
+### Streaming
+
+- OpenAI-compatible SSE with `content`, `reasoning_content` and `tool_calls`.
+- Usage accounting from `stream_options.include_usage`.
+- Tool-call arguments are buffered and only announced once a tool name has arrived, so a
+  truncated call never reaches the transcript as a parse error.
+
+### Known behaviour
+
+- History reasoning is **not** replayed except for the newest assistant turn. Replaying it
+  made long sessions slow rather than coherent: a 100-turn conversation carried a 245 kB
+  body and took 61 s per turn, against 8 s with the current rule.
+- Intermittent `502 Bad Gateway` from `loomyad.xunfei.cn` under load is upstream and is
+  reported as a retryable `SERVER` failure.

package/LICENSE

@@ -0,0 +1,26 @@
+MIT License
+
+Copyright (c) 2026 dsh-loomy contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+Note: the icon.png and icon-mask.png placeholder artwork is generated work and
+carries this same license. The Loomy and iFlytek names and logos are the property
+of their respective owners; this plugin is an unofficial integration and is not
+affiliated with or endorsed by iFlytek.

package/README.md

@@ -1,3 +1,224 @@
-# Temporary Holding Version
+# dsh-loomy
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+把 [Loomy](https://loomy.xunfei.cn)（讯飞 Loomy 桌面端）的账号接入 DeepSeek Harness，作为
+模型提供方使用。
+
+一个 Loomy 账号在 DSH 里长成一条独立的模型路由：
+
+```
+@loomy/dsh-loomy/loomy      ← 第一个账号
+@loomy/dsh-loomy/<id>       ← 每个账号一条
+```
+
+![选择 Loomy 模型时，输入框右侧会显示积分胶囊](docs/pill-composer.png)
+
+> 选中 Loomy 模型后，输入框右下角出现积分胶囊：绿点表示当日额度还有余量，
+> 显示「每日赠送积分 · 剩余 / 总额 · 可用合计 · 今日已领」，随对话实时扣减，
+> 点击可看每个账号的明细。
+
+## 快速安装
+
+```sh
+dsh plugin --profile desktop add @kukonce/dsh-loomy
+```
+
+（npm 安装；也可以用 `dsh plugin --profile desktop add github:kukonce/dsh-loomy` 走 GitHub 源码。）
+
+装完重启 DSH。第一次启动会自动尝试导入本机 Loomy 桌面端的登录态；没有的话用
+`/loomy login <手机号>` 或设置面板里的「Loomy」分区登录。
+
+登录用手机短信验证码，或者直接复用本机 Loomy 桌面端已有的登录态 —— **不需要 API Key**，
+Loomy 本身就没有 API Key 这种东西。账号的「每日赠送 5000 积分」由插件在启动时和每天
+本地零点自动刷新。
+
+---
+
+## 装到 DSH 里
+
+插件放在 `~/.dsh/local-plugins/dsh-loomy`，然后在某个 profile 里登记两处：
+
+**1. `~/.dsh/profiles/<profile>/package.json`** —— 加依赖和 bundle：
+
+```jsonc
+{
+  "dependencies": {
+    "@kukonce/dsh-loomy": "file:C:/Users/<you>/.dsh/local-plugins/dsh-loomy"
+  },
+  "dsh": {
+    "profile": {
+      "bundles": [
+        // …原有条目…
+        "@kukonce/dsh-loomy"
+      ]
+    }
+  }
+}
+```
+
+**2. 装依赖**（用 DSH 自带的 pnpm，在 profile 目录里跑）：
+
+```powershell
+cd ~/.dsh/profiles/<profile>
+node <dsh>/dsh-runtimes/dsh-primary-runtime/dependencies/pnpm/bin/pnpm.mjs install --ignore-scripts
+```
+
+然后**重启 DSH**。新增的 bundle 是在启动时加载的，热重载不会把一条新的 bundle 拉进来。
+
+装好之后：设置里多一个「Loomy」分区，命令里多一个 `/loomy`。
+
+---
+
+## 登录
+
+插件**不会**自己去导入桌面端登录 —— 导入是一个决定，不是安装的副作用。
+
+原因很实在：Windows 上 Loomy 把登录态放在 `C:\Users\Public\Loomy\<sha256(用户名)[:12]>\userData\`，
+而 `C:\Users\Public` 是全机共享目录。如果插件去扫 `C:\Users\Public\Loomy\*`，它拿到的「最近更新的
+那份」很可能就是这台机器上**别人**的登录态。所以导入只会发生在你明确要求的时候，并且默认只读当前
+用户自己那个哈希目录。
+
+三种方式，等价：
+
+```
+/loomy import [目录]           导入 Loomy 桌面端已有的登录（只读本用户目录）
+/loomy login 13800138000      发送短信验证码
+/loomy login code 123456      用验证码换 session
+```
+
+也可以在「设置 → Loomy」里点。
+
+登录态存在 `~/.dsh/dsh-loomy/accounts.json`，目录权限 0700、文件 0600。**它是明文的** ——
+Loomy 的 session 本身就是一个不加密的 bearer 串，没有任何一层能把它变成不可读；能读你用户目录
+的进程就能读它。介意的话退出登录即可（`/loomy logout`）。
+
+---
+
+## 每日 5000 积分是怎么回事
+
+Loomy 的积分分两个池子：
+
+| 池子 | 额度 | 来源 |
+|---|---|---|
+| 每日赠送（daily） | 5000 / 天 | 每日重置，优先消耗 |
+| 长期 / 永久（permanent） | 不固定 | 注册奖励、新手任务、兑换码 |
+
+**让每日池回到 5000 的是 `POST /api/v1/points/first-login`**，不是「读一下余额」。它名字叫
+"首次登录"，实际行为是「开始今天的计费周期」：同一个 `dailyCycleDate` 内重复调用是幂等的
+（返回 `alreadyProcessed: true`），所以随便调都是免费的。
+
+插件在三个时机调它：
+
+1. **启动** 之后约 12 秒（等其它插件先安静下来）；
+2. **每天本地零点**，`msUntilNextMidnight()` 算出来的那一刻；
+3. **面板刷新**时 —— 顺带当余额读取用，因为它是唯一一个一次返回四个数字加今日消耗的接口。
+
+本地留一本账 `daily-grant.json` 记住「今天领过没有」，避免重启后又问一遍；面板上的按钮强制重来。
+
+> **注意**：这里没有任何「假装已领取」的逻辑。能不能真的拿到 5000 由服务端判定，插件只是把
+> 官方客户端的那个调用照做了一遍。
+
+---
+
+## 模型
+
+目录是**按账号实时拉的**（`GET /api/v1/models`），不是写死的表 —— 你的账号能用哪些模型，
+选择器里就只有哪些。这台机器上当前是 9 个（见 [docs/models.md](docs/models.md)）。
+
+目录里有 3 个模型（`Hy-Image-3.5-preview`、`doubao-seedream-5-lite`、`qwen-image-3.0-pro`）的
+`type` 是 `image` —— 它们的地址和对话接口相同，但对对话请求一律返回 **404「该模型暂未开放」**
+（2026-11-11 实测）。所以**模型选择器里不会出现它们**：能被选中的只有真正能回答对话的 6 个。
+`/loomy models` 会把它们列出来并标 `[不支持对话]`，免得你以为是插件漏了。
+
+```
+/loomy models     列出当前账号的模型、能力和上下文长度
+```
+
+---
+
+## 命令
+
+```
+/loomy status                 账号、积分、模型数量一览
+/loomy login <手机号>          发验证码
+/loomy login code <验证码>     验证码换 session
+/loomy import [目录]          导入桌面端登录（只读本用户目录；目录可选）
+/loomy logout [id]            退出（账号 id 省略时取第一个）
+/loomy models [id]            当前账号的模型目录
+/loomy credits [id]           积分明细（每日/长期/今日消耗）
+/loomy claim [id]             立刻领取今日赠送额度
+/loomy tasks [id]             新手任务进度（一次性 10000 积分池）
+/loomy claimtask <任务名>      完成一个新手任务并领取
+```
+
+新手任务奖励**不会自动领** —— 那是每个账号只有一份的长期积分，什么时候花应该由你决定。
+
+---
+
+## 为什么这样做
+
+### 为什么要发两个认证头
+
+同一个 host 上的两组接口读不同的头，而且失败时返回的是 **HTTP 200 + 错误码**，不是 401：
+
+- `/api/v1/models`、`/points/*` 这些读 `token: <session>`；
+- `/api/v1/chat/completions` 读 `Authorization: Bearer <session>`（方案名大小写敏感）。
+
+所以插件两边都发。注意错误信息 `缺少 token` 容易误导 —— 它说的是「缺 Authorization」，
+不是「缺 token」。完整矩阵见 [docs/protocol.md](docs/protocol.md)。
+
+### 为什么要垫高 max_tokens
+
+这些是推理模型，**思考过程和正文共用同一个 `max_tokens` 预算**。实测给 200 tokens 时，
+预算全被思考吃掉，正文为空、`finish_reason: length` —— 用户看到的是「模型没回答」，
+实际是被截断了。所以适配器给 `max_tokens` 兜了个 1024 的下限。
+
+### 为什么每个账号一条路由
+
+模型目录和积分余额都是按账号算的，而模型选择器是按 provider 分组的。两个账号挤一条路由，
+在界面上就变成「一个账号，模型列表一直在变」。
+
+---
+
+## 已知限制和风险
+
+- **这是非官方集成。** 没有公开 API，所有接口都是照官方桌面客户端的行为逆出来的，随时可能变。
+- **账号风险和合规。** 用插件调用等同于用 Loomy 客户端调用，但自动化流量可能触发风控。请自己判断
+  是否符合你账号的协议条款。
+- **会话认证。** session 是 bearer 串，没有 refresh 接口。失效了只能重新登录（错误码 `100002`）。
+  插件会把它标成「登录已失效」并提示重登，不会假装还能用。
+- **生图模型不提供。** 目录里有 3 个 `type: image` 的生图模型，它们不接受对话请求，插件既不会
+  在选择器里提供它们，也没有实现生图调用 —— 这里只做对话。
+- **点数由服务端计费。** 插件不预测也不拦截消耗；余额以服务端返回为准。
+- **单机单用户。** 账号表、日志、缓存都在 `~/.dsh/dsh-loomy/` 下，没有多用户隔离。
+
+---
+
+## 文件都在哪
+
+```
+~/.dsh/dsh-loomy/
+  accounts.json       账号表（含 session，明文，0600）
+  catalog.json        模型目录缓存（目录接口挂了时兜底）
+  daily-grant.json    每日领取账本
+  expired.json        哪些账号的 session 被判失效
+```
+
+整个目录删掉 = 插件回到初始状态。
+
+---
+
+## 协议细节
+
+- [docs/protocol.md](docs/protocol.md) —— 主机、认证头矩阵、信封格式、SSE 事件、错误表、未知项
+- [docs/models.md](docs/models.md) —— 模型目录快照
+- [docs/verify/live-check.mjs](docs/verify/live-check.mjs) —— 可重跑的协议自检（47 项）
+
+```powershell
+node ~/.dsh/local-plugins/dsh-loomy/docs/verify/live-check.mjs
+```
+
+---
+
+## 许可证
+
+MIT。图标是占位图。Loomy / 讯飞 的名称和标识归各自所有者，本项目与讯飞无隶属关系。