gbz185-sdk 0.1.0

package/docs/CONFORMANCE.md

@@ -0,0 +1,96 @@
+# GB/Z 185 Conformance Verification
+
+This document verifies `gbz185-sdk` against the seven GB/Z 185-2026 agent interconnection documents supplied in this workspace.
+
+The verification scope is SDK-level conformance: types, validation helpers, runtime surfaces, lifecycle flows, and transport extension points. The GB/Z 185 files are guidance documents, so some items are necessarily implemented as adapter interfaces rather than fixed code.
+
+## Result
+
+- Functional domains from GB/Z 185.1: covered.
+- FRAI-01 through FRAI-10: covered by exported coverage constants and runtime/client surfaces.
+- GB/Z 185.2 identity-code structure and validation: covered.
+- GB/Z 185.3 identity, credential, and authentication lifecycle: covered by reference runtime plus production adapter interfaces.
+- GB/Z 185.4 description lifecycle: covered.
+- GB/Z 185.5 discovery service and preset discovery: covered.
+- GB/Z 185.6 interaction models and group message distribution: covered.
+- GB/Z 185.7 tool service and tool access: covered.
+
+Items marked as extension points are not missing SDK functions. They are areas where the standard references governance, UI, CA, network, scheduler, or security infrastructure that must be supplied by the application environment.
+
+## Coverage Matrix
+
+| Standard | Clause | Topic | Status | SDK Surface |
+| --- | --- | --- | --- | --- |
+| GB/Z 185.1 | 5 | Concept model domains | Covered | `createAgentInterconnectRuntime`, `AgentInterconnectRuntime`, `GBZ185_FUNCTIONS` |
+| GB/Z 185.1 | 6.2 | Functional reference architecture function set | Covered | `GBZ185_FUNCTIONS` |
+| GB/Z 185.1 | 6.3 | FRAI-01 through FRAI-10 | Covered | `GBZ185_FRAI_INTERFACES` |
+| GB/Z 185.2 | 5.1-5.6 | Identity code OID/version/provider/requester/serial structure | Covered | `formatIdentityCode`, `parseIdentityCode`, `validateIdentityCode` |
+| GB/Z 185.2 | 6 | Identity-code allocation and management | Covered by reference runtime | `IdentityRegistryRuntime`, `AgentIdentityMaintenance` |
+| GB/Z 185.2 | Appendix B | International identity-code governance | Extension point | `IdentityAccountStore`, `IdentityRegistryRuntime` |
+| GB/Z 185.3 | 5 | Identity-management framework | Covered | `IdentityRegistryRuntime`, `CredentialIssuer`, `CredentialVerifier`, `InterconnectionAuthorizationRuntime` |
+| GB/Z 185.3 | 6 | Registration and evidence verification | Covered by reference runtime | `IdentityRegistryRuntime.register`, `RegisterIdentityInput.evidence` |
+| GB/Z 185.3 | 7 | Account update/lock/unlock/revoke/audit | Covered by reference runtime | `IdentityRegistryRuntime`, `IdentityAuditEvent` |
+| GB/Z 185.3 | 8 | Credential issue/update/lock/unlock/revoke/status | Covered by reference runtime | `CredentialIssuer`, `CredentialStatusStore` |
+| GB/Z 185.3 | 9 | Presentation, verification, assertion, authorization | Covered by reference runtime | `createProcessCredentialPackage`, `CredentialVerifier`, `InterconnectionAuthorizationRuntime` |
+| GB/Z 185.3 | 9.2 | National CA roots, algorithms, immutable audit | Extension point | `CertificateChainVerifier`, `CredentialIssuer`, `CredentialVerifier` |
+| GB/Z 185.4 | 5 | Agent description and skill attributes | Covered | `AgentDescription`, `SkillDescription`, validation helpers |
+| GB/Z 185.4 | 6-8 | Register/review/certificate/publish/change/unpublish/revoke | Covered by reference runtime | `AgentDescriptionRegistry`, `AgentDescriptionMaintenance` |
+| GB/Z 185.5 | 5-6.1 | Discovery service flow | Covered by reference runtime | `DiscoveryService`, `AgentInterconnectClient.discover` |
+| GB/Z 185.5 | 6.2 | Preset/cache/user/well-known discovery | Covered by reference runtime | `PresetDiscoverySource`, `DiscoveryService` |
+| GB/Z 185.5 | 6.1 | API/GUI/LUI query interface | Extension point | `JsonTransport`, `HttpJsonTransport`, `AgentInterconnectClient` |
+| GB/Z 185.6 | 5-6 | Point-to-point/group/hybrid modes | Covered by reference runtime | `InteractionRuntime`, `AgentInteractionMode` |
+| GB/Z 185.6 | 7 | Data/message/task/session models | Covered | `DataItem`, `Message`, `Task`, `Session` |
+| GB/Z 185.6 | 8 | Point-to-point and group message flows | Covered by reference runtime | `InteractionRuntime`, `MessageDistributionRuntime` |
+| GB/Z 185.6 | Appendix A-B | Streaming/notification/collaboration patterns | Extension point | `JsonTransport`, `InteractionRuntime`, `MessageDistributionRuntime` |
+| GB/Z 185.7 | 4 | Tool architecture | Covered | `ToolAccessRuntime`, `ToolRuntime` |
+| GB/Z 185.7 | 5 | Tool list/update/invocation loop | Covered by reference runtime | `ToolAccessRuntime`, `ToolRuntime` |
+| GB/Z 185.7 | 6 | Tool data formats | Covered | `ToolDescriptor`, `ToolRequestData`, `ToolSyncData`, `ToolUpdateData`, `ToolInvokeRequest`, `ToolInvokeResult` |
+
+The same matrix is exported as `GBZ185_CONFORMANCE_MATRIX` for automated checks.
+
+## Automated Verification
+
+The package test suite verifies:
+
+- identity code parse/format/validation and malformed code rejection;
+- description required fields and skill fields;
+- discovery service, preset filtering behavior, undiscoverable filtering, empty-result handling;
+- description review, publication certificate, publish, unpublish, and revoke;
+- point-to-point and group interaction flows;
+- message distribution receipts;
+- tool list acquisition, updates, success, missing tool, and repeated invocation;
+- credential success, expiry, lock, audience mismatch, and tamper rejection;
+- interconnection authorization facade;
+- identity revocation linked to credential revocation;
+- GB/Z 185.1 function-domain and FRAI interface coverage;
+- conformance matrix coverage for all seven standard parts.
+
+Run:
+
+```bash
+pnpm install
+pnpm typecheck
+pnpm test
+pnpm build
+pnpm pack --pack-destination /tmp
+```
+
+Current verified package name:
+
+```text
+gbz185-sdk@0.1.0
+```
+
+## Explicit Adapter Boundaries
+
+The SDK deliberately does not hard-code the following because the standards do not define concrete implementation details or because the responsibility belongs to external governance infrastructure:
+
+- regulator-approved identity registration service governance;
+- international identity-code approval processes;
+- production CA, national algorithm suite, key custody, and certificate-status service;
+- immutable audit-log storage;
+- legal/risk review policy for description registration and publication;
+- GUI/LUI discovery interfaces;
+- fixed REST paths, WebSocket frames, MCP methods, message brokers, schedulers, or callback URLs.
+
+Each of those areas has an exported interface or transport boundary so production systems can provide the required implementation without changing the SDK object model.

package/docs/GITHUB_PAGES.md

@@ -0,0 +1,54 @@
+# GitHub Pages Deployment
+
+This repository is configured to publish the static documentation site from the `site/` directory with GitHub Actions.
+
+## Files
+
+- `.github/workflows/pages.yml`: GitHub Pages workflow.
+- `site/index.html`: documentation home page.
+- `site/api.html`: API overview.
+- `site/conformance.html`: GB/Z 185 conformance page.
+- `site/assets/styles.css`: shared styles.
+
+## Deployment
+
+On every push to `main`, GitHub Actions uploads the `site/` directory and deploys it to GitHub Pages.
+
+Canonical URL for this repository:
+
+```text
+https://blogs.idevlab.dev/gbz185-sdk/
+```
+
+Default GitHub Pages URL:
+
+```text
+https://ichendev.github.io/gbz185-sdk/
+```
+
+The default GitHub Pages URL redirects to the account-level custom domain above.
+
+Manual redeploy:
+
+```bash
+gh workflow run "Deploy GitHub Pages"
+```
+
+Check deployment status:
+
+```bash
+gh run list --workflow "Deploy GitHub Pages"
+gh run watch
+```
+
+## Local Preview
+
+```bash
+python3 -m http.server 4173 --directory site
+```
+
+Open:
+
+```text
+http://localhost:4173/
+```

package/docs/NPM_RELEASE.md

@@ -0,0 +1,107 @@
+# npm Release Checklist
+
+This package is prepared for the public npm package name:
+
+```text
+gbz185-sdk
+```
+
+As of 2026-06-26, `npm view gbz185-sdk` returns `404 Not Found`, so the name is available unless someone publishes it first.
+
+## 1. Account And Registry
+
+```bash
+npm whoami
+npm config get registry
+```
+
+Expected registry:
+
+```text
+https://registry.npmjs.org/
+```
+
+If `npm whoami` returns `E401`, login first:
+
+```bash
+npm login
+```
+
+If the account has 2FA enabled, npm will ask for an OTP during publish.
+
+## 2. Version Check
+
+For the first release, `package.json` is set to `0.1.0`.
+
+Before later releases:
+
+```bash
+npm view gbz185-sdk version dist-tags
+pnpm version patch
+```
+
+Use `patch`, `minor`, or `major` according to the public API change.
+
+## 3. Local Release Gate
+
+Run the same checks that `prepublishOnly` runs:
+
+```bash
+pnpm install --frozen-lockfile
+pnpm typecheck
+pnpm test
+pnpm build
+pnpm example:calendar
+pnpm pack:check
+```
+
+The package should include `dist`, `docs`, `examples`, `README.md`, `LICENSE`, `CHANGELOG.md`, and `package.json`. It should not include `src`, `test`, `site`, `node_modules`, or local tarballs.
+
+## 4. Publish
+
+```bash
+npm publish --access public
+```
+
+`package.json` already includes:
+
+```json
+{
+  "publishConfig": {
+    "access": "public"
+  }
+}
+```
+
+The explicit `--access public` flag is still recommended for the first publish.
+
+## 5. Post-Publish Smoke Test
+
+After npm confirms publication:
+
+```bash
+npm view gbz185-sdk version dist-tags
+
+mkdir -p /tmp/gbz185-sdk-npm-smoke
+cd /tmp/gbz185-sdk-npm-smoke
+npm init -y
+npm install gbz185-sdk
+node --input-type=module -e "import { formatIdentityCode, validateIdentityCode } from 'gbz185-sdk'; const id = formatIdentityCode({ registrationServiceProvider: 'A1', registrationRequester: 'REQ001', ontologySerial: 'CALENDAR', instanceSerial: '1' }); console.log(id, validateIdentityCode(id));"
+```
+
+Expected output includes:
+
+```text
+1.2.156.3088.1.A1.REQ001.CALENDAR.1 true
+```
+
+## 6. Git Tag
+
+After a successful publish:
+
+```bash
+git tag v0.1.0
+git push origin v0.1.0
+```
+
+For later versions, tag the exact published version.

package/docs/SDK_GUIDE.md

@@ -0,0 +1,439 @@
+# GB/Z 185 SDK Guide
+
+This guide explains how the SDK maps GB/Z 185-2026 into TypeScript APIs and how to use the reference runtime.
+
+## Install
+
+```bash
+npm install gbz185-sdk
+```
+
+The package is ESM-only and supports Node.js `>=20`. It also works with `pnpm add gbz185-sdk` and `yarn add gbz185-sdk`.
+
+## 1. Runtime Shape
+
+The SDK is organized around the seven GB/Z 185 parts:
+
+| GB/Z 185 Part | SDK Surface |
+| --- | --- |
+| 185.1 General architecture | `createAgentInterconnectRuntime()` wires the identity, description, discovery, interaction, and tool domains. |
+| 185.2 Identity code | `formatIdentityCode`, `parseIdentityCode`, `validateIdentityCode`. |
+| 185.3 Identity management | `IdentityRegistryRuntime`, `CredentialIssuer`, `CredentialVerifier`, process credential packages, authentication assertions. |
+| 185.4 Agent description | `AgentDescription`, `SkillDescription`, `AgentDescriptionRegistry`. |
+| 185.5 Agent discovery | `DiscoveryService`, `DiscoveryQuery`, `DiscoveryResult`, preset discovery sources. |
+| 185.6 Agent interaction | `Session`, `Task`, `Message`, `DataItem`, `InteractionRuntime`. |
+| 185.7 Tool invocation | `ToolDescriptor`, `ToolRuntime`, tool list sync, tool updates, tool invocation results. |
+
+The default runtime is in-memory and in-process. It is intended for local development, tests, examples, and protocol experiments.
+
+## 1.1 Complete Function Coverage
+
+GB/Z 185.1 defines function domains in the agent domain, management service domain, interconnection service domain, and resource access domain. The SDK exposes each function domain as a runtime, facade, or interface.
+
+| Domain | Standard Function | SDK Surface |
+| --- | --- | --- |
+| Agent domain | Agent identity maintenance | `AgentIdentityMaintenance` |
+| Agent domain | Agent description maintenance | `AgentDescriptionMaintenance` |
+| Agent domain | Agent interconnection authorization | `InterconnectionAuthorizationRuntime` |
+| Agent domain | Agent interaction | `InteractionRuntime` |
+| Agent domain | Tool access | `ToolAccessRuntime` |
+| Management service domain | Agent identity management | `IdentityRegistryRuntime` |
+| Management service domain | Agent credential management | `CredentialIssuer` / `DevelopmentCredentialIssuer` |
+| Management service domain | Agent identity authentication | `CredentialVerifier` / `DevelopmentCredentialVerifier` |
+| Interconnection service domain | Agent description management | `AgentDescriptionRegistry` |
+| Interconnection service domain | Agent discovery | `DiscoveryService` |
+| Interconnection service domain | Message distribution | `MessageDistributionRuntime` |
+| Resource access domain | Tool service | `ToolRuntime` |
+
+The SDK also exports `GBZ185_FUNCTIONS` and `GBZ185_FRAI_INTERFACES` for machine-readable coverage checks. The FRAI constants cover `FRAI-01` through `FRAI-10`.
+
+For a clause-level verification matrix, see `docs/CONFORMANCE.md` or import `GBZ185_CONFORMANCE_MATRIX`.
+
+## 2. Identity Codes
+
+GB/Z 185.2 uses an OID-style identity code. This SDK fixes the standard prefix and current version:
+
+- OID prefix: `1.2.156.3088`
+- Version: `1`
+- Registration service provider: up to 6 base36 characters
+- Registration requester: up to 6 base36 characters
+- Ontology serial: up to 9 base36 characters
+- Instance serial: up to 9 base36 characters
+
+```ts
+import { formatIdentityCode, parseIdentityCode, validateIdentityCode } from "gbz185-sdk";
+
+const agentId = formatIdentityCode({
+  registrationServiceProvider: "A1",
+  registrationRequester: "REQ001",
+  ontologySerial: "CALENDAR",
+  instanceSerial: "1"
+});
+
+console.log(agentId);
+// 1.2.156.3088.1.A1.REQ001.CALENDAR.1
+
+console.log(validateIdentityCode(agentId));
+console.log(parseIdentityCode(agentId));
+```
+
+## 3. Register And Publish An Agent
+
+Use `createAgentInterconnectRuntime()` when you want all in-memory services connected through the default `InProcessJsonTransport`.
+
+```ts
+import { createAgentInterconnectRuntime, type AgentDescription } from "gbz185-sdk";
+
+const runtime = createAgentInterconnectRuntime();
+
+const registration = await runtime.client.registerIdentity({
+  delegatorId: "example-org",
+  subject: "Calendar Agent",
+  registrationServiceProvider: "A1",
+  registrationRequester: "REQ001",
+  ontologySerial: "CALENDAR",
+  instanceSerial: "1",
+  issueCredential: true,
+  credentialAudience: ["requester-agent"],
+  credentialScope: ["agent:interact", "tool:invoke"]
+});
+
+const description: AgentDescription = {
+  agentId: registration.account.id,
+  name: "Calendar Agent",
+  version: "1.0.0",
+  description: "Creates calendar events",
+  provider: "Example Org",
+  capabilities: { asyncMessages: true },
+  defaultInputTypes: ["text", "json"],
+  defaultOutputTypes: ["json"],
+  skills: [
+    {
+      skillId: "schedule.add",
+      skillName: "add_schedule",
+      skillDescription: "Add one calendar schedule item",
+      tags: ["calendar", "schedule"],
+      inputTypes: ["text", "json"],
+      outputTypes: ["json"]
+    }
+  ]
+};
+
+await runtime.client.registerDescription(description);
+await runtime.client.publishDescription(description.agentId);
+```
+
+The full description lifecycle also includes review, publication certificate issuance, unpublish, and revoke:
+
+```ts
+await runtime.client.reviewDescription(description.agentId, {
+  reviewerId: "description-manager",
+  approved: true,
+  riskLevel: "low"
+});
+
+await runtime.client.issuePublicationCertificate(description.agentId, {
+  issuer: "description-manager",
+  publicKeyDigest: "sha256:..."
+});
+
+await runtime.client.publishDescriptionWithInfo(description.agentId, {
+  regions: ["CN"],
+  openBeta: false,
+  paid: false,
+  permissionRequirements: ["calendar.write"]
+});
+
+await runtime.client.unpublishDescription(description.agentId);
+await runtime.client.revokeDescription(description.agentId, "retired");
+```
+
+## 4. Discovery
+
+Discovery searches published descriptions and optional preset sources. By default, descriptions marked `discoverable: false` are filtered out.
+
+```ts
+const results = await runtime.client.discover({
+  text: "calendar schedule",
+  requiredSkills: ["schedule.add"],
+  inputTypes: ["text"],
+  outputTypes: ["json"],
+  requireAvailable: true
+});
+
+const target = results[0]?.description;
+```
+
+`DiscoveryQuery` supports:
+
+- `text`
+- `agentId`
+- `name`
+- `requiredSkills`
+- `tags`
+- `inputTypes`
+- `outputTypes`
+- `includeUndiscoverable`
+- `requireAvailable`
+- `limit`
+
+## 5. Interaction
+
+GB/Z 185.6 is represented as:
+
+- `Session`: a multi-agent interaction process
+- `Task`: a work unit inside a session
+- `Message`: an exchange unit
+- `DataItem`: the message payload unit
+
+```ts
+const session = await runtime.client.createSession({
+  mode: "point_to_point",
+  sender: { agentId: "requester-agent-id" },
+  receivers: [{ agentId: target.agentId, mode: "point_to_point" }]
+});
+
+const task = await runtime.client.submitTask({ sessionId: session.id });
+
+await runtime.client.sendMessage({
+  senderRole: "service",
+  senderId: target.agentId,
+  sessionId: session.id,
+  taskId: task.id,
+  artifact: "work_result",
+  final: true,
+  lastChunk: true,
+  dataItems: [
+    {
+      type: "application/json",
+      metadata: {},
+      payload: { ok: true }
+    }
+  ]
+});
+```
+
+Supported interaction modes are:
+
+- `point_to_point`
+- `group`
+- `hybrid`
+
+For group mode, use `MessageDistributionRuntime` or the client `distributeMessage` helper. The distribution service records delivery receipts and writes the source message into the interaction runtime.
+
+```ts
+const receipts = await runtime.client.distributeMessage({
+  senderRole: "requester",
+  senderId: "requester-agent-id",
+  sessionId: session.id,
+  dataItems: [{ type: "text/plain", metadata: {}, payload: "hello group" }]
+});
+```
+
+## 6. Tool Invocation
+
+Register tools with `ToolRuntime`, then invoke them through the client.
+
+```ts
+await runtime.toolRuntime.registerTool(
+  {
+    toolId: "calendar.add",
+    toolName: "add_schedule",
+    toolDescription: "Add one calendar event",
+    toolVersion: "1.0.0",
+    toolInputParam: { date: "string", time: "string", event: "string" },
+    toolOutputParam: { eventId: "string", accepted: "boolean" }
+  },
+  (input) => ({
+    eventId: `evt-${input.date}-${input.time}`,
+    accepted: true
+  })
+);
+
+const toolResult = await runtime.client.invokeTools({
+  sessionId: session.id,
+  toolInvokeList: [
+    {
+      toolId: "calendar.add",
+      toolVersion: "1.0.0",
+      toolInputParam: {
+        date: "2026-06-26",
+        time: "10:00",
+        event: "GB/Z 185 SDK review"
+      }
+    }
+  ]
+});
+```
+
+Tool failures are returned as result items instead of throwing for the whole batch. For example, a missing tool returns `statusCode: "TOOL_NOT_FOUND"` and `ok: false`.
+
+The agent-side tool-access facade wraps the resource-side tool service:
+
+```ts
+const tools = await runtime.toolAccess.getToolList();
+const updates = await runtime.toolAccess.syncToolUpdates();
+const rounds = await runtime.toolAccess.invokeUntilComplete({
+  initialRequest: {
+    sessionId: session.id,
+    toolInvokeList: [
+      {
+        toolId: "calendar.add",
+        toolVersion: "1.0.0",
+        toolInputParam: { date: "2026-06-26", time: "10:00", event: "review" }
+      }
+    ]
+  },
+  isComplete: (result) => result.toolResultList.every((item) => item.ok),
+  nextRequest: (result) => ({
+    sessionId: session.id,
+    toolInvokeList: []
+  })
+});
+```
+
+## 7. Credential Verification
+
+The credential layer is X.509-first by interface:
+
+- `CertificateChainVerifier`
+- `CredentialStatusStore`
+- `CredentialIssuer`
+- `CredentialVerifier`
+
+The bundled `DevelopmentCredentialIssuer` uses Node.js `crypto` with Ed25519 keys so local flows can run without an external CA. It can optionally verify a supplied PEM certificate through `NodeX509CertificateChainVerifier`, but it is not a production CA implementation.
+
+```ts
+import {
+  DevelopmentCredentialIssuer,
+  DevelopmentCredentialVerifier,
+  InMemoryCredentialRepository,
+  InMemoryCredentialStatusStore,
+  createProcessCredentialPackage
+} from "gbz185-sdk";
+
+const repository = new InMemoryCredentialRepository();
+const statusStore = new InMemoryCredentialStatusStore();
+const issuer = new DevelopmentCredentialIssuer(repository, statusStore);
+const verifier = new DevelopmentCredentialVerifier(statusStore);
+
+const issued = await issuer.issueCredential({
+  agentId: "agent-id",
+  subject: "Requester Agent",
+  audience: ["service-agent"],
+  scope: ["agent:interact"]
+});
+
+const presentation = createProcessCredentialPackage({
+  credential: issued.credential,
+  privateKeyPem: issued.privateKeyPem,
+  audience: "service-agent",
+  scope: ["agent:interact"],
+  payload: { action: "connect" }
+});
+
+const assertion = await verifier.verifyPresentation({
+  package: presentation,
+  expectedAudience: "service-agent",
+  requiredScope: ["agent:interact"]
+});
+```
+
+Agent interconnection authorization is available as a higher-level facade:
+
+```ts
+const auth = runtime.interconnectionAuthorization;
+const presentation = auth.createPresentation({
+  credential: issued.credential,
+  privateKeyPem: issued.privateKeyPem,
+  audience: "service-agent",
+  scope: ["agent:interact"]
+});
+
+const decision = await auth.authenticatePeer(presentation, {
+  expectedAudience: "service-agent",
+  requiredScope: ["agent:interact"]
+});
+```
+
+Identity account lock/unlock/revoke operations are linked to associated credential states in the reference runtime. Revoking an identity account also revokes credentials issued through that account.
+
+For production, replace the development issuer/verifier/status store with implementations backed by your CA, key custody, certificate status service, audit log, and persistence layer.
+
+## 8. Transport
+
+The SDK does not define REST paths or WebSocket frames. Every client method delegates to:
+
+```ts
+interface JsonTransport {
+  request<TRequest, TResponse>(operation: string, payload: TRequest): Promise<TResponse>;
+}
+```
+
+Bundled transports:
+
+- `InProcessJsonTransport`: local runtime and tests.
+- `HttpJsonTransport`: POSTs `{ operation, payload }` to a configured endpoint.
+
+Operation names used by `createAgentInterconnectRuntime()`:
+
+- `identity.register`
+- `identity.get`
+- `identity.issueCredential`
+- `identity.lock`
+- `identity.unlock`
+- `identity.revoke`
+- `description.register`
+- `description.review`
+- `description.issuePublicationCertificate`
+- `description.publish`
+- `description.unpublish`
+- `description.revoke`
+- `discovery.discover`
+- `interaction.createSession`
+- `interaction.submitTask`
+- `interaction.sendMessage`
+- `interaction.distributeMessage`
+- `tool.list`
+- `tool.updates`
+- `tool.invoke`
+
+## 9. Local Verification
+
+```bash
+pnpm install
+pnpm typecheck
+pnpm test
+pnpm build
+pnpm example:calendar
+pnpm pack --pack-destination /tmp
+```
+
+The test suite covers:
+
+- identity code parse/format/validation
+- description validation
+- discovery filtering and matching
+- session/task/message flows
+- tool list, update, success, and missing-tool failures
+- credential success, expiry, lock, audience mismatch, and tamper rejection
+- full smoke flow: register -> publish -> discover -> session -> tool invocation -> final message
+- full GB/Z 185.1 function-domain coverage constants and FRAI-01 through FRAI-10
+- description review/publication certificate/unpublish/revoke lifecycle
+- group-mode message distribution
+- tool-access facade and iterative invocation
+- identity revocation linked to credential revocation
+
+## 10. Boundaries
+
+This SDK is a reference implementation and developer toolkit. It intentionally does not decide:
+
+- production CA policy
+- national cryptographic algorithm suite
+- HTTP route shape
+- WebSocket event shape
+- MCP adapter semantics
+- database schema
+- distributed message broker behavior
+
+Those should be added as application-specific adapters on top of the stable TypeScript interfaces.