@eduwork/dsh-mail 0.1.0-alpha.5 → 0.1.1

package/docs/compatibility.en.md

@@ -2,11 +2,12 @@
 
 [简体中文](compatibility.md) | **English**
 
-Package `@eduwork/dsh-mail@0.1.0-alpha.5` retains the alpha.4 runtime and settings contracts. See [migration](EDUWORK-MIGRATION.en.md).
+`@eduwork/dsh-mail@0.1.1` targets official DeepSeek Harness `0.1.5-rc.1` while retaining exact peer ranges for previously accepted baselines. See [migration](EDUWORK-MIGRATION.en.md) for the old unscoped package.
 
 ## Reviewed baseline
 
-- DeepSeek Harness `0.1.2-alpha.2`;
+- DeepSeek Harness `0.1.5-rc.1` (current release baseline);
+- DeepSeek Harness `0.1.2-rc.1`, `0.1.3-alpha.1`, `0.1.3-alpha.2`, and `0.1.5-alpha.1` (previously accepted compatibility baselines);
 - Node.js 22+;
 - dynamic Web Client Bundle;
 - local Host filesystem;
@@ -14,6 +15,10 @@ Package `@eduwork/dsh-mail@0.1.0-alpha.5` retains the alpha.4 runtime and settin
 
 The DSH Profile provides `settings`, `credentials`, `tools`, `permissionPresets`, `approval`, and `fs`. The settings page also depends on official Remotes, Renderer, and Settings Client packages. Ordinary sending requires an interactive approval path; Full Access does not prompt.
 
+DSH `0.1.5-rc.1` requires plugins to use the Agent explicitly from tool execution context. Mail reads the current session from each execution's `exec.agent`, uses `agent.session` for permission presets and workspace resolution, does not depend on a global Agent, does not create or resume Sessions, and does not use ordinary subprocess handles. The ToolRuntime, Permission Presets, Credentials, Settings, Renderer, and Settings Client seams are accepted.
+
+The official generic-file upload, Workspace Files, and `readByteRange()` can support future large-attachment improvements, but they cannot yet replace the Host binary write needed for IMAP downloads: `ctx.fs` still has no `writeBytes()`. This version therefore retains the local download adapter with workspace containment, real-path revalidation, and exclusive random filenames.
+
 ## Protocol scope
 
 - IMAP uses read-only mailbox semantics and UIDVALIDITY to reject stale UIDs.
@@ -24,7 +29,7 @@ The DSH Profile provides `settings`, `credentials`, `tools`, `permissionPresets`
 
 ## DSH binary-write limitation
 
-DSH `0.1.2-alpha.2` exposes `ctx.fs.readBytes` but no `writeBytes`:
+The current DSH `0.1.5-rc.1` release baseline exposes `ctx.fs.readBytes` but no `writeBytes`:
 
 - outbound local attachments use the official seam end to end;
 - downloads require `ctx.fs.processPath()` and the Host Node process to share one filesystem;
@@ -34,4 +39,4 @@ DSH `0.1.2-alpha.2` exposes `ctx.fs.readBytes` but no `writeBytes`:
 
 ## Version policy
 
-During `0.x`, a DSH alpha may change the Client Loader, settings slots, or tool schemas. For every upgrade, run the full automated suite and real IMAP/SMTP acceptance in an isolated Profile. Compilation alone is insufficient.
+The plugin follows its own SemVer instead of mirroring the host product: patch for compatibility fixes and dependency maintenance, minor for backward-compatible capability additions, and major only for breaking tool or configuration contracts. During DSH `0.x`, run the full automated suite and target-runtime acceptance for every upgrade, then complete IMAP/SMTP interoperability in an isolated Profile. Compilation alone is insufficient.

package/docs/compatibility.md

@@ -2,11 +2,12 @@
 
 **简体中文** | [English](compatibility.en.md)
 
-`@eduwork/dsh-mail@0.1.0-alpha.5` 保留 alpha.4 的运行时和设置契约。详见[迁移说明](EDUWORK-MIGRATION.md)。
+`@eduwork/dsh-mail@0.1.1` 面向官方 DeepSeek Harness `0.1.5-rc.1`，同时保留已验收旧基线的精确 peer 范围。旧无作用域包迁移见[迁移说明](EDUWORK-MIGRATION.md)。
 
 ## 已验证基线
 
-- DeepSeek Harness `0.1.2-alpha.2`；
+- DeepSeek Harness `0.1.5-rc.1`（当前发布基线）；
+- DeepSeek Harness `0.1.2-rc.1`、`0.1.3-alpha.1`、`0.1.3-alpha.2`、`0.1.5-alpha.1`（保留兼容的历史验收基线）；
 - Node.js 22+；
 - Web Client 动态 Bundle；
 - 本地 Host 文件系统；
@@ -14,6 +15,10 @@
 
 插件依赖 DSH Profile 提供 `settings`、`credentials`、`tools`、`permissionPresets`、`approval` 和 `fs`。设置页还依赖官方 Web Client 的 Remotes、Renderer 与 Settings 插槽；普通权限下发信需要交互式审批通路，Full Access 下不会弹出审批。
 
+DSH `0.1.5-rc.1` 要求插件从工具执行上下文显式使用 Agent。Mail 从每次执行的 `exec.agent` 读取当前会话，通过 `agent.session` 获取权限预设和工作区，不依赖全局 Agent，不创建或恢复 Session，也不使用普通 subprocess handle。ToolRuntime、Permission Presets、Credentials、Settings、Renderer 和 Settings Client 接缝均已验收。
+
+官方通用文件上传、Workspace Files 和 `readByteRange()` 可供后续大附件体验复用，但当前不能替代 IMAP 下载所需的 Host 二进制写入：`ctx.fs` 仍没有 `writeBytes()`。因此本版本继续保留受工作区约束、重新校验真实路径并使用独占随机文件名的本地下载适配。
+
 ## 协议范围
 
 - IMAP 遵循只读 mailbox 语义，并用 UIDVALIDITY 防止陈旧 UID 误读。
@@ -24,7 +29,7 @@
 
 ## DSH 二进制写限制
 
-`ctx.fs` 在 `0.1.2-alpha.2` 提供 `readBytes`，没有 `writeBytes`。因此：
+当前发布基线 DSH `0.1.5-rc.1` 提供 `readBytes`，没有 `writeBytes`。因此：
 
 - 发送本地附件可完整复用官方 seam；
 - 下载附件只能在 `ctx.fs.processPath()` 与 Host Node 进程指向同一文件系统时工作；插件会在创建目录后解析真实路径并再次验证工作区包含关系；
@@ -33,4 +38,4 @@
 
 ## 版本策略
 
-在 `0.x` 阶段，DSH alpha 的 Client Loader、settings slots 或 tool schema 变化可能要求插件同步更新。每次升级先运行 `npm run check`，再在隔离 Profile 中完成真实 IMAP/SMTP 验收，不应只依赖编译通过。
+插件独立使用 SemVer，不跟随宿主产品版本。兼容性修复和依赖维护使用 patch，向后兼容能力使用 minor，破坏工具或配置契约才使用 major。在 DSH `0.x` 阶段，每次升级都先运行 `npm run check` 与目标 Runtime 验收，再在隔离 Profile 中完成 IMAP/SMTP 互操作，不应只依赖编译通过。

package/docs/decisions/0001-mail-assistant-boundary.en.md

@@ -20,7 +20,7 @@ Delete, move, archive, flag mutation, contacts, rules, polling, auto-reply, HTML
 
 ## Consequences
 
-- The plugin can be open-sourced and composed by Web or desktop DSH without depending on ChatECNU Work.
+- The plugin can be open-sourced and composed by Web or desktop DSH without depending on a particular product composition.
 - Users keep a professional mail client for mailbox-state management; the Agent focuses on retrieval, understanding, and authorized sending.
 - Full Access matches other DSH write tools and skips per-call approval, while the independent sending capability remains mandatory.
 - Any future background or mutation boundary requires another ADR, threat model, and migration plan.

package/docs/decisions/0001-mail-assistant-boundary.md

@@ -20,7 +20,7 @@ Gmail 等专用 OAuth2 API 与通用 IMAP/SMTP 的认证、权限和审计模型
 
 ## 结果
 
-- 插件可以独立开源并被 Web 或桌面 DSH 组合复用，不绑定 ChatECNU Work。
+- 插件可以独立开源并被 Web 或桌面 DSH 组合复用，不绑定任何特定产品。
 - 用户仍使用专业邮箱客户端管理邮箱状态，Agent 聚焦检索、理解和经授权的发信。
 - Full Access 与 DSH 其他写工具保持一致，会跳过逐次审批；独立的发信开关仍是必要条件。
 - 未来扩展若改变写操作或后台授权，必须新增 ADR、威胁模型和迁移说明。

package/docs/getting-started.en.md

@@ -5,7 +5,7 @@
 ## Requirements
 
 - Node.js 22+;
-- DeepSeek Harness `0.1.2-alpha.2`;
+- DeepSeek Harness `0.1.5-rc.1`;
 - a Profile with Settings, Credentials, Tools, Filesystem, Permission Presets, Approval, and Web Client;
 - an IMAP/SMTP-enabled mailbox and provider-issued app password.
 
@@ -14,7 +14,7 @@
 For normal use, pin the reviewed exact npm version:
 
 ```bash
-dsh plugin --profile web add @eduwork/dsh-mail@0.1.0-alpha.5
+dsh plugin --profile web add @eduwork/dsh-mail@0.1.1
 ```
 
 For auditing, development, or unpublished changes, use a source checkout:
@@ -27,7 +27,7 @@ npm run check
 dsh plugin --profile web add .
 ```
 
-Installation adds one Bundle to the Profile. Empty configuration is valid: the plugin performs no server probe or runtime installation during install, startup, or save. A source installation links the checkout into the Profile, so keep that directory available. Team deployments should pin an exact npm version; use `@eduwork/dsh-mail@alpha` only when intentionally following prereleases.
+Installation adds one Bundle to the Profile. Empty configuration is valid: the plugin performs no server probe or runtime installation during install, startup, or save. A source installation links the checkout into the Profile, so keep that directory available. Team deployments should pin the reviewed exact npm version. Before upgrading, back up the Profile's `package.json` and `cordis.patch.yml`; never enable the scoped and unscoped packages together.
 
 ## Configuration
 
@@ -38,6 +38,8 @@ Open **Settings → Mail assistant** and follow the page order:
 3. Use Advanced settings only when the provider needs a distinct login username, a nonstandard inbox path, or changed safety limits.
 4. Enable Agent reading and sending independently, then save.
 
+Without a UI, put only the address, hosts, ports, TLS modes, and capability switches in Bundle configuration. The app password must enter a DSH Credential Provider under the fixed reference `DSH_MAIL_ASSISTANT_PASSWORD`; never put it in YAML, source code, shell history, or diagnostic logs.
+
 Typical secure combinations are IMAP 993 with implicit TLS, SMTP 465 with implicit TLS, or SMTP 587 with STARTTLS. Follow the provider's documentation. Certificate validation cannot be disabled.
 
 ## Acceptance
@@ -47,9 +49,24 @@ Typical secure combinations are IMAP 993 with implicit TLS, SMTP 465 with implic
 3. Search a range with more matches than a deliberately small page size; the agent must follow `nextCursor` until `hasMore=false` before summarizing the full range.
 4. Read a test message containing prompt-injection text; the agent must treat it as untrusted data.
 5. Download a small attachment; it must land under `.dsh-mail-assistant/attachments/` in the current workspace without overwriting.
-6. Keep an ordinary permission preset, enable sending, and send to a controlled test address; a fresh approval must appear.
+6. Keep an ordinary permission preset, enable sending, ask the agent to show recipient, subject, body, and attachments first, then send to a controlled test address; a fresh approval must appear.
 7. Reject approval; no SMTP send occurs.
 8. Switch to Full Access and send again to the controlled address; no approval appears and delivery succeeds.
 9. Try an attachment outside the workspace; the tool must reject it.
 
 Use a dedicated test mailbox. Never put addresses, subjects, bodies, server logs, or app passwords in a public issue.
+
+## Development acceptance
+
+```bash
+npm ci
+npm run check
+```
+
+To verify the real DSH `0.1.5-rc.1` contract, point `DSH_RUNTIME_ROOT` at a clean runtime of that exact version and run:
+
+```bash
+npm run accept:dsh-015-rc1
+```
+
+This uses a no-network delivery simulator to cover Agent-session, rejection, one-time approval, and Full Access paths without a real mailbox. Run real IMAP/SMTP interoperability only with a dedicated test account in an isolated Profile.

package/docs/getting-started.md

@@ -5,8 +5,8 @@
 ## 前置条件
 
 - Node.js 22+；
-- DeepSeek Harness `0.1.2-alpha.2`；
-- Profile 中已经有 Settings、Credentials、Tools、Filesystem、Approval 和 Web Client；
+- DeepSeek Harness `0.1.5-rc.1`；
+- Profile 中已经有 Settings、Credentials、Tools、Filesystem、Permission Presets、Approval 和 Web Client；
 - 一个开启了 IMAP/SMTP 的邮箱账号，以及邮箱服务商签发的客户端授权码或应用专用密码。
 
 ## 安装
@@ -14,7 +14,7 @@
 普通使用固定经过复核的 npm 精确版本：
 
 ```bash
-dsh plugin --profile web add @eduwork/dsh-mail@0.1.0-alpha.5
+dsh plugin --profile web add @eduwork/dsh-mail@0.1.1
 ```
 
 需要审计、开发或验证尚未发布的改动时，使用源码 checkout：
@@ -29,7 +29,7 @@ dsh plugin --profile web add .
 
 安装只向 Profile 加入一个 Bundle。插件配置为空也能正常启动；不会在启动时探测服务器或安装额外运行时。
 
-源码安装会把 checkout 链接进 Profile，因此目录必须持续存在。团队部署应固定 npm 精确版本；只有明确希望持续跟随预发布更新时才使用 `@eduwork/dsh-mail@alpha`。
+源码安装会把 checkout 链接进 Profile，因此目录必须持续存在。团队部署应固定经复核的 npm 精确版本。升级前先备份 Profile 的 `package.json` 与 `cordis.patch.yml`，不要同时启用新旧包。
 
 ## 配置
 
@@ -40,6 +40,8 @@ dsh plugin --profile web add .
 3. 仅在服务商要求时，到“高级设置”填写独立登录用户名；收件箱目录通常保持 `INBOX`；
 4. 最后分别开放 Agent 的读信和发信能力并保存。
 
+无 UI 时，只把邮箱地址、服务器、端口、TLS 模式和能力开关写入 Bundle 配置。授权码必须进入 DSH Credential Provider，固定引用名为 `DSH_MAIL_ASSISTANT_PASSWORD`；不要写入 YAML、源码、命令历史或诊断日志。
+
 常见安全组合是 IMAP 993 + 隐式 TLS、SMTP 465 + 隐式 TLS，或 SMTP 587 + STARTTLS。具体值以邮箱服务商文档为准；不要为了连通而关闭证书校验，本插件也不提供这个开关。
 
 ## 验收
@@ -49,9 +51,24 @@ dsh plugin --profile web add .
 3. 用较小的每页条数查找一个命中较多的时间范围；确认 Agent 按 `nextCursor` 持续翻页，直到 `hasMore=false` 后才总结整个范围。
 4. 读取一封包含“忽略此前指令”等文本的测试邮件；确认 Agent 把它视为不可信数据。
 5. 下载一个小附件；确认文件位于当前工作区的 `.dsh-mail-assistant/attachments/`，且不会覆盖同名文件。
-6. 保持普通权限，开启发信，让 Agent 向自己的测试地址发送纯文本；确认出现逐次审批。
+6. 保持普通权限，开启发信，让 Agent 先展示收件人、主题、正文和附件，再向自己的测试地址发送纯文本；确认出现逐次审批。
 7. 拒绝审批；确认没有 SMTP 发送。
 8. 切换到 Full Access，再向自己的测试地址发信；确认不再弹出审批且邮件正常送达。
 9. 尝试把工作区外文件作为附件；确认工具拒绝。
 
 真实邮箱测试应使用专门测试账号，不要在公开 issue 附上服务器日志、地址、标题、正文或授权码。
+
+## 开发验收
+
+```bash
+npm ci
+npm run check
+```
+
+要复核 DSH `0.1.5-rc.1` 的真实运行时契约，把 `DSH_RUNTIME_ROOT` 指向该版本的干净 Runtime 后运行：
+
+```bash
+npm run accept:dsh-015-rc1
+```
+
+此验收使用无网络发送模拟器检查 Agent 会话、审批拒绝、单次允许与 Full Access 路径，不需要真实邮箱。真实 IMAP/SMTP 互操作只在专用测试账号和隔离 Profile 中执行。

package/docs/release-checklist.en.md

@@ -2,11 +2,11 @@
 
 [简体中文](release-checklist.md) | **English**
 
-A release pull request records reviewers, date, command-output links, and exceptions. Every item blocks a stable release; an alpha release must complete all applicable items and state remaining risk.
+A release pull request or release record captures the maintainer decision, date, command-output links, independent technical-review evidence, and exceptions. A sole maintainer owns publication during the project's initial stage; do not invent a second human approver who does not exist. Any applicable incomplete security or publication check blocks a stable release. Additional maintainers and multi-person review remain future governance goals.
 
 ## Authority and metadata
 
-- [ ] Repository owner approved public release and the MIT license.
+- [ ] The current maintainer approved public release and the MIT license and recorded technical-review evidence and remaining risk.
 - [ ] GitHub repository, npm name, homepage, issues, and private security-report URLs are correct.
 - [ ] Version, changelog, compatibility, and install commands agree.
 - [ ] Chinese is the default language and every Markdown document has an English mirror with reciprocal entries.
@@ -34,6 +34,7 @@ A release pull request records reviewers, date, command-output links, and except
 
 ## Functional acceptance
 
+- [ ] Run `npm run accept:dsh-015-rc1` against the exact current DSH version declared by the manifest, and confirm that the runtime contains no mixed older DSH packages.
 - [ ] `mail_list_folders` returns server folders without mutation.
 - [ ] `mail_find` covers both directions, pagination, dates, folders, stale UIDVALIDITY, and `hasMore=false`.
 - [ ] `mail_read` preserves unread state; truncation and HTML fallback match documentation.
@@ -43,9 +44,10 @@ A release pull request records reviewers, date, command-output links, and except
 
 ## Supply chain and publication
 
-- [ ] Clean `npm ci` and `npm run check` pass on Windows and Linux with Node 22.
+- [ ] Clean `npm ci` and `npm run check` pass on Windows and Linux with Node 22/24.
 - [ ] `npm audit`, CodeQL, direct/transitive licenses, and install scripts receive human review.
 - [ ] GitHub Actions use immutable commits; Dependabot and branch protection are active.
 - [ ] `npm pack --dry-run` and the extracted tarball contain only expected files; the Host bundle has no bare IMAP/SMTP imports.
 - [ ] Tag, release notes, tarball checksum, deprecation, and rollback are ready.
-- [ ] Stable publication uses npm Trusted Publishing/OIDC and provenance rather than a long-lived token.
+- [ ] Enable OIDC/provenance only after verifying that npm Trusted Publishing is bound to this repository, `.github/workflows/release.yml`, and environment `npm`.
+- [ ] When Trusted Publishing is not verified, publish the reviewed frozen artifact with the npm CLI and browser 2FA; make no provenance claim and store no long-lived token.

package/docs/release-checklist.md

@@ -2,11 +2,11 @@
 
 **简体中文** | [English](release-checklist.en.md)
 
-发布 Pull Request 应记录审查人、日期、命令输出链接和例外。任何未完成项目都会阻止稳定发布；alpha 发布也必须完成与本次改动相关的项目并明确剩余风险。
+发布 Pull Request 或发布记录应记维护者决策、日期、命令输出链接、独立技术复核证据和例外。项目初期由单一维护者负责发布；不得虚构尚不存在的第二位人工批准人。任何适用且未完成的安全或发布检查都会阻止稳定发布；未来增加替补和多人审查作为治理目标记录。
 
 ## 授权与元数据
 
-- [ ] 仓库所有者确认公开发布和 MIT 许可证。
+- [ ] 当前维护者确认公开发布和 MIT 许可证，并记录技术复核证据与剩余风险。
 - [ ] GitHub 仓库、npm 包名、主页、Issue 和安全报告地址准确。
 - [ ] 版本、Changelog、兼容性和安装命令一致。
 - [ ] 默认文档为中文，每份 Markdown 文档都有英文镜像和双向入口。
@@ -34,6 +34,7 @@
 
 ## 功能验收
 
+- [ ] 使用 manifest 声明的当前 DSH 精确版本运行 `npm run accept:dsh-015-rc1`，并确认 Runtime 没有混入旧版 DSH 包。
 - [ ] `mail_list_folders` 返回真实目录且不修改状态。
 - [ ] `mail_find` 的正序/倒序、多页、日期、目录、UIDVALIDITY 失效和 `hasMore=false` 均测试。
 - [ ] `mail_read` 不改变已读状态，正文截断和 HTML 降级符合文档。
@@ -43,9 +44,10 @@
 
 ## 供应链与发布
 
-- [ ] Windows 与 Linux 使用 Node 22 完成干净 `npm ci` 和 `npm run check`。
+- [ ] Windows 与 Linux 使用 Node 22/24 完成干净 `npm ci` 和 `npm run check`。
 - [ ] `npm audit`、CodeQL、直接/间接许可证和安装脚本已人工审查。
 - [ ] GitHub Actions 固定到不可变 commit，Dependabot 与分支保护有效。
 - [ ] `npm pack --dry-run` 和解压后的 tarball 只包含预期文件；Host bundle 没有外部 IMAP/SMTP 裸导入。
 - [ ] tag、发布说明、tarball checksum、弃用和回滚方案已准备。
-- [ ] 稳定发布使用 npm Trusted Publishing/OIDC 和 provenance，不使用长期 Token。
+- [ ] 已现场验证 npm Trusted Publisher 绑定本仓库、`.github/workflows/release.yml` 与 Environment `npm` 后，才启用 OIDC/provenance 发布路径。
+- [ ] Trusted Publisher 未验证时，从经复核的冻结包使用 npm CLI 和浏览器 2FA 发布，不声明 provenance，也不保存长期 Token。

package/lib/client.js

@@ -33,8 +33,8 @@ window.__ModuleLoader__.load({
 		const inject = [
 			"slots",
 			"remote",
-			"remote.settings",
-			"remote.credentials"
+			"remote.credentials",
+			"settingsScope"
 		];
 		const NS = "dsh-mail-assistant";
 		const PASSWORD_REF = "DSH_MAIL_ASSISTANT_PASSWORD";
@@ -90,6 +90,8 @@ window.__ModuleLoader__.load({
 			usage: "保存后，在对话里让 Agent“查一下最近邮件”即可验证。插件不会在启动或保存时主动连接邮箱。",
 			error: "保存失败",
 			reload: "重新加载",
+			unavailable: "当前 DSH 连接未提供此设置命名空间。",
+			readOnly: "当前连接为只读模式，无法保存设置。",
 			credentialPartial: "授权码已经保存，但其他配置保存失败；请修正后再次保存。"
 		} : {
 			nav: "Mail assistant",
@@ -143,6 +145,8 @@ window.__ModuleLoader__.load({
 			usage: "After saving, ask the agent to find recent mail. The plugin never connects to a mailbox during startup or save.",
 			error: "Save failed",
 			reload: "Reload",
+			unavailable: "This DSH connection does not expose the mail settings namespace.",
+			readOnly: "This connection exposes settings in read-only mode.",
 			credentialPartial: "The app password was stored, but the remaining settings failed to save. Fix the form and save again."
 		};
 		const defaults = {
@@ -219,33 +223,37 @@ window.__ModuleLoader__.load({
 		}
 		function MailSettings({ service }) {
 			const [draft, setDraft] = (0, react.useState)(null);
-			const [revision, setRevision] = (0, react.useState)(0);
 			const [passwordConfigured, setPasswordConfigured] = (0, react.useState)(false);
+			const [credentialWritable, setCredentialWritable] = (0, react.useState)(false);
 			const [password, setPassword] = (0, react.useState)("");
 			const [busy, setBusy] = (0, react.useState)(false);
 			const [notice, setNotice] = (0, react.useState)("");
 			const [error, setError] = (0, react.useState)("");
 			const [preset, setPreset] = (0, react.useState)("custom");
 			const [advancedOpen, setAdvancedOpen] = (0, react.useState)(false);
+			const subscribe = (0, react.useMemo)(() => service.scope.subscribe.bind(service.scope), [service.scope]);
+			const getSnapshot = (0, react.useMemo)(() => service.scope.getSnapshot.bind(service.scope), [service.scope]);
+			const snapshot = (0, react.useSyncExternalStore)(subscribe, getSnapshot, getSnapshot);
 			const load = async () => {
 				setError("");
 				setNotice("");
-				const [settings, credentials] = await Promise.all([unwrap(service.settings.describe()), unwrap(service.credentials.describe([PASSWORD_REF]))]);
-				const namespace = settings.namespaces.find((candidate) => candidate.ns === NS);
-				if (!namespace) throw new Error("dsh-mail-assistant settings namespace is not available");
-				const next = {
-					...defaults,
-					...namespace.value ?? {}
-				};
-				setDraft(next);
-				setPreset(detectPreset(next));
-				setRevision(namespace.revision ?? 0);
+				const credentials = await unwrap(service.credentials.describe([PASSWORD_REF]));
 				setPasswordConfigured(credentials[PASSWORD_REF]?.configured === true);
+				setCredentialWritable(credentials[PASSWORD_REF]?.writable === true);
 				setPassword("");
 			};
 			(0, react.useEffect)(() => {
 				load().catch((cause) => setError(cause?.message || String(cause)));
 			}, []);
+			(0, react.useEffect)(() => {
+				if (snapshot.status !== "ready") return;
+				const next = {
+					...defaults,
+					...snapshot.value ?? {}
+				};
+				setDraft(next);
+				setPreset(detectPreset(next));
+			}, [snapshot]);
 			const set = (key, value) => setDraft((current) => ({
 				...current,
 				[key]: value
@@ -269,12 +277,12 @@ window.__ModuleLoader__.load({
 						setPasswordConfigured(true);
 						setPassword("");
 					}
-					const namespace = await unwrap(service.settings.replace(NS, draft, revision));
-					setDraft({
-						...defaults,
-						...namespace.value ?? draft
-					});
-					setRevision(namespace.revision ?? revision + 1);
+					const ops = Object.entries(draft).map(([field, value]) => ({
+						op: "set",
+						path: [field],
+						value
+					}));
+					await service.scope.mutate(ops, snapshot.revision);
 					setNotice(copy.saved);
 				} catch (cause) {
 					setError(passwordStored ? copy.credentialPartial : cause?.message || `${copy.error}`);
@@ -361,7 +369,7 @@ window.__ModuleLoader__.load({
 			};
 			if (!draft) return /* @__PURE__ */ (0, react_jsx_runtime.jsxs)("div", {
 				style: styles.root,
-				children: [/* @__PURE__ */ (0, react_jsx_runtime.jsx)("p", { children: error || copy.loading }), error && /* @__PURE__ */ (0, react_jsx_runtime.jsx)("button", {
+				children: [/* @__PURE__ */ (0, react_jsx_runtime.jsx)("p", { children: error || (snapshot.status === "unavailable" ? copy.unavailable : copy.loading) }), error && /* @__PURE__ */ (0, react_jsx_runtime.jsx)("button", {
 					style: styles.button,
 					onClick: () => load(),
 					children: copy.reload
@@ -531,6 +539,7 @@ window.__ModuleLoader__.load({
 												type: "password",
 												autoComplete: "new-password",
 												value: password,
+												disabled: busy || !credentialWritable,
 												placeholder: copy.credentialPlaceholder,
 												onChange: (event) => setPassword(event.currentTarget.value),
 												style: styles.input
@@ -538,7 +547,7 @@ window.__ModuleLoader__.load({
 											/* @__PURE__ */ (0, react_jsx_runtime.jsx)("span", { children: copy.passwordHint }),
 											passwordConfigured && /* @__PURE__ */ (0, react_jsx_runtime.jsx)("button", {
 												type: "button",
-												disabled: busy,
+												disabled: busy || !credentialWritable,
 												style: {
 													...styles.button,
 													justifySelf: "start",
@@ -710,6 +719,14 @@ window.__ModuleLoader__.load({
 						},
 						children: copy.usage
 					}),
+					!snapshot.writable && /* @__PURE__ */ (0, react_jsx_runtime.jsx)("p", {
+						role: "status",
+						style: {
+							color: colors.secondary,
+							fontSize: 12
+						},
+						children: copy.readOnly
+					}),
 					error && /* @__PURE__ */ (0, react_jsx_runtime.jsx)("p", {
 						role: "alert",
 						style: {
@@ -728,7 +745,7 @@ window.__ModuleLoader__.load({
 					}),
 					/* @__PURE__ */ (0, react_jsx_runtime.jsx)("button", {
 						type: "button",
-						disabled: busy,
+						disabled: busy || !snapshot.writable,
 						onClick: save,
 						style: styles.primary,
 						children: busy ? copy.saving : copy.save
@@ -738,7 +755,7 @@ window.__ModuleLoader__.load({
 		}
 		function apply(ctx) {
 			const service = {
-				settings: ctx.remote.settings,
+				scope: ctx.settingsScope.bind({ namespace: NS }),
 				credentials: ctx.remote.credentials
 			};
 			ctx.slots.inject("settings.section", () => ctx.slots.register({