@nite07/dsh-search 0.1.4 → 0.1.11

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/docs/BACKENDS.md CHANGED
@@ -305,7 +305,55 @@ Facts that shape the design:
305
305
  - The tweet shape moved too: the body is `details.full_text` (long posts still use `note_tweet`), the timestamp is `details.created_at_ms`, and engagement counts sit under `counts`. Fields are located structurally rather than by a fixed path, because X moves them between releases.
306
306
  - Both modes surface credentials only as field names in error messages; tokens, cookies and upstream response bodies never appear in output.
307
307
 
308
- The behaviour contract for both modes is covered by unit tests with mocked fetch. **Neither mode has been exercised against the live service**: no bearer token and no X cookies were supplied. The `session` parsing paths that depend on X's current layout are listed as assumptions in the port notes.
308
+ The behaviour contract for both modes is covered by unit tests with mocked fetch. When this section was written **neither mode had been exercised against the live service**, because no bearer token and no X cookies were supplied; `session` mode was then verified live the same day, further down this file, and the parsing paths that depend on X's current layout remain assumptions in the port notes. `key` mode still has no live call.
309
+
310
+ ## Xiaohongshu (added 2026-11-17)
311
+
312
+ Xiaohongshu publishes no callable search API: notes and comments only exist inside its own page runtime, and its internal endpoints refuse a plain in-page fetch, so a read has to go through the site's own HTTP client inside a signed-in page. The backend therefore drives a browser the user hosts, and has exactly one access mode.
313
+
314
+ | Access mode | Credential | Transport | Cost |
315
+ | --- | --- | --- | --- |
316
+ | `browser` (default, and the only one) | `DSH_SEARCH_BROWSER_TOKEN` — the bearer token the browser container prints at startup | Patchright over a Playwright WebSocket endpoint, evaluating scripts in a signed-in Xiaohongshu page | No vendor fee and no published quota; the browser and its machine are the cost |
317
+
318
+ Facts that shape the design:
319
+
320
+ - **The browser is a shared resource, not a backend.** The `browser` config block holds the endpoint, the session file and the read timeout, and every backend in `browser` mode attaches to it, so one container can serve several. A backend's own `endpoint` is a fallback used only while the shared one is empty. The endpoint token is resolved under the fixed name `DSH_SEARCH_BROWSER_TOKEN` for the same reason: it guards the endpoint, not a site account, so it is never a per-backend credential.
321
+ - **Sign-in is not the plugin's.** The container keeps one window open on its display; a person signs in over VNC and the keeper client writes `/profile/state.json` every minute. Reads start from that file, so a restart resumes signed in. Nothing here can log in, and no site credential leaves the container.
322
+ - **Reads are capped.** Search takes 1–40 notes per call with `sort` of `general`, `time_descending` or `popularity_descending`; one call returns citeable sources, one per note. A note read takes either a share link or a note id. Comments are cursor-paged, 1–100 per page (the `xiaohongshu_note` tool asks for 20 by default and never above 50).
323
+ - **The per-note token is load-bearing.** Search results carry an `xsecToken` that detail and comment reads require, but a `Source` must not expose it, so nothing would remember it by default. The adapter keeps it in-process (bounded to 500 notes) and also accepts the `xsec_token` embedded in a share link. A read with neither fails as a configuration error naming both ways to get one, rather than returning an empty note.
324
+ - **Failures are classified, not swallowed.** A page answer saying login is required, or HTTP 401/406, is reported as `authentication` with the action "sign in over VNC"; 403 is `authentication` naming privacy or missing permission; 429 is `rate-limit`; page-runtime codes (`NOT_READY`, `NO_RUNTIME`, `NO_CLIENT`, `NO_REGISTRATION`, `BAD_CLIENT`) are `protocol` with the action "open xiaohongshu.com in that browser once".
325
+ - **Version lock between both ends.** Patchright is a direct dependency of the core and pins its own Playwright protocol version; a browser container built against a different major.minor refuses the connection with `428 Precondition Required`. The image ships the matching version, so upgrade both together.
326
+ - **Reachability.** Plaintext `ws://` endpoints are accepted on loopback and on private or tailnet ranges, because a self-hosted browser is normally reached over a LAN or a tailnet rather than from the same host.
327
+
328
+ ### Shared browser settings
329
+
330
+ | Config field | Meaning |
331
+ | --- | --- |
332
+ | `browser.endpoint` | The Playwright endpoint every browser-mode backend attaches to, for example `ws://127.0.0.1:3000/ws`. When set it wins over a backend's own endpoint. |
333
+ | `browser.statePath` | Where the signed-in session is read from; empty uses the core's default, `~/.config/dsh-search/browser/state.json`, which has to be the file the container's `/profile` volume is mounted at. |
334
+ | `browser.timeoutMs` | How long one browser read may take. |
335
+
336
+ The endpoint token is stored once for the browser — in the settings page under **Shared browser**, or by `search_manage` with `scope: browser` — and the snapshot reports the endpoint and whether a token is configured, so the page can say which of the two a read actually uses.
337
+
338
+ ### Browser container (`image/`)
339
+
340
+ `@nite07/search-core` ships the container in its own `image/` directory, and nothing inside it knows which site is being read:
341
+
342
+ | Piece | Why it is there |
343
+ | --- | --- |
344
+ | Patchright + Google Chrome | A Playwright fork that closes the CDP leaks detection looks for, driving the browser its authors recommend |
345
+ | Token proxy on `:3000` | The Playwright server has no authentication beyond an unguessable path; the proxy requires `Authorization: Bearer <token>` and forwards only authorised upgrades |
346
+ | Xvfb + x11vnc + noVNC on `:6080` | One window a person can reach on a headless host, for the single sign-in |
347
+ | Keeper client | Keeps a client attached so the window stays open, and writes the session to disk every minute |
348
+ | `/profile` volume | Holds `state.json` and the endpoint token; the core reads the same file to start signed in |
349
+
350
+ A compose file and an `env.example` sit next to the image sources: the endpoint port, the noVNC port and its password, the endpoint token (generated on first start when empty) and the start URL are all environment values. Without compose it is one `podman build` and one `podman run` with the same ports, volume and `--shm-size=1gb`.
351
+
352
+ ### Verification status for Xiaohongshu (2026-11-17, live)
353
+
354
+ Search, note detail and comment reads were all executed against a signed-in session. Three defects only a live session could expose were found and fixed: the proxy forwarded `Origin` and `Host` unchanged so a reachable endpoint answered 403; a page script used a leftover placeholder instead of a string helper and threw past the health probe; and the per-note token was not remembered, so a note found by search could not be opened afterwards. Unit tests cover the read paths with an injected browser.
355
+
356
+ Re-verified in this deployment on 2026-11-18 through the shared browser: search, note detail and comments each answered in 2.5–3.2 s, and the deployment wiring (container, endpoint, session file, stored token) is recorded in [VERIFICATION.md](VERIFICATION.md).
309
357
 
