@agent-network-protocol/dsh-anp-identity 0.1.0-dsh-test.20260831.1

package/BOUNDARY.md

@@ -0,0 +1,47 @@
+# Security and ownership boundary
+
+The DSH package is a policy and lifecycle layer around ANP Identity. It does not replace the native custody boundary.
+
+## Trust zones
+
+- ANP Identity Rust and its Node binding hold Store Root Keys, managed private keys, and decrypted signing material.
+- The DSH Host process is trusted to load the native Provider and configure consumer policy.
+- Ordinary `IdentityClientLease` consumers receive public identity data, signatures, verification outcomes, high-level document sessions, and complete HTTP responses.
+- `HostProviderLease` consumers are explicitly listed in `allowProviderConsumers`. They may use sealed secret handoffs and exact HTTP Header patches for a native bridge. They must never forward those values to Browser, Remote, tools, or model APIs.
+
+Consumer identifiers are soft same-process identities. The allowlists prevent accidental cross-plugin use and provide an auditable policy, but JavaScript in the same process is not a sandbox.
+
+## Secret rules
+
+- The default client surface has no raw ECDH, private-key import, Root Key export, sealed envelope, or Header patch method.
+- ECDH shared secrets, Root Keys, and imported identity material cross the JavaScript bridge only as `anp-sealed-secret/1` envelopes on the Host Provider surface.
+- Injected Store Root Keys are a Host bootstrap exception. Supply them only programmatically; never serialize them into Loader configuration. The Provider copies each 32-byte input for one native call and clears that copy afterward.
+- Payloads and HTTP bodies may be application-sensitive even though they are not key material. The plugin does not log them or place them in errors.
+- The Node binding owns native temporary zeroization. JavaScript Buffers cannot be promised equivalent zeroization because the runtime may copy them.
+
+## Catalog rules
+
+`catalog-v1` contains no cryptographic secrets. It records labels, handles, consumer grants, and Store identity references. The native Store is always identity truth.
+
+- A create intent is durable before native creation. A separate cross-process create lock makes the Store delta recoverable without holding the catalog lock across a native await.
+- A deletion tombstone blocks new grants, handles, and client signing before native deletion starts.
+- Catalog writes use a generation check, an exclusive cross-process lock, a same-directory temporary file, `fsync`, atomic rename, and directory `fsync`.
+- Corruption never falls back to guessed grants. Explicit rebuild produces only `Unclaimed` identities.
+- Deleting an identity with another consumer grant is rejected.
+
+## HTTP dispatcher
+
+The default client API exposes only `dispatch(Request, transport)`:
+
+- exact HTTPS origins must be authorized by Host configuration and requested by the lease;
+- caller-supplied `Authorization`, `Signature-Input`, `Signature`, and `Content-Digest` are rejected;
+- replayable request bytes are buffered up to 4 MiB;
+- the authenticated Request uses `redirect: 'manual'`;
+- only `Content-Digest`, `Signature-Input`, and `Signature` may be applied from the native patch;
+- transport failures propagate unchanged, while provider failures use stable codes without request or path detail.
+
+AWiki's Bearer Token cache, challenge processing, and retry policy remain in `dsh-awiki` and AWiki IM Core. This package signs one exact request and does not duplicate that authentication state.
+
+## Out of scope
+
+This package does not provide OS sandboxing, malicious-plugin isolation, DID resolution or publication, remote backup, Store rekey, Root Key rotation, or an end-user approval UI. Root Transfer user-presence confirmation remains an AWiki workflow above the Host Provider lease.

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,170 @@
+# ANP Identity for DeepSeek Harness
+
+`@agent-network-protocol/dsh-anp-identity` gives DSH applications one shared, multi-DID identity store without making each application implement key custody, DID document lifecycle, crash recovery, or request signing.
+
+Applications use a small TypeScript facade through `ctx.anpIdentity`. The plugin delegates private-key operations to the ANP Identity native module, keeps private keys encrypted at rest, and stores only non-secret DSH metadata—labels, handles, and consumer grants—in its catalog.
+
+## What problem it solves
+
+A DSH installation may host several plugins and several independent DIDs. Those plugins need consistent answers to the same questions:
+
+- Where are DID private keys stored, and which key is valid for a purpose?
+- How can a DID document update survive process and network failures?
+- How can two plugins share an identity without either plugin owning its private key?
+- How can a request be authenticated without exposing a reusable signature header patch?
+- How can a Store contain several DIDs while handles and deletion grants remain consistent?
+
+This package supplies that coordination layer. ANP Identity remains the source of truth for identities and encrypted keys. A transactional `catalog-v1` adds DSH-specific ownership metadata. Creation uses a recoverable intent; deletion writes a tombstone before touching the native Store; cross-process mutations use a file lock, generation checks, and atomic rename.
+
+## What it provides
+
+- Multi-DID create, list, open, delete, and recovery operations.
+- Purpose-based Ed25519 signing and verification.
+- Origin Proof signing.
+- Transactional DID document change sessions.
+- Consumer-scoped leases, grants, labels, and unique handles.
+- Bounded authenticated HTTP dispatch with exact HTTPS-origin allowlists, a 4 MiB body limit, managed-header rejection, and manual redirects.
+- A separate Host Provider lease for AWiki IM Core and similar trusted native consumers. Host-only operations include sealed ECDH, sealed import/export, enrollment, Root Transfer, and exact HTTP header patches.
+
+## What it does not provide
+
+- It is not a DID registry, resolver, publication server, backup system, or wallet UI.
+- It does not implement AWiki messaging, Bearer Token state, challenge retries, or P5 Root Transfer. `dsh-awiki` and AWiki IM Core own those workflows.
+- It does not expose raw ECDH shared secrets, Root Keys, imported private keys, or general signing tools to Browser, Remote, agents, or models.
+- Consumer names are a same-process policy and diagnostics boundary. They prevent accidental misuse; they do not sandbox malicious code running in the same Node.js process.
+
+See [BOUNDARY.md](./BOUNDARY.md) for the complete trust model.
+
+## Installation
+
+Install the DSH plugin:
+
+```bash
+pnpm add @agent-network-protocol/dsh-anp-identity
+```
+
+The package installs the exact compatible ANP Identity wrapper. That wrapper
+selects the prebuilt native package for the current platform; users do not need
+Rust or a source checkout.
+
+Load the Service before its Provider. The included `cordis.patch.yml` is a starting point:
+
+The shipping DSH layer grants `@awiki/dsh-plugin` client and Host Provider
+access by default so the documented two-plugin AWiki installation works without
+an extra local patch. Set `DSH_ANP_IDENTITY_ALLOW_CONSUMERS` and
+`DSH_ANP_IDENTITY_ALLOW_PROVIDER_CONSUMERS` to explicit JSON arrays to replace
+those defaults for a different deployment.
+
+```yaml
+- insert:
+    - id: anp-identity
+      name: '@agent-network-protocol/dsh-anp-identity'
+      config:
+        stateRoot: /var/lib/dsh/anp-identity
+        allowConsumers: ['example/identity-client', '@awiki/dsh-plugin']
+        allowProviderConsumers: ['@awiki/dsh-plugin']
+        httpAllowedOrigins:
+          example/identity-client: ['https://api.example.com']
+
+    - id: anp-identity-provider
+      name: '@agent-network-protocol/dsh-anp-identity/provider'
+      config:
+        stateRoot: /var/lib/dsh/anp-identity
+        rootKeyProvider: keyring
+        rootKeyProviderId: anp-identity/dsh
+```
+
+`rootKeyProviderId` is `service/account` for keyring, the environment variable name for `env`, and the key id for programmatic `injected` setup. `local-file` must be selected explicitly; copying both the Store and its local Root Key file permits offline decryption.
+
+## Use it from another DSH plugin
+
+Declare the Cordis dependency, acquire only the capabilities you need, and dispose the lease with the calling plugin's fiber:
+
+```ts
+import type { Context } from '@deepseek-ai/cordis'
+import type {} from '@agent-network-protocol/dsh-anp-identity'
+
+export const inject = ['anpIdentity']
+
+export async function apply(ctx: Context): Promise<void> {
+  const lease = await ctx.anpIdentity.acquireClient({
+    consumer: 'example/identity-client',
+    capabilities: ['identity:read', 'identity:create', 'identity:sign'],
+  })
+  ctx.effect(() => () => lease.dispose(), 'example: ANP Identity client lease')
+
+  const identities = await lease.list()
+  const identity = identities.length === 0
+    ? await lease.create({
+        label: 'Example agent',
+        identity: {
+          profile: 'e1',
+          domain: 'agents.example.com',
+          pathSegments: ['agents', 'example'],
+          managedKeys: [
+            { fragment: 'root', role: 'root_control' },
+            { fragment: 'request', role: 'request_signing' },
+          ],
+        },
+      })
+    : await lease.get(identities[0]!.reference)
+
+  const snapshot = await identity.publicIdentity()
+  await identity.sign({
+    purpose: 'authentication',
+    kid: `${snapshot.reference.did}#request`,
+    payload: Buffer.from('canonical application bytes'),
+  })
+}
+```
+
+For HTTP authentication, request `identity:http-auth`, configure an exact origin for that consumer, and call `identity.authenticatedHttp.dispatch(request, transport)`. The caller never receives the signature header patch.
+
+## Modules and cooperation
+
+| Module | Responsibility |
+| --- | --- |
+| `ctx.anpIdentity` | Public multi-DID facade, client leases, catalog, grants, handles, and HTTP dispatch |
+| `./provider` | Opens the native Store and registers exactly one native Provider with Cordis lifecycle ownership |
+| `./provider-api` | Versioned Host-only contract used by an externally bridged native consumer such as AWiki IM Core |
+| `@agent-network-protocol/anp-identity` | Encrypted key custody, DID documents, signing, recovery, and sealed secret handoffs |
+| `dsh-awiki` | AWiki account, messaging, Bearer Token/challenge state, and application workflows |
+
+Mobile applications do not need this DSH package. They can link the ANP Identity Rust crate directly through their native integration while using the same Facade and Host SPI semantics.
+
+## Recovery behavior
+
+The native Store is always the identity truth. On startup:
+
+- a Store identity absent from catalog and journals becomes `Unclaimed` with no grants;
+- a catalog entry absent from the Store is removed;
+- a pending create intent is completed when its Store identity can be identified;
+- a deletion tombstone rolls forward;
+- a corrupt catalog blocks grants and handles. Explicit `recover()` rebuilds entries as `Unclaimed` and never invents authorization.
+
+`recover()` is an exclusive, Store-wide operation. Do not use it as a polling API.
+
+## Development
+
+```bash
+npm install --legacy-peer-deps
+npm run verify
+```
+
+The test suite uses the real native binding for multi-DID, restart, signing, HTTP dispatch, corruption recovery, and tombstone recovery, plus real child processes for catalog locking.
+
+The functional HTTP-signing E2E additionally requires the `dsh` CLI, Node
+`^22.19.0` or `>=24.0.0`, `pnpm`, `uv`, OpenSSL, and the sibling ANP checkout
+expected by the workspace:
+
+```bash
+npm run test:functional
+```
+
+It builds the debug native binding, packs and installs the native package and
+DSH plugins into a temporary real DSH profile, then sends signed GET and POST
+requests to an independent HTTPS process backed by the ANP Python verifier. A
+tampered POST must be rejected. The temporary DSH profile, Store, certificate,
+and tarballs are removed after the run.
+
+Licensed under Apache-2.0.

package/README.zh.md

@@ -0,0 +1,148 @@
+# 面向 DeepSeek Harness 的 ANP Identity
+
+`@agent-network-protocol/dsh-anp-identity` 为 DSH 应用提供共享的多 DID 身份 Store。应用不需要各自实现私钥托管、DID Document 生命周期、崩溃恢复和请求签名。
+
+普通插件通过 `ctx.anpIdentity` 使用精简的 TypeScript Facade。私钥操作由 ANP Identity 原生模块完成；私钥在磁盘上加密保存。DSH catalog 只记录 label、handle 和 consumer grant 等非秘密元数据。
+
+## 它解决什么问题
+
+一个 DSH 安装中可能同时存在多个插件和多个 DID。这个插件统一解决：
+
+- DID 私钥由谁保管，以及某个签名目的应该使用哪类密钥；
+- DID Document 更新如何在进程崩溃或发布结果不确定时恢复；
+- 多个插件如何共用身份，而不让任一普通插件取得私钥；
+- HTTP 请求如何完成身份认证，同时不把可复用 Header patch 交给调用方；
+- 多 DID、通用 handle、consumer grant 和删除保护如何保持一致。
+
+ANP Identity Store 是身份与加密密钥的真值。插件增加事务化的 `catalog-v1`：创建前写 intent，删除前写 tombstone；跨进程修改使用文件锁、generation 检查和原子 rename。异常重启后流程会继续完成，未知身份只会成为无授权的 `Unclaimed`，不会猜测所有者。
+
+## 主要能力
+
+- 多 DID 创建、列举、打开、删除和恢复；
+- 按 purpose 约束的 Ed25519 签名与验签；
+- Origin Proof 签名；
+- 事务化 DID Document Change Session；
+- consumer-scoped lease、grant、label 和唯一 handle；
+- 有上限的 HTTP 认证 dispatcher：只允许配置的精确 HTTPS origin，body 最大 4 MiB，拒绝调用方预置认证 Header，并强制 manual redirect；
+- 独立的 Host Provider lease，供 AWiki IM Core 等可信原生消费者使用。sealed ECDH、sealed 导入导出、enrollment、Root Transfer 和精确 Header patch 只在这个 Host 面存在。
+
+## 它不解决什么
+
+- 它不是 DID Registry、Resolver、发布服务、备份系统或钱包 UI；
+- 它不实现 AWiki 消息、Bearer Token、challenge 重试或 P5 Root Transfer；这些属于 `dsh-awiki` 与 AWiki IM Core；
+- 它不向 Browser、Remote、Agent Tool 或模型暴露 raw ECDH shared secret、Root Key、导入私钥和通用签名工具；
+- consumer 名称是同进程策略与诊断边界，可防误用，但不是针对同一 Node.js 进程内恶意代码的沙箱。
+
+完整边界见 [BOUNDARY.md](./BOUNDARY.md)。
+
+## 安装与配置
+
+```bash
+pnpm add @agent-network-protocol/dsh-anp-identity
+```
+
+本包会安装精确兼容的 ANP Identity wrapper，由 wrapper 自动选择当前平台的预编译原生包；
+用户不需要 Rust 或源码 checkout。Cordis 中先装载 Service，再装载 Provider：
+
+随包发布的 DSH layer 默认向 `@awiki/dsh-plugin` 开放 client 和 Host Provider，确保文档中的
+双插件安装无需额外本地 patch。其他部署可通过
+`DSH_ANP_IDENTITY_ALLOW_CONSUMERS` 与
+`DSH_ANP_IDENTITY_ALLOW_PROVIDER_CONSUMERS` JSON 数组完整替换默认值。
+
+```yaml
+- insert:
+    - id: anp-identity
+      name: '@agent-network-protocol/dsh-anp-identity'
+      config:
+        stateRoot: /var/lib/dsh/anp-identity
+        allowConsumers: ['example/identity-client', '@awiki/dsh-plugin']
+        allowProviderConsumers: ['@awiki/dsh-plugin']
+        httpAllowedOrigins:
+          example/identity-client: ['https://api.example.com']
+
+    - id: anp-identity-provider
+      name: '@agent-network-protocol/dsh-anp-identity/provider'
+      config:
+        stateRoot: /var/lib/dsh/anp-identity
+        rootKeyProvider: keyring
+        rootKeyProviderId: anp-identity/dsh
+```
+
+keyring 的 `rootKeyProviderId` 格式为 `service/account`；env 模式填写环境变量名；injected 模式填写 key id，并且只能通过可信 Host 代码以 Buffer 注入，不能写入 Loader YAML。`local-file` 必须显式启用；如果 Store 与 Root Key 文件被一起复制，攻击者可以离线解密 Store。
+
+## 其他 DSH 插件如何使用
+
+调用插件声明 `inject = ['anpIdentity']`，申请最小 capability，并让 lease 随自己的 Cordis fiber 释放：
+
+```ts
+const lease = await ctx.anpIdentity.acquireClient({
+  consumer: 'example/identity-client',
+  capabilities: ['identity:read', 'identity:create', 'identity:sign'],
+})
+
+const identity = await lease.create({
+  label: 'Example agent',
+  handle: 'example.agent',
+  identity: {
+    profile: 'e1',
+    domain: 'agents.example.com',
+    pathSegments: ['agents', 'example'],
+    managedKeys: [
+      { fragment: 'root', role: 'root_control' },
+      { fragment: 'request', role: 'request_signing' },
+    ],
+  },
+})
+
+const snapshot = await identity.publicIdentity()
+await identity.sign({
+  purpose: 'authentication',
+  kid: `${snapshot.reference.did}#request`,
+  payload: Buffer.from('canonical application bytes'),
+})
+```
+
+HTTP 认证需要申请 `identity:http-auth`，由 Host 为该 consumer 配置精确 origin，然后调用 `identity.authenticatedHttp.dispatch(request, transport)`。普通 consumer 永远拿不到 Header patch。
+
+## 模块协作
+
+| 模块 | 职责 |
+| --- | --- |
+| `ctx.anpIdentity` | 公共多 DID Facade、client lease、catalog、grant、handle 和 HTTP dispatch |
+| `./provider` | 打开原生 Store，并按 Cordis 生命周期注册唯一 Provider |
+| `./provider-api` | 提供给 AWiki IM Core 等外部原生消费者的版本化 Host-only 契约 |
+| `@agent-network-protocol/anp-identity` | 加密密钥托管、DID Document、签名、恢复和 sealed secret handoff |
+| `dsh-awiki` | AWiki 账户、消息、Bearer Token/challenge 状态和应用工作流 |
+
+移动端不依赖这个 DSH 包，可直接链接 ANP Identity Rust crate，同时复用相同的 Facade/Host SPI 语义。
+
+## 恢复语义
+
+- Store 有身份、catalog/journal 没有记录：重建为无 grant 的 `Unclaimed`；
+- catalog 有记录、Store 没有身份：删除 dangling 条目；
+- create intent 未完成：在能够唯一识别 Store 身份时继续提交；
+- deletion tombstone 未完成：继续删除；
+- catalog 损坏：grant 与 handle fail closed。显式执行 `recover()` 后，按 Store 重建为 `Unclaimed`，不会伪造授权。
+
+`recover()` 会获取 Store 级独占锁并执行全量恢复，不应作为轮询 API。
+
+## 开发验证
+
+```bash
+npm install --legacy-peer-deps
+npm run verify
+```
+
+HTTP 签名功能 E2E 还需要 `dsh` CLI、Node `^22.19.0` 或 `>=24.0.0`、
+`pnpm`、`uv`、OpenSSL，以及工作区约定的相邻 ANP checkout：
+
+```bash
+npm run test:functional
+```
+
+该命令会构建 debug native binding，将 native package、DSH 插件和测试
+consumer 打包并安装到临时的真实 DSH profile，再向使用 ANP Python verifier
+的独立 HTTPS 进程发送签名 GET 和 POST；篡改后的 POST 必须被拒绝。运行结束
+后会删除临时 DSH profile、Store、证书和 tarball。
+
+许可证：Apache-2.0。

package/cordis.patch.yml

@@ -0,0 +1,21 @@
+# Host-only ANP Identity service and its native Provider. Apply after the DSH
+# base profile. Keep the Provider after the Service so Cordis injection owns
+# shutdown ordering.
+
+- insert:
+    - id: anp-identity
+      name: '@agent-network-protocol/dsh-anp-identity'
+      config:
+        stateRoot: !!js process.env.DSH_ANP_IDENTITY_STATE_ROOT
+        allowConsumers: !!js JSON.parse(process.env.DSH_ANP_IDENTITY_ALLOW_CONSUMERS ?? '["@awiki/dsh-plugin"]')
+        allowProviderConsumers: !!js JSON.parse(process.env.DSH_ANP_IDENTITY_ALLOW_PROVIDER_CONSUMERS ?? '["@awiki/dsh-plugin"]')
+        httpAllowedOrigins: !!js JSON.parse(process.env.DSH_ANP_IDENTITY_HTTP_ALLOWED_ORIGINS ?? '{}')
+        recoveryOnOpen: true
+
+    - id: anp-identity-provider
+      name: '@agent-network-protocol/dsh-anp-identity/provider'
+      config:
+        stateRoot: !!js process.env.DSH_ANP_IDENTITY_STATE_ROOT
+        rootKeyProvider: !!js process.env.DSH_ANP_IDENTITY_ROOT_KEY_PROVIDER ?? 'keyring'
+        rootKeyProviderId: !!js process.env.DSH_ANP_IDENTITY_ROOT_KEY_PROVIDER_ID ?? 'anp-identity/dsh'
+        keyringFallbackToLocalFile: false

package/examples/third-party-plugin.ts

@@ -0,0 +1,32 @@
+import type { Context } from '@deepseek-ai/cordis'
+import type {} from '@agent-network-protocol/dsh-anp-identity'
+
+export const name = 'anp-identity-third-party-example'
+export const inject = ['anpIdentity']
+
+export async function apply(ctx: Context): Promise<void> {
+  const lease = await ctx.anpIdentity.acquireClient({
+    consumer: 'example/identity-client',
+    capabilities: ['identity:read', 'identity:create', 'identity:sign', 'identity:handle'],
+  })
+  ctx.effect(() => () => lease.dispose(), 'example: ANP Identity client lease')
+  const identity = await lease.create({
+    label: 'Example agent',
+    handle: 'example.agent',
+    identity: {
+      profile: 'e1',
+      domain: 'agents.example.com',
+      pathSegments: ['agents', 'example'],
+      managedKeys: [
+        { fragment: 'root', role: 'root_control' },
+        { fragment: 'request', role: 'request_signing' },
+      ],
+    },
+  })
+  const publicIdentity = await identity.publicIdentity()
+  await identity.sign({
+    purpose: 'authentication',
+    kid: `${publicIdentity.reference.did}#request`,
+    payload: Buffer.from('application-defined canonical bytes'),
+  })
+}