@senguoyun/dsh-arkme 0.1.42 → 0.1.44

package/docs/avatar-diagnostics.md

@@ -0,0 +1,36 @@
+# 头像失败诊断日志
+
+诊断标记：`[ArkmeAvatarDiag]`。仅追加失败日志，不修改头像展示、缓存、并发限制或重试策略。
+需要发布包含本改动的插件后才生效；不自动修改本机已安装包。
+
+## 下次复现时
+
+先保留日志、记录发生时间和目标用户，再重启客户端，避免丢失故障现场。
+macOS 生产版日志位于 `~/Library/Application Support/Arkme Harness/`：
+
+- `logs/desktop-startup.log`：Browser 头像加载失败，由桌面壳捕获 renderer console。
+- `logs/harness.log`：Host 资料请求、头像引用和图片读取失败。
+- 账号隔离实例的 Host 日志可能位于 `dsh-containers/<scope>/logs/harness.log`，具体以启动日志中的实例路径为准。
+
+先筛选 `[ArkmeAvatarDiag]`，再按发生时间、`viewerUserId` 和 `targetUserId` / `referenceTargetUserId` 对账。
+例如 1D3E 的目标用户 ID 是 `21698`。批量资料失败的目标位于 `targetUserIds`。
+
+| event | 含义 |
+| --- | --- |
+| `profile_fetch_failed` | 批量资料请求失败，尚未生成头像引用 |
+| `profile_missing` | 成功响应漏掉了请求的用户资料 |
+| `profile_avatar_rejected` | 非空头像值被地址安全校验拒绝 |
+| `private_avatar_seal_failed` | 私聊头像引用生成失败 |
+| `image_read_failed` | Host 最终无法读取用户头像 |
+| `image_load_failed` | Browser 头像共享缓存收到加载失败 |
+
+`trigger=load` 表示普通加载，`revalidate` 表示重验证；不代表新增重试。
+`hasCachedImage=false` 表示这次失败没有旧图片可保留，可能显示默认头像。
+`durationMillis` 包含排队时间。`httpStatus` 是 Host 错误状态，`upstreamStatus`（存在时）是底层服务或图片下载的 HTTP 状态。
+引用中的 `referenceViewerUserId` / `referenceTargetUserId` 只是解析出的诊断提示，不参与授权校验。
+
+日志以单行 JSON 输出，避免桌面桥接把字段变成 `[object Object]`。不记录原始头像引用、签名 URL、图片内容、昵称、token、错误全文或堆栈。
+正常图片加载、未设置头像及合法 phone_avatar 默认头像不记录错误；共享并发读取只记一次，旧账号请求在切换后的预期取消不记 Browser 错误。
+
+已确认的恢复慢机制仍保持原样：首次加载失败后，相同引用的普通渲染不触发重试；周期维护约 10–12 分钟。
+本次日志用于确认真实复现的首次失败阶段，不预先认定为超时或鉴权问题。

package/docs/consumer-plugin-contract.md

@@ -77,6 +77,23 @@ if ((await arkme.capabilities()).features.extensionPreviews === true && userConf
 
 The SDK communicates only with the same-origin Provider route. Consumers must not read OS credential-store entries, SQLite files, state files, or tokens directly.
 
+## Team capability
+
+`capabilities().features.teamDirectory`, `teamMembers`, and `teamGovernance` advertise the complete Team contract. Consumers call `listTeams()` or `resolveTeams()` to obtain an opaque, account-scoped `teamRef`, then pass that reference unchanged to `listTeamMembers()`. A display name or public Jotmo ID must never be substituted for `teamRef`; member `userRef` and Team `teamRef` are distinct reference types and are not interchangeable.
+
+`createTeams()` requires one stable idempotency key per item. `joinTeamsByJotmoID()` accepts only the exact public Team Jotmo ID and reports whether the current account is the owner, was already a member, or joined now. Both mutations must originate from a current same-origin human UI action. Consumers must not receive, persist, or reconstruct the managed OpenAPI credential, backend numeric IDs, owner request IDs, or internal cursors.
+
+Member identity is an enrichment owned outside Team membership. `identityState=unavailable` or `incomplete` keeps the authoritative membership row visible while telling the Consumer not to invent a display identity. A member may include a Host-resolved `avatarRef` or `avatarFallback`; avatar enrichment failure never removes the authoritative membership row. Consumers discard Team pages and cursors on account change, propagate `AbortSignal`, and retry from a fresh list after an authorization or lifecycle error.
+
+| Capability | Built-in UI | Browser SDK | DSH model Tool | Shared owner |
+| --- | --- | --- | --- | --- |
+| List/resolve my Teams | Contacts → Team directory | `listTeams()`, `resolveTeams()` | `list_my_teams`, `resolve_my_teams` | OpenAPI Team capability registry → Team query owner |
+| List Team members | Team detail with loading, partial identity, pagination and retry states | `listTeamMembers()` | `list_team_members` | OpenAPI Team capability registry → Team membership owner + public identity batch reader |
+| Create Team | No built-in entry | `createTeams()` from a confirmed same-origin UI | `create_teams` after explicit user intent | OpenAPI Team capability registry → existing Team create command |
+| Join by public ID | No built-in entry | `joinTeamsByJotmoID()` from a confirmed same-origin UI | `join_teams_by_jotmo_id` after explicit user intent | OpenAPI Team capability registry → existing Team join command |
+
+The built-in UI and Browser SDK enter through the same injected `TeamServicePort`; model Tools use the OpenAPI MCP projection of the same capability definitions. REST and MCP therefore share one authorization, validation, idempotency, cursor, error, and result contract without routing model traffic through the browser Host.
+
 `capabilities().features.myExtensions` advertises the current-account extension inventory. `myExtensions()` merges only Host-approved live Cordis, Profile-resolved and cloud-owned facts; consumers must use its states and `publish` result without rescanning Profile files or inferring ownership from names. Every publishable item carries one Host-derived route: `dynamic-cordis-v2` means `artifactContractVersion=2` and `artifactKind=dsh-bundle-tgz` for a live current-session Dynamic Cordis Package; `profile-native-v3` means `artifactContractVersion=3` and `artifactKind=dsh-native-package-tgz` for an installed or Profile-local DSH Bundle. Callers pass `ownedRef` unchanged and never choose a mode themselves. A GitHub repository URL is optional provenance metadata, not a third upload route, publication credential or cloud clone/build request. A third-party registry/Git dependency appears only when its actually resolved package declares `dsh.bundle.patch`; it is a V3 publication candidate rather than an assertion that the current account authored the upstream code. `publisher_role` is server-owned: explicit values win, while historical rows without a role resolve to importer only when they have GitHub provenance. Consumers never submit this role. `ownedRef` is short-lived and account-bound. `publishMyExtension()` requires a current explicit human request and can publish only the exact Cordis Package, resolved Bundle directory or local Bundle tgz behind that ref; consumers must refresh the list after expiry or account switch. Profile paths, Agent IDs, source archives, artifact upload requests and signing material never enter this contract.
 
 Plugin update discovery and acknowledgement are lifecycle concerns owned by the bundled Arkme UI. They are intentionally absent from the public Browser SDK, Host `arkmeData` service and model tool catalog. Consumers must not invoke raw `plugin.update.*` operations or attempt to mutate a DSH profile.
@@ -129,7 +146,7 @@ Interaction flow:
 点击微信 -> 显示 Flutter AppBridge OAuth 缺失说明，不发起伪请求
 ```
 
-`readImage(avatarRef)` resolves an opaque image reference returned by `profile()` or `listSources()`. Private chats expose one optional `avatarRef`. Groups expose the preferred additive `groupAvatar` presentation plus legacy `avatarRefs`: `groupAvatar.slots` preserves the server-selected order for up to five members, including safe phone-default or generic fallbacks when a real image is absent, while legacy `avatarRefs` contains only resolvable real images. `memberCount`, `strategy`, and `computedAtMillis` describe the snapshot without exposing member or session identities. The Provider refreshes an authorized public profile image before downloading it and returns bounded PNG/JPEG/WebP/GIF base64 bytes; signed URLs, STS credentials and bearer tokens never enter the browser contract. Consumers must use `imageDataUrl()` (or decode the payload themselves) instead of concatenating OSS URLs or fetching an avatar reference directly.
+`readImage(avatarRef)` resolves an opaque image reference returned by `profile()`, `listSources()` or `listTeamMembers()`. Private chats and Team members expose one optional `avatarRef`. Groups expose the preferred additive `groupAvatar` presentation plus legacy `avatarRefs`: `groupAvatar.slots` preserves the server-selected order for up to five members, including safe phone-default or generic fallbacks when a real image is absent, while legacy `avatarRefs` contains only resolvable real images. `memberCount`, `strategy`, and `computedAtMillis` describe the snapshot without exposing member or session identities. The Provider refreshes an authorized public profile image before downloading it and returns bounded PNG/JPEG/WebP/GIF base64 bytes; signed URLs, STS credentials and bearer tokens never enter the browser contract. Consumers must use `imageDataUrl()` (or decode the payload themselves) instead of concatenating OSS URLs or fetching an avatar reference directly.
 
 `capabilities().features.worldFeed === true` advertises the additive World read contract. `worldFeed()` returns account-bound opaque `recordRef`, `avatarRef`, and `imageRefs` values; it never exposes stable record IDs, bearer tokens, `file_asset://` references, or signed OSS URLs. File-asset avatars are batch-resolved by the Provider. Resolution failure is best-effort and must keep the feed readable with its declared fallback avatar.
 

package/docs/emoji-presentation.md

@@ -0,0 +1,54 @@
+# 表情展示合同
+
+原始正文继续保存 jm_emoji / im_emoji token、Unicode 和既有媒体引用，不把展示转换写回正文。
+插件的 arkme-emoji-text 持有无资源依赖的表情目录、解析和安全截断；Browser 只关联内嵌 SVG。
+
+- 应用内用户内容经 ArkmeRichText；先识别完整 URL，再解析普通文本中的表情。正文保留原有链接行为，preview 只展示，不发起链接标题请求或产生交互元素。
+- 纯文本出口经 arkmeEmojiPlainText；未知编码原样保留。图片表情包继续走 contentBlocks 媒体链，不从文字猜测。
+- 视觉省略用 CSS；响应限长保护完整 token 和 Unicode 字素簇，并保留原有长度预算与截断标记。
+- 编辑器保留自己的光标、mention 和草稿模型，共享目录与序列化规则。
+- SVG 失败退化为可读 Unicode；图片提供语义名称。单个富文本块内含表情图片的复制选区转为 Unicode，同时保留 HTML 中的链接与格式；不含表情或跨块的选区保留浏览器原生复制。不得为每条文本新增网络请求、缓存或订阅。
+
+## 能力与验收范围
+
+| 消费面 / owner | 本次范围 | 验证 |
+| --- | --- | --- |
+| UI | 日历、时间轴与详情抽屉的延展父引用、相关快记、转发选择弹窗与转发详情、录音/长文卡片及已有 Unicode 展示入口 | 同一组 token、组合表情和混合内容贯穿实际组件；预览无请求/额外交互；失败与复制 |
+| Host | 既有内容投影使用共享安全截断，不改权限、查询或持久化合同 | 日历、相关快记、消息签名快照与两类转发快照的内容完整性测试 |
+| Tools / SDK | 不新增能力，继续消费同一 Host；不复制转换逻辑 | 现有日历和相关快记入口兼容测试 |
+| Client / Harness | 无原生桥或装配协议变化 | 独立制品安装、隔离页面验收；已安装客户端和生产发布不在本次授权内 |
+
+开发基线：插件 official/dev e7563b9e5fa84284032aeb0c7cd3a7020e1e0c44；提交 PR 前已合入最新 dev a055b4b15647741647c07acb368e68f958a74492 的 Markdown 合同。
+客户端只读参考 master 02f86d21dc3c2c94b01c4cd0e1f5f4bdda6bdeae。
+性能边界：解析工作随本次文本长度增长，不持有跨内容缓存；预览不新增 I/O。
+
+## 本次验证
+
+- 原始基线相关测试 203 项通过；修改后 typecheck、build 和制品清单检查通过。
+- 最新基线集成后全量：4024 项通过、5 项跳过、16 项失败。16 项失败全部在未修改的 dev/a055b4b 对应测试中逐项复现，失败集合完全一致；涉及 Markdown 基线的旧 UI/Host 参数断言、identity 与 service-architecture 清单。没有新增失败。
+- 官方 DSH 0.1.1-rc.2（源码参考标签 dsh-v0.1.1-rc.2，b150a551）通过 plugin CLI 安装独立 tgz；使用带空格的全新 DSH_HOME 和独立凭据命名空间。最终安装的 client.js 与构建输出摘要一致。
+- Chromium 实际页面使用浏览器路由固定样例，不使用真实账号：日历、时间轴父引用、详情父引用和相关快记均成功加载两种 token 对应的 SVG；未知 token 与 Unicode 保留，预览没有链接节点或链接元数据请求。
+- 实际复制快捷键产生 Unicode 文本；验证监听器阻止写入系统剪贴板。模拟缺失图片资源后成功退化为 Unicode。
+- 最终制品 SHA-256：bbad76d87ceb19e6e306e07c00ccea80a6811686c0758c91c4a5dcea1c73ef7b，版本保持 0.1.43。制品不含测试、node_modules、本机路径或验收端口。
+- 上述是隔离 DSH Browser 页面验收，不等同于真实账号的远端数据验收、已安装 Electron 客户端替换或 Windows/Linux 验收；未发布或提交 PR。性能只验证无新增预览请求，不声称测得吞吐或帧率提升。
+
+## 深入审查与修复
+
+| 问题 | 修复及证据 |
+| --- | --- |
+| P2：转发对象弹窗的最近消息与底部摘要绕过公共渲染 | 统一使用 preview 模式；实际弹窗加载 4 个表情图片，无链接节点；选择对象、填写附言、发送一次并关闭弹窗均验证通过，提交保留 actionRefs 与原始附言 token |
+| P2：表情优先解析会拆开 URL 参数 | 由已有链接解析器先确定 URL 边界，再将普通文本交给唯一表情解析器；body/preview 都覆盖含 token 的完整 URL |
+| P2：普通选区复制被无条件接管，含链接选区只留下纯文本 | 仅转换选区内的已知表情图片；保留 text/html 的原始 href；真实复制快捷键验证普通选区不接管、表情转 Unicode、链接不丢失，测试阻止写入系统剪贴板 |
+| P2：历史转发摘要用冒号猜作者，破坏 token、URL 和时间 | 摘要整体作为内容显示；作者只从结构化字段取得。摘要-only 记录显示通用摘要标签，复现样例均通过 |
+| P2：消息操作签名快照、普通记录/Agent 转发快照会写入半个 token | 使用共享安全截断并保留原有预算；公共读取→签名引用→转发写入测试与 Agent 网关测试证明原始正文保留，写入摘要不含半个 token |
+| 清理：Browser 有重复解析包装和松散的 run 类型；目录继承 Object 原型 | 删除包装层，直接消费无资源依赖的判别联合类型；Browser 目录不再将 constructor / __proto__ 视为表情 |
+
+架构边界：表情目录与文本语义归插件公共层，SVG 和复制归 Browser；聊天关系、普通记录和 Agent 的来源身份、授权、幂等仍由原 owner 持有。仅共用无副作用的文本函数，不合并不同消息协议，不转换持久化原始正文。
+
+没有新增状态机、计时器、订阅、缓存或数据库字段。图片组件仅保留当前资源是否加载失败的局部状态；没有新增兼容开关、双轨解析或过渡协议。jm_emoji / im_emoji 和摘要-only 读取属于既有历史数据合同。未修改提示词、版本字段或根 README。
+
+表情修复快照已通过官方 CLI 装入独立 Profile，并在 Electron 验收客户端加载（代码摘要一致）；转发弹窗和历史详情完成了固定业务样例的真实页面复验。最新 Markdown 基线的集成完成单测、类型检查与打包，尚未重新进行真机账号验收。
+
+输入区目标预览追加验收：延展与重新编辑共用的目标摘要已接入 preview 模式，102 项相关测试、typecheck 与 build 通过；原稿、重新编辑草稿及延展提交引用均保持原始数据。
+
+Markdown 集成：保留 text_format、代码块与业务标签的 AST 边界，只对普通正文文本渲染表情；新增复合样例验证正文渲染、行内/块级代码保留原文、URL 参数值不变。

package/docs/member-event-cache.md

@@ -0,0 +1,49 @@
+# 群成员变动记录的临时缓存
+
+退群记录使用插件客户端的共享内存缓存，不引入 SWR，不写本地磁盘或后端存储。
+缓存按登录环境、账号和群的 opaque source key 隔离；目前事件类型固定为 `left`。
+
+## 请求规则
+
+- 第一次进入群聊：等待快记窗口和群主身份就绪，查询当前时间范围。
+- 五分钟内再次进入：复用记录、查询范围、分页游标和空结果。最新窗口复用原截止时间，避免每次以新的当前时间查询。
+- 超过五分钟再次进入：先展示已缓存记录，再查询当前窗口。有效期只在进入时判断，没有定时校准、轮询、聚焦刷新或网络恢复刷新。
+- 历史滚动：只查询未覆盖的范围；密集事件的下一页仍由真实滚动触发。游标始终携带原查询范围，不拼接到新的时间窗口。
+- 加载旧游标不延长首页的有效期。未加载的分页不能被当作完整历史。
+- 查询失败保留已有记录，不自动重试；同群两秒失败冷却跨视图切换保留。
+
+## 缓存的首帧恢复
+
+展示缓存与发起查询分别控制。成员列表刷新时，群主身份会暂时变为未知；快记也可能仍在后台加载。
+这两种等待只阻止新的事件查询，不隐藏同账号、同群已授权读取的缓存。
+Hook 在渲染阶段通过只读 `peek` 同步取得记录，按已恢复的快记窗口过滤，避免先渲染空列表再等待 Effect 插入退群提示。
+组件重新挂载、尚无快记窗口时，使用缓存中上次同模式的窗口，不借用其他群或其他模式的窗口。
+没有缓存的首次进入仍等待群主身份和快记窗口。明确撤销权限时，首帧就隐藏记录并清理缓存。
+
+## 生命周期和通知
+
+`member-event-cache.ts` 持有每群的 `MemberEventTimeline`，组件只是订阅者。
+离开视图停止通知触发的查询和视图更新，已发出的请求可以完成并填充缓存；再次进入复用同一请求与分页状态。
+
+全局 SSE 消费者通过 `member-event-hints.ts` 通知缓存：
+
+- 正在查看的群沿用 300 毫秒合并、两秒最小刷新间隔和串行请求。
+- 非当前群只记录变动，不发请求；再次进入查询一次。
+- 事件 ID 去重状态保留在缓存中，请求按发起时的通知版本记录结果。请求期间的新通知继续有效。
+- 历史定位视图只刷新其历史窗口；这不能把最新窗口误标为已更新。
+
+退出登录或切换账号、环境会销毁缓存并取消请求，迟到结果不能写回。
+确认失去群主身份或服务端拒绝访问会清除对应群记录；身份加载中的临时禁用不会清缓存。
+名称点击和发起私聊仍沿用原服务端权限校验。
+
+## 容量与展示
+
+保留最近使用的 20 个群。离开视图后的缓存每群最多保留 1,000 条事件和 200 个查询范围；当前正在浏览的列表不因缓存限额截断。
+淘汰事件时同步丢弃覆盖这些事件的查询范围，避免出现“记录已淘汰，但被误判为已经加载”的缺口。
+
+快记与成员变动继续按发生时间和稳定 ID 合并。历史定位过滤当前窗口，不混入未来记录；名称高亮和资料卡行为保持原实现。
+
+## 验证
+
+回归测试覆盖切群和重新挂载的首帧、身份及快记加载中的缓存显示、空结果、过期后展示旧数据、失败冷却、跨视图游标、历史范围缺口、容量淘汰、权限撤销、账号隔离、后台群通知及请求期间新通知。
+请求入口和共享缓存通过真实 Hook / 控制器运行，接口边界使用可控响应记录实际发起的调用。

package/docs/resizable-composer-verification.md

@@ -0,0 +1,45 @@
+# Resizable chat composer verification
+
+- Base: official `origin/dev`, `4b8b40346be695774900997da4d6ce2f5a05e970`.
+- Branch: `codex/c20260904-resizable-composer`.
+- Scope: shared Arkme chat composer, client presentation only. No changes to DSH, plugin version, authentication or message sending.
+- Behavior: 6px top drag target, vertical resize cursor, 1px green border while hovered/dragged/focused, local browser height preference, double-click/Enter reset, arrow/Home/End keyboard controls, viewport height limit, pointer capture and cursor cleanup.
+
+## Capability coverage
+
+| Surface | Result |
+| --- | --- |
+| UI | Implemented and exercised in the installed plugin on Windows. |
+| Tools | N/A: visual browser layout preference; no new business operation. |
+| SDK | N/A: no Host API or shared business capability introduced. |
+| Host | N/A: no Host storage or routes; localStorage contains only an editor height. |
+
+## Verification
+
+- Relevant pre-change composer tests: 8 passed.
+- Composer presentation/draft tests after integration: 18 passed.
+- Resize, auth ownership and retained-surface tests after SSR fix: 15 passed.
+- TypeScript check and diff whitespace check passed.
+- Full suite: 3106 passed, 26 failed, 4 skipped; 16 failed suites and one additional suite-load failure within those suites. Not an all-green result. Remaining failures include Windows ACL command/module errors, fixture/source newline checksums, packaging/workflow expectations and timeouts. They have not all been independently reproduced on a clean baseline.
+- Standard build passed after temporarily normalizing the credential helper's six checksum inputs to LF. Original checkout line endings were restored afterward; no helper source changes are part of this patch.
+- Generated npm tarball, verified its client bundle hash matches the build, and installed it through official DSH `0.1.1-rc.1` into a fresh isolated profile. No link-based installation or DSH source edits.
+- Actual browser: upward drag changed editor height from 38px to 191px; green rounded border visible; reload and reopening conversation restored 191px; double-click reset to 38px. No test message sent.
+- Windows verified. macOS/Linux not exercised; this change adds no native/platform-specific code.
+
+The earlier sidebar-width PR is separate and is not included in this branch's dev baseline. No production deployment or replacement of the user's running instance is included.
+
+## Follow-up: message viewport anchoring
+
+- Confirmed missing behavior: a shrinking message viewport did not preserve its previous bottom distance, leaving latest messages below the visible region.
+- Added a viewport ResizeObserver: when previously within 80px of the bottom, keep the latest message visible; while reading history, preserve scrollTop. Handles resize-generated scroll events arriving before the observer, reset/expansion, short lists and observer disposal.
+- Composer bounds now use the actual chat area's available height; observers reconnect when the composer appears or the conversation changes. Switching conversation clears active drag/hover/focus state. Keyboard focus and pointer hover are tracked independently.
+- Relevant resize/auth/retained-surface tests: 18 passed. Typecheck and standard build passed (same temporary LF build normalization described above).
+- Full follow-up suite: 3108 passed, 27 failed, 4 skipped. Includes a recording-service timeout under the full parallel run; not an all-green result.
+- Installed a new immutable tarball into a separate official DSH profile; preserved the previous preview instance.
+- Browser verified: composer grew from 96px to 284px and the latest message moved upward by the same 188px, keeping the gap above the input. While reading older messages, increasing input height by 200px retained the same messages at the same top positions instead of jumping to the latest message.
+
+## Pre-PR review
+
+- Reviewed the complete integration, pointer lifecycle, optional storage, observer cleanup, history anchoring, scope changes and height bounds. No new blocking finding identified.
+- Re-fetched official dev; base remains unchanged with no integration conflict.
+- Re-ran seven targeted suites: 36 tests passed. The separate recording-service rerun from the follow-up passed; full-suite failures above remain disclosed rather than presumed resolved.

package/docs/resizable-note-detail-verification.md

@@ -0,0 +1,41 @@
+# Resizable note detail
+
+- Base: official dev `4b8b40346be695774900997da4d6ce2f5a05e970`.
+- Branch: `codex/c20260904-resizable-detail`.
+- Scope: shared right-edge overlay for normal/forwarded quick notes and interwoven details. Does not change message sending, underlying conversation layout, versions, root README or DSH sources.
+- Left-edge 10px pointer target, 3px green highlight, ew-resize cursor; pointer capture, cancellation/unmount cleanup, keyboard support, double-click reset and optional localStorage width memory.
+- Requested parity: default/minimum width 405px, maximum max(405px, 60% of available width). Containers narrower than 405px cap both bounds to the available width to prevent overflow. Previously saved preferences are clamped to the new bounds.
+
+## Coverage
+
+| Surface | Evidence |
+| --- | --- |
+| UI | Shared resize hook integrated into both detail owners; unit and drawer tests. |
+| Tools | N/A: no business capability, browser layout preference only. |
+| SDK | N/A: no public service/API changes. |
+| Host | N/A: no Host routes or persistence changes. |
+
+- Before change: 17 drawer tests passed. Final targeted coverage: 22 tests passed across identity, resize and drawer suites.
+- Typecheck passed. Standard build passed after temporary LF normalization of the existing credential-helper checksum inputs; original line endings restored, no helper source diff.
+- Latest full-suite run: 3102 passed, 30 failed, 4 skipped. One documentation identity failure was subsequently corrected and the identity suite passed in the targeted rerun. Remaining failures include Windows ACL/module issues, fixture checksums and other areas; not all were independently reproduced on an untouched baseline. Full-suite status is not green.
+- Packaged tarball installed via official DSH 0.1.1-rc.1 into a new isolated profile; existing preview instances preserved. No link installation or production deployment.
+- Windows is the exercised platform; macOS/Linux not verified.
+- Installed-package browser verification: final bounds verified at 405px minimum/default and approximately 554px maximum for a 924px container (60%). Green full-height divider confirmed. Earlier persistence verification confirmed the dragged width survived closing/reopening the detail. No messages sent or note data changed.
+- Scope review: no blocking issue identified in the resize change. Emoji rendering is untouched; the preview base does not include the separate sidebar emoji asset fix. This PR intentionally does not merge that work.
+
+## Updated dev integration (2026-09-04)
+
+- The earlier preview above is superseded. Merged official dev `4f093d0cff3ae98588ee8d9fc85c7bcf5d247696` without conflicts. The remote fetch configuration tracked only master, so fetching dev alone had left the old origin/dev reference unchanged; this run explicitly refreshed that reference.
+- Sidebar preview rendering now inherits dev's `ArkmeRichText` with 20px application emoji assets and matches master `8fea757ff81170311393036240a0c292afd3737a` in the emoji implementation. No separate emoji feature patch or version bump was authored; package metadata is inherited from dev.
+- Reviewed the complete five-file diff against updated dev, including the automatically merged detail shell. The resize scope remains client-only; Tools/SDK/Host remain N/A.
+- Targeted resize/drawer/sidebar/identity suites: 28 tests passed. Typecheck and build passed. The existing credential-helper source files were temporarily normalized to LF for build verification and restored byte-for-byte afterward.
+- Full suite: 3549 passed, 55 failed, 4 skipped (22 failed suites). This is not an all-green result and the failures are not all proven pre-existing. No unrelated test fixes are included.
+- A fresh isolated official DSH 0.1.1-rc.1 profile installed the immutable tarball. Installed client SHA256 matches the build. Windows browser verified detail width 405px -> 495px by pointer drag and back to 405px on Enter; targeted 28 tests passed again after review. Sidebar renderer and emoji assets are unchanged from current master. No messages sent or note content changed.
+
+## Review follow-up: regression coverage and baseline comparison
+
+- Added five tests covering parent resize/recovery and observer cleanup, pointer cancellation, lost pointer capture, unavailable storage, all resize keys and the window-resize fallback without ResizeObserver.
+- Compared full suites against an untouched worktree at dev `4f093d0cff3ae98588ee8d9fc85c7bcf5d247696`. This identified two PR-specific outdated assertions still requiring 372px in interwoven and forwarded details. Updated both to the intended 405px default, container cap and accessible resize separator; retained their other content and authorization assertions.
+- Expanded relevant suites: 88 passed. Typecheck and diff check passed. Review found no remaining confirmed resize implementation defect. No runtime code, emoji assets, metadata or version changes in this follow-up; the existing installed client remains byte-identical to the build.
+- Clean dev full run: 3546 passed, 56 failed, 4 skipped. Final PR full run: 3552 passed, 57 failed, 4 skipped. All 56 baseline failing test identities also fail in the PR. The one additional recording-service timeout passes when rerun alone, and its implementation/test files are identical to dev. The suite-load failure is `spawnSync pnpm ENOENT` on both revisions. This comparison does not claim the whole repository is green or repair unrelated baseline issues.
+- Remaining platform evidence limitation: macOS/Linux were not exercised. Windows pointer interaction evidence from the unchanged runtime above remains applicable.