310
358
  ## Outbound identity
311
359
 
@@ -4,10 +4,11 @@ Date: 2026-11-17 (Asia/Shanghai), profile `web`. The DSH release running at that
4
4
 
5
5
  ## Automated
6
6
 
7
- `npm run check` (typecheck + 28 tests + build) passes. Coverage highlights:
7
+ `npm run check` (typecheck + 21 tests + build) passes. Coverage highlights:
8
8
 
9
- - Config validation: unknown fields, ranges, enumerations, non-loopback `http`, credentials in URLs, unverified backends cannot be enabled.
9
+ - Config validation: unknown fields, ranges, enumerations, endpoint schemes (`http(s)` or `ws(s)`, no credentials, query or fragment), unverified backends cannot be enabled.
10
10
  - Fixed access modes: anonymous mode never resolves or transmits a stored key; key mode without a credential fails without any request; no fallback path exists in the engine.
11
+ - Fixed credential names: credential destinations are defined in code, never editable configuration. Legacy name fields are discarded on load, and management requests cannot override the destination with a reference. The shared browser exposes one token input without storage-name controls or explanations. Stored secrets are never echoed back.
11
12
  - Retry: only allowlisted statuses; bounded attempts on the same endpoint; `Retry-After` honoured and never shortened; `401`/quota-exhaustion bodies are not retried and never surface in results.
12
13
  - Failure reporting: partial failures and total failure appear in returned content with backend, mode, kind and attempt count; failed backends are not cached.
13
14
  - Deduplication, domain filtering, local budget accounting (durable domain, serialized reservations, fail-closed on storage errors), cancellation.
@@ -31,14 +32,14 @@ Executed through the plugin engine and through DSH `web_search` after `searchPro
31
32
 
32
33
  ## Verified, not live
33
34
 
34
- Keyed backends (Tavily, Brave, DeepSeek, Zhihu, Baidu, Doubao, Linkup, Serper, Serpex, OpenAI, Anthropic, Mojeek, Tencent) are request/response-tested against documented contracts only. No credential was supplied, so no live keyed call, billing check, or account-quota observation exists. Serper remains unverified and disable-able.
35
+ Keyed backends (Tavily, Brave, DeepSeek, Zhihu, Baidu, Doubao, Linkup, Serpex, OpenAI, Anthropic, Mojeek, Tencent) are request/response-tested against documented contracts only. No credential was supplied, so no live keyed call, billing check, or account-quota observation exists. Serper was retired from the catalogue on 2026-11-17 ([BACKENDS.md](BACKENDS.md#retired-entries)), so it is no longer a candidate here. X `key` mode has no live call either; its `session` mode was verified live the same day, as recorded in [BACKENDS.md](BACKENDS.md#x-session-search-verification-2026-11-17-live).
35
36
 
36
37
  ## Deployed state
37
38
 
38
39
  - Bundle `@nite07/dsh-search` installed by Plugin Manager from the linked worktree; Host fiber active; Settings entry `nite-search` active in the live slot tree.
39
40
  - `searchProvider: nite-search`, `fetchProvider: http`.
40
41
  - Old bundle `@240xu/dsh-websearch` disabled, not removed (rollback: enable it and restore `searchProvider: unified`).
41
- - Enabled backends: Keenable, Exa, You.com (anonymous) and local SearXNG. Everything else disabled.
42
+ - Enabled backends, as read from the live profile configuration: Keenable, AnySearch, Exa, Parallel, You.com, SearXNG and Reddit (all anonymous), X (`session`) and Xiaohongshu (`browser`). Everything else disabled. Live results for several of them are recorded below; [BACKENDS.md](BACKENDS.md) carries its own live table for 2026-11-17.
42
43
 
43
44
  ## Not verified
44
45
 
@@ -50,7 +51,9 @@ Keyed backends (Tavily, Brave, DeepSeek, Zhihu, Baidu, Doubao, Linkup, Serper, S
50
51
 
51
52
  Applied P0+P1 fixes: conditional field visibility (single-backend selector only in single mode; retry/breaker/cache/diagnostics dependants follow their switch; anonymous mode hides the credential surface; unverified backends are read-only), a pre-flight blocker banner (no backend enabled / single mode pointing at a disabled backend / key mode without a stored credential), structured trial-search results with failure reasons, diagnostics with time, reason and message, backend search/filter/count toolbar, collapsed-card cost chips and credential dot, nested advanced options, sticky save bar, inline confirmations instead of `window.confirm`, range-aware field errors, and a checkbox group for retry statuses.
52
53
 
53
- `npm run check` now covers 31 tests, including `visible()` and `blockersOf()` semantics (hidden values are preserved, not reset). Rebuilt and reloaded via one authorized `dsh-web` restart; `web_search` still answers through `nite-search` afterwards and the settings entry stays registered.
54
+ `npm run check` then covered 31 tests, including `visible()` and `blockersOf()` semantics (hidden values are preserved, not reset). Rebuilt and reloaded via one authorized `dsh-web` restart; `web_search` still answers through `nite-search` afterwards and the settings entry stays registered.
55
+
56
+ That 31 is history: the engine's tests moved into `@nite07/search-core` when the plugin stopped embedding it (commit `25fc123`), which is why this repository now runs 21 and core runs 109.
54
57
 
55
58
  Still unverified after this pass: the rendered page itself. The automation browser is rejected by the deployment edge (`ERR_INVALID_AUTH_CREDENTIALS`) for both the token URL and `/connect`, so there is no screenshot or manual keyboard pass. Visual, light/dark and focus behaviour rest on code review only.
56
59
 
@@ -82,3 +85,33 @@ Anonymous mode was exercised against the real endpoints, with retry and cache di
82
85
  | `fetchRedditThread` on the first permalink | post title resolved, 13 top-level comments parsed, `truncated: true` at the 4,000-character test budget |
83
86
 
84
87
  This confirms the anonymous token flow (Android client id + device headers), the persisted-operation hashes for `SearchPosts` and `PostComments`, the `/by_id` metadata call, and the comment tree shaping. The `oauth` mode is contract-tested only: no client id/secret was supplied, so no live OAuth call was made. Assumptions that remain unverified are listed in the port notes: the OAuth Listing field shapes, and whether the anonymous path keeps working if Reddit closes `/by_id` to those tokens.
88
+
89
+ ## Xiaohongshu and the shared browser (2026-11-18, live)
90
+
91
+ ### Deployment
92
+
93
+ - Container `systemd-search-browser`, image `localhost/search-browser:latest`, unit source `~/pod/search-browser/search-browser.container`, copy in `~/.config/containers/systemd/`.
94
+ - Publishes `3030 → 3000` (the Playwright endpoint, path `/ws`) and `6080` (noVNC); volume `~/pod/search-browser/data:/profile`; `BROWSER_WS_TOKEN` is set in the unit, so the proxy takes the token from the environment and never reads the volume's `ws-token` file.
95
+ - Live configuration: `browser.endpoint: ws://127.0.0.1:3030/ws`, `browser.timeoutMs: 60000`, `browser.statePath` empty, Xiaohongshu enabled in `browser` mode.
96
+ - An empty `statePath` resolves to the core default `~/.config/dsh-search/browser/state.json`, and `~/.config/dsh-search/browser` is a symlink to `~/pod/search-browser/data`, so the core reads the exact `state.json` the container writes. Without that link the default path is a different file and every read starts signed out.
97
+ - The stored credential `DSH_SEARCH_BROWSER_TOKEN` was compared against the container's `BROWSER_WS_TOKEN` by hash, not by eye, and matches. It is the same token the container prints.
98
+
99
+ ### Reads
100
+
101
+ Executed through `@nite07/search-core` directly against that endpoint and session — the same code path the tool runs, without the tool wrapper:
102
+
103
+ | Call | Result |
104
+ | --- | --- |
105
+ | `searchXhs` "机械键盘", 3 results | 3 sources in 3.17 s, each with a working `xiaohongshu.com/explore/<id>` link |
106
+ | `fetchXhsNote` on the first source | title, author, 934 likes, 8 tags, one picture and the full description, 2.53 s |
107
+ | `fetchXhsComments` on the same note, limit 5 | 5 comments with author, likes, reply count and IP location, `hasMore: true`, 2.52 s |
108
+
109
+ The note read used only the id the search returned, so the in-process note-token cache is what made it work.
110
+
111
+ One failure was reproduced deliberately: a token that differs from the container's answers `authentication` naming the endpoint ("rejected the token") before any page is opened. That is the same message the earlier stale `ws-token` file produced, which is worth knowing: when `BROWSER_WS_TOKEN` is set, the file in the volume is dead weight, and the token to paste into the settings is the one the container prints.
112
+
113
+ ### Not verified this pass
114
+
115
+ - A `xiaohongshu_note` call through the DSH tool surface: the backend-enabled check, the credential lookup from the store, the picture download into the scratch directory and the rendered block.
116
+ - The **Shared browser** section of the settings page in a real browser; it rests on code review and unit tests.
117
+ - Anything on the site beyond these reads. No search result was clicked, nothing was liked, no note-level action was taken.
package/locale/en.json CHANGED
@@ -61,7 +61,7 @@
61
61
  "credentialTitle": "Credential storage",
62
62
  "credentialConfigured": "Credential configured",
63
63
  "credentialMissing": "No credential configured",
64
- "credentialHelp": "Secrets are write-only and are never returned to this page. Some references are read-only.",
64
+ "credentialHelp": "Saved credentials are never displayed.",
65
65
  "credentialValue": "New credential value",
66
66
  "replaceCredential": "Replace credential",
67
67
  "deleteCredential": "Delete credential",
@@ -187,8 +187,6 @@
187
187
  "help.backend.mode": "Choose a fixed anonymous or key mode. No automatic switching.",
188
188
  "field.backend.endpoint": "Endpoint URL",
189
189
  "help.backend.endpoint": "Use a trusted HTTPS endpoint, or a trusted local self-hosted endpoint. Never put secrets in the URL.",
190
- "field.backend.credentialRef": "Credential reference",
191
- "help.backend.credentialRef": "Reference only, not the secret value. Save this reference before managing its credential.",
192
190
  "field.backend.timeoutMs": "Request timeout (ms)",
193
191
  "help.backend.timeoutMs": "Deadline for each backend request.",
194
192
  "field.backend.rateLimitPerMinute": "Attempts per minute",
@@ -223,12 +221,32 @@
223
221
  "choice.session": "Browser session cookies",
224
222
  "colorLegend": "Green: free path, own account or self-hosted. Yellow: free allowance. Red: trial credits or paid. Sorted cheapest first.",
225
223
  "credentialPending": "Wait for the current action to finish.",
226
- "credentialRefRequired": "Set a credential reference name first.",
227
- "credentialReadOnly": "This reference is read-only: another source supplies its value, so the plugin cannot overwrite it. Pick a different reference name, such as DSH_SEARCH_X_SESSION.",
224
+ "credentialReadOnly": "This credential is provided by another source and cannot be changed here.",
228
225
  "credentialPlainKey": "Paste the key itself.",
229
226
  "credentialShapeLabel": "Credential format",
230
227
  "field.tools.webSearchPlus": "Allow web_search_plus",
231
228
  "help.tools.webSearchPlus": "Off hides the tool entirely: the agent then searches only through the configured strategy.",
232
229
  "field.tools.compactByDefault": "Compact results by default",
233
- "help.tools.compactByDefault": "Sources carry only URL, title and date. Saves context when the agent only needs links; a call can still ask for full snippets."
230
+ "help.tools.compactByDefault": "Sources carry only URL, title and date. Saves context when the agent only needs links; a call can still ask for full snippets.",
231
+ "choice.browser": "Browser",
232
+ "field.browser.endpoint": "Shared browser endpoint",
233
+ "field.browser.statePath": "Shared session file",
234
+ "field.browser.timeoutMs": "Browser read timeout (ms)",
235
+ "field.browser.maxConcurrentReads": "Per-site concurrent reads",
236
+ "help.browser.endpoint": "The Playwright endpoint every browser-backed reader shares, for example ws://<host>:3000/ws. When set it wins over a backend's own endpoint; leave it empty to let each backend name its own.",
237
+ "help.browser.statePath": "Optional. Where the browser container writes the signed-in session; empty uses the search core default.",
238
+ "help.browser.timeoutMs": "How long one browser read may take.",
239
+ "help.browser.maxConcurrentReads": "How many browser reads may run at once on one site. This differs from “Parallel concurrency” under “Search behavior”: that setting bounds search requests across providers, while this bounds reads on the one shared browser page. A 429 rate-limit answer lowers it to 1 for the rest of that browser session; it is a local safety bound, not a site quota.",
240
+ "sharedBrowser": "Shared browser",
241
+ "sharedBrowserHint": "This block describes the browser container you host: its endpoint, its endpoint token, the session file, the read timeout and the per-site read cap. Every backend in browser mode shares it.",
242
+ "browserTokenTitle": "Endpoint token",
243
+ "browserTokenValue": "New endpoint token",
244
+ "saveToken": "Save token",
245
+ "browserTokenHelp": "Used to connect to the browser service. Sign in to Xiaohongshu through VNC.",
246
+ "browserInheritedEndpoint": "This backend inherits the shared endpoint: {{endpoint}}",
247
+ "browserInheritedEndpointMissing": "This backend has no endpoint to connect to: the shared browser settings are empty and it names none of its own.",
248
+ "browserOwnEndpoint": "The shared browser endpoint is empty, so this backend uses its own endpoint: {{endpoint}}.",
249
+ "browserInheritedHint": "The endpoint and the token both come from the shared browser settings, so they are changed in one place.",
250
+ "browserOverride": "Give this backend its own endpoint (fallback only)",
251
+ "browserOverrideHint": "Applies only while the shared browser settings are empty. Use it to point one backend at a different browser container."
234
252
  }
package/locale/zh.json CHANGED
@@ -61,7 +61,7 @@
61
61
  "credentialTitle": "凭证存储",
62
62
  "credentialConfigured": "已配置凭证",
63
63
  "credentialMissing": "未配置凭证",
64
- "credentialHelp": "凭证仅可写入,不会回显。部分凭证引用只允许读取。",
64
+ "credentialHelp": "凭证保存后不会回显。",
65
65
  "credentialValue": "新的凭证值",
66
66
  "replaceCredential": "替换凭证",
67
67
  "deleteCredential": "删除凭证",
@@ -187,8 +187,6 @@
187
187
  "help.backend.mode": "固定使用匿名或密钥模式,不自动切换。",
188
188
  "field.backend.endpoint": "端点 URL",
189
189
  "help.backend.endpoint": "仅使用可信的 HTTPS 或本地自托管端点,不要在 URL 中填写密钥。",
190
- "field.backend.credentialRef": "凭证引用",
191
- "help.backend.credentialRef": "填写引用而非密钥本身。请先保存引用,再管理对应的凭证。",
192
190
  "field.backend.timeoutMs": "请求超时(毫秒)",
193
191
  "help.backend.timeoutMs": "每次后端请求的时间上限。",
194
192
  "field.backend.rateLimitPerMinute": "每分钟尝试上限",
@@ -223,12 +221,32 @@
223
221
  "choice.session": "浏览器会话 Cookie",
224
222
  "colorLegend": "绿色=免费/自带账号/自托管,黄色=免费额度,红色=试用或付费。由便宜到贵排序。",
225
223
  "credentialPending": "当前操作还没结束,稍等。",
226
- "credentialRefRequired": "请先填一个凭证引用名。",
227
- "credentialReadOnly": "这个凭证引用是只读的:它的值由其它来源提供,插件无法覆盖。换一个引用名试试,例如 DSH_SEARCH_X_SESSION。",
224
+ "credentialReadOnly": "该凭证由其他来源提供,无法在此修改。",
228
225
  "credentialPlainKey": "直接填密钥字符串。",
229
226
  "credentialShapeLabel": "凭证格式",
230
227
  "field.tools.webSearchPlus": "允许使用 web_search_plus",
231
228
  "help.tools.webSearchPlus": "关闭后这个工具不会注册,agent 只能用配置里的固定策略搜索。",
232
229
  "field.tools.compactByDefault": "默认返回精简结果",
233
- "help.tools.compactByDefault": "结果只保留链接、标题和日期。agent 只需要链接时能省下大量上下文;单次调用仍可要求完整摘要。"
230
+ "help.tools.compactByDefault": "结果只保留链接、标题和日期。agent 只需要链接时能省下大量上下文;单次调用仍可要求完整摘要。",
231
+ "choice.browser": "浏览器",
232
+ "field.browser.endpoint": "共享浏览器端点",
233
+ "field.browser.statePath": "共享会话文件",
234
+ "field.browser.timeoutMs": "浏览器读取超时(毫秒)",
235
+ "field.browser.maxConcurrentReads": "同站点并发读取数",
236
+ "help.browser.endpoint": "所有依赖浏览器的后端共用的 Playwright 端点,例如 ws://<主机>:3000/ws。填写后优先于各后端自己的端点;留空则各后端各用自己的。",
237
+ "help.browser.statePath": "可选。浏览器容器把登录态写在哪个文件;留空则用搜索核心的默认位置。",
238
+ "help.browser.timeoutMs": "一次浏览器读取最多等多久。",
239
+ "help.browser.maxConcurrentReads": "同一个站点上最多同时跑几个浏览器读取。它与“搜索行为”中的“并行数量”作用不同:后者限制的是同时请求多少个搜索后端,这里限制的是共享浏览器页面上的读取。遇到 429 限流后,本次浏览器会话会保守降到 1;这是本地安全上限,不代表网站额度。",
240
+ "sharedBrowser": "共享浏览器",
241
+ "sharedBrowserHint": "这里描述你自己托管的浏览器容器:端点、端点令牌、登录态文件、读取超时与同站点并发读取数。所有处于浏览器模式的后端都共用这一份配置。",
242
+ "browserTokenTitle": "端点令牌",
243
+ "browserTokenValue": "新的端点令牌",
244
+ "saveToken": "保存令牌",
245
+ "browserTokenHelp": "用于连接浏览器服务。小红书账号请在 VNC 中登录。",
246
+ "browserInheritedEndpoint": "该后端继承共享端点:{{endpoint}}",
247
+ "browserInheritedEndpointMissing": "该后端没有可连接的端点:共享浏览器配置为空,它自己也没有填写。",
248
+ "browserOwnEndpoint": "共享浏览器端点尚未填写,该后端目前使用自己的端点:{{endpoint}}。",
249
+ "browserInheritedHint": "端点与令牌都来自共享浏览器配置,需要修改时只改那一处。",
250
+ "browserOverride": "为该后端单独指定端点(仅作兜底)",
251
+ "browserOverrideHint": "只有共享浏览器配置留空时这里才会生效,用于把单个后端指向另一个浏览器容器。"
234
252
  }
package/package.json CHANGED
@@ -1,15 +1,16 @@
1
1
  {
2
2
  "name": "@nite07/dsh-search",
3
- "version": "0.1.4",
3
+ "version": "0.1.11",
4
4
  "description": "Explicit-mode multi-backend search with transparent costs and complete Web settings for DSH",
5
5
  "license": "MIT",
6
6
  "repository": {
7
7
  "type": "git",
8
- "url": "git+https://git.nite07.com/nite/dsh-search.git"
8
+ "url": "git+https://git.nite07.com/nite/search.git",
9
+ "directory": "packages/dsh-search"
9
10
  },
10
- "homepage": "https://git.nite07.com/nite/dsh-search",
11
+ "homepage": "https://git.nite07.com/nite/search/src/branch/main/packages/dsh-search",
11
12
  "bugs": {
12
- "url": "https://git.nite07.com/nite/dsh-search/issues"
13
+ "url": "https://git.nite07.com/nite/search/issues"
13
14
  },
14
15
  "keywords": [
15
16
  "dsh",
@@ -47,22 +48,38 @@
47
48
  "engines": {
48
49
  "node": ">=22"
49
50
  },
51
+ "dependencies": {
52
+ "@nite07/search-core": "0.1.6"
53
+ },
50
54
  "peerDependencies": {
51
55
  "@deepseek-ai/cordis": "*",
52
- "@deepseek-ai/schemastery": "*",
53
- "@deepseek-ai/dsh-web": "*",
54
- "@deepseek-ai/dsh-credentials": "*",
55
56
  "@deepseek-ai/dsh-config-editor": "*",
57
+ "@deepseek-ai/dsh-credentials": "*",
56
58
  "@deepseek-ai/dsh-storage-domain": "*",
59
+ "@deepseek-ai/dsh-web": "*",
60
+ "@deepseek-ai/schemastery": "*",
57
61
  "zod": "*"
58
62
  },
59
63
  "devDependencies": {
60
- "typescript": "^7.0.2",
61
- "esbuild": "^0.28.2",
62
- "tsx": "^4.20.0",
64
+ "@deepseek-ai/cordis": "4.1.0",
65
+ "@deepseek-ai/cordis-plugin-group": "1.1.0",
66
+ "@deepseek-ai/cordis-plugin-include": "1.1.0",
67
+ "@deepseek-ai/cordis-plugin-loader": "1.1.0",
68
+ "@deepseek-ai/dsh-app-boot": "0.2.2-rc.4",
69
+ "@deepseek-ai/dsh-config-editor": "0.2.2-rc.4",
70
+ "@deepseek-ai/dsh-credentials": "0.2.2-rc.4",
71
+ "@deepseek-ai/dsh-home-paths": "0.2.2-rc.4",
72
+ "@deepseek-ai/dsh-launch-environment": "0.2.2-rc.4",
73
+ "@deepseek-ai/dsh-storage": "0.2.2-rc.4",
74
+ "@deepseek-ai/dsh-storage-domain": "0.2.2-rc.4",
75
+ "@deepseek-ai/dsh-web": "0.2.2-rc.4",
76
+ "@deepseek-ai/schemastery": "3.19.0",
63
77
  "@types/node": "^24.0.0",
64
78
  "@types/react": "^19.3.0",
65
- "@nite07/search-core": "0.1.0"
79
+ "esbuild": "^0.28.2",
80
+ "tsx": "^4.20.0",
81
+ "typescript": "^7.0.2",
82
+ "zod": "4.6.6"
66
83
  },
67
84
  "dsh": {
68
85
  "bundle": {