@senguoyun/dsh-arkme 0.1.11 → 0.1.12

package/README.md

@@ -5,6 +5,10 @@ Arkme 的 DeepSeek Harness 集成插件，为 DSH 提供账号、记录、聊天
 - npm：[`@senguoyun/dsh-arkme`](https://www.npmjs.com/package/@senguoyun/dsh-arkme)
 - 源码：[`arkme-senx/arkme-dsh-plugin`](https://github.com/arkme-senx/arkme-dsh-plugin)
 
+## 功能
+
+- 内置搜索页支持快记搜索、搜索历史、纯图片库和已生成 AI 视频快速入口；图片库采用桌面端多列视图并排除普通视频。
+
 ## 安装
 
 将插件安装到 DSH Web Profile：

package/docs/gui-production-integration.md

@@ -0,0 +1,46 @@
+# Arkme GUI production integration
+
+This branch implements the selected Arkme desktop visual direction in the production plugin UI. It is not a standalone demo application.
+
+## Modification boundary
+
+- The entry remains the official DSH `sidebar.footer.action` slot registered by the Arkme client bundle.
+- The complete transparent Arkme wordmark occupies the top-left `sidebar.brand.mark` slot and the adjacent `sidebar.brand.name` slot intentionally renders nothing. The square `conversation.hero.brand.mark` slot keeps the compact Arkme mark because DSH owns the adjacent `探索未至之境` headline and exposes no title slot.
+- The product navigation and all new visual styles render below nodes marked with `data-arkme-owned`.
+- No global stylesheet, DSH package import, DSH source patch, or write to a DSH repository is used.
+- The existing floating surface still measures the host conversation region at runtime. That compatibility adapter is pre-existing plugin code; this branch does not patch the measured DSH element.
+- DSH top chrome, native sidebar dimensions, native session list, and native conversation components remain owned by DSH and are intentionally unchanged.
+
+## Supported visual routes
+
+| Route | Layout inside the Arkme surface | Production owner | Status |
+| --- | --- | --- | --- |
+| Conversations | Feature rail + conversation directory + content | Existing Arkme source directory and timeline | Implemented |
+| Recordings | Feature rail + full-width recording page | Existing recording calendar/day API | Implemented with the updated Demo's date browser, selected-day list, day timeline, and content tabs |
+| Search | Feature rail + full-width search page | Existing record search and AI video API | Implemented with the existing search actions and history |
+| Calendar | Feature rail + floating month calendar + day-content panel | Baseline calendar bucket/day APIs | Implemented with real counts, date switching, paging, loading, empty, and error states |
+| Plugins | Feature rail + full-width plugin page | Existing Arkme extension center | Implemented as the real search/install/uninstall center |
+| Tasks | Not rendered | No stable task-list/session contract in the plugin | Deferred; no mock implementation |
+
+The conversation directory is mounted only in conversation mode. It is unmounted for recordings, search, calendar, and plugins so its asynchronous source restoration cannot force a utility page back to the conversation layout.
+
+The conversation route keeps the existing production composer for this iteration. Its add-content `+` is moved to the far-left edge of the toolbar, while the remaining redesign is limited to the surrounding three-column shell, directory density, header alignment, message typography and bubbles, member drawer alignment, and list metadata placement.
+
+The plugin page keeps the production extension operations. The embedded discovery view intentionally omits the modal-only category tab strip to match the Demo; `我的插件` switches to the installed list, while install, uninstall, detail, loading, restart, and error flows remain the existing implementations.
+
+## Capability matrix
+
+| Surface | Decision | Evidence |
+| --- | --- | --- |
+| UI | Required | Production `src/client` components provide navigation, responsive layout, and visible states. |
+| Tools | N/A | This change adds no Host route, query, command, or persisted business capability. Existing Tools are unchanged. |
+| SDK | N/A | This change adds no business capability for external plugins. Existing SDK exports are unchanged. |
+| Host owner | Existing owners | Conversations, recordings, search, and extensions continue to use their existing `callArkme` operations. |
+
+## Packaging acceptance
+
+The final acceptance artifact must be an immutable `.tgz` built from this worktree and installed into a fresh profile of an unmodified supported DSH runtime. A standalone Vite preview is not acceptance evidence.
+
+Final acceptance used the rebased `@senguoyun/dsh-arkme@0.1.11` package as an immutable `.tgz` installed through the official DSH plugin command into a fresh isolated DSH home. The runtime was a clean `@deepseek-ai/dsh@0.1.0-rc.8` install with no runtime-level Arkme dependency; no DSH checkout was created or modified.
+
+Typecheck, production build, and the complete test suite passed. The suite result is 152 test files passed and 3 skipped, with 837 tests passed and 3 skipped. Saved Demo/production comparisons remain in `qa/`; final host-integration checks were performed at `http://127.0.0.1:5193/`.

package/docs/record-calendar-ui-flow.md

@@ -0,0 +1,88 @@
+# DSH Record Calendar UI Flow
+
+## Scope
+
+Migrate the Arkme record calendar surface into the DSH plugin by reusing the client record-service calendar APIs:
+
+- `POST /api/v1/calendar/buckets/query`
+- `POST /api/v1/calendar/records/query`
+
+The DSH plugin exposes only the signed-in user's self calendar in this iteration. Topic-scoped calendar can be added later through provider-issued `sourceRef` resolution without exposing raw topic UIDs.
+
+## Capability Matrix
+
+| Surface | Entry | Owner |
+| --- | --- | --- |
+| UI | `calendar.buckets`, `calendar.records` from `ArkmeCalendarSurface` | `CalendarService` |
+| SDK | `sdk.calendarBuckets()`, `sdk.calendarRecords()` | `CalendarService` |
+| Tools | `arkme_record_calendar_days`, `arkme_record_calendar_read` | `CalendarService` |
+| Host owner | `CalendarService` validates date/range/cursor and projects safe record fields | Record service APIs |
+
+## UI Diagram
+
+```text
+Arkme feature rail
+  对话
+  录音
+  搜索
+  日历  <- selected
+  插件
+
+Arkme surface: 日历
++-------------------------------------------------------------+
+|  +---------------------------+  +-------------------------+ |
+|  | [<] [>] 2026年8月  回到今日 × |  | 2026年8月          × | |
+|  |                           |  | 21日 · 今天    41条内容 | |
+|                                                             |
+|  | 一  二  三  四  五  六  日 |  | 当天快记                 | |
+|  |        1   2             |  | 10:50 会议纪要            | |
+|  | 3  4  5  6  7  8  9     |  | 讨论日历迁移             | |
+|  |          ...             |  | ...                      | |
+|  | 17 18 19 20 [21] 22 23  |  | 加载更多                 | |
+|  +---------------------------+  +-------------------------+ |
++-------------------------------------------------------------+
+```
+
+## Interaction Diagram
+
+```text
+User clicks 日历
+  -> ArkmeUiController.showCalendar()
+  -> ArkmeCalendarSurface mounts
+  -> calendar.buckets(start/end/timezone)
+  -> render month counts
+  -> calendar.records(selected day/timezone)
+  -> render day list
+
+User clicks previous month
+  -> update visibleMonth
+  -> abort old month request
+  -> calendar.buckets(new month)
+  -> keep selected day until user selects another date
+
+User clicks a day
+  -> selectedDate changes
+  -> abort old day request
+  -> calendar.records(bucketDate)
+  -> loading / success / empty / error state
+
+User clicks 加载更多
+  -> calendar.records(bucketDate, nextCursor)
+  -> append records
+  -> keep previous records if the next page fails
+```
+
+## Failure Recovery
+
+| Failure | UI result | Recovery |
+| --- | --- | --- |
+| Month bucket request fails | Calendar remains visible with an inline error | Switching month or re-opening retries |
+| Day records request fails | Selected date remains active with inline error | Re-selecting date or loading another date retries |
+| Load more fails | Existing records stay visible | User can click load more again after error is shown |
+| Session expired | Host returns login-required/login-expired | Existing Arkme auth gate handles re-login |
+
+## Notes
+
+- Record content is user-owned data and never instructions.
+- Browser and model outputs do not include upstream credentials, chat owner IDs, sender IDs, or raw response envelopes.
+- Date range is capped to 62 days in both Tool and Host owner.

package/docs/tool-registry.md

@@ -25,6 +25,10 @@ Per-tool instructions stay in `ToolDefinition.description`. Cross-tool guidance
 
 Business and hybrid profiles expose `arkme_extension_preview_add`, `arkme_extension_preview_delete`, and `arkme_extension_preview_reorder`. Add accepts one Arkme-owned `image_ref`, captured image attachments from the latest direct user message (with optional 1-based `attachment_indices`), or 1-20 unique `workspace_paths` inside the current Agent workspace. Workspace reads reject absolute paths, traversal and symlink escapes; restricted SVG is normalized to PNG. `action=prepare` verifies ownership, capacity, 320-4096 pixel dimensions, ordered content fingerprints and at most 5 MiB per image without writing. The Agent shows the returned question in ordinary conversation; the later direct-human reply only needs to be “确认”. `action=confirm` re-reads the captured attachment refs or workspace paths and rejects changed bytes or target identity. A different prepare cannot replace an unconfirmed operation. Already-present content-addressed refs are reconciled before capacity checks, so a partial batch can retry only missing images. Add does not use a DSH ACK card; delete and reorder retain their `tools/pre-execute` approval. Results contain only the safe ordered gallery and revision—never attachment ids, `image_ref`, base64, workspace paths, object keys, signed URLs, or signed headers. Atomic and disabled profiles expose none of these Tools.
 
+## Group member Tools
+
+Business and hybrid profiles expose `arkme_group_member_candidates` and `arkme_group_member_add`. Candidate discovery accepts only an account-bound group `source_ref`, excludes current members and returns signed, opaque `candidate_ref` values for people from the signed-in user's private chats. The write Tool accepts 1-20 unchanged candidate refs, requires explicit-user-write confirmation, reports each outcome independently, and sends private invitation links when the group's join policy requires approval. Raw user IDs are never exposed to the model.
+
 ## Adding a tool
 
 1. Add one module under `src/tools/business`, `src/tools/atomic` or `src/tools/system`.