@tablestore/tablestore-agent-cli 0.3.1 → 0.4.1

package/dist/dashboard-runtime/node_modules/@tablestore/agent-storage/CHANGELOG.md

@@ -0,0 +1,175 @@
+# Changelog
+
+All notable changes to `@tablestore/agent-storage` are documented here.
+
+## 0.0.13
+
+Breaking realignment of the eight item (file-memory) APIs with the service
+contract (Claude-aligned). The wire format changed; there is no forward
+compatibility with 0.0.12 item payloads. Runtime behaviour is unchanged -
+requests are still passed through as-is and every 2xx is accepted (ranged
+`deleteItem` now answers HTTP 200).
+
+### Changed
+
+- All item requests: `view` (`'basic' | 'full'`) replaces `includeContent`.
+  The default is `'basic'`, so `getItem` no longer returns `content` unless
+  `view: 'full'` is passed (the old default included content).
+- `getItem` and exact `deleteItem`: exactly one of `itemId` or `path` is
+  required; providing both is invalid. Both modes require a fully specified
+  four-part scope.
+- `addItem`: paths must start with `/` (the service no longer adds it); the
+  path limit is 1024 bytes (was 800).
+- `updateItem`: a full four-part scope is required, and required `itemId` is
+  the only source address. At least one of `content` or `path` is required and
+  both may be combined atomically; `path` is the target path. `newPath` is
+  removed, as is the empty-mutation no-op. Optimistic concurrency now uses
+  `precondition?: ItemPrecondition` with `expectedVersionId` instead of
+  `expectedSha256`; `overwrite` applies only when a target `path` is present,
+  while `sessionId` and `view` remain optional.
+- `deleteItem`: wildcard scopes trigger an asynchronous ranged delete,
+  answered immediately with **HTTP 200**
+  `{ type, taskId, status: 'pending' }`; optional segment-aligned `pathPrefix`
+  and `sessionId` narrow/annotate the range, while `itemId`, `path`, and
+  `precondition` are forbidden. Exact deletes accept optional
+  `precondition?: ItemPrecondition` (`expectedVersionId`) and `sessionId`, and
+  return `{ type, itemId, deleted: true }`.
+- `listItems`: new `depth` (0/1; depth 1 rolls deeper directories up into
+  `memoryfile_prefix` entries) and `view`; `limit` defaults to 20, max 100
+  (was 100/500), capped at 20 with `view: 'full'`; `pathPrefix` must start
+  and end with `/`.
+- `listItemVersions`: scope-level listing — `itemId` is now an optional
+  filter, `path` is removed, and `sessionId`/`apiKeyId` (mutually exclusive),
+  `createdAtGte`/`createdAtLte` (RFC3339) and `view` filters are added.
+- `getItemVersion` / `redactItemVersion`: addressed by the self-contained
+  `versionId` only; `itemId` and `versionSeq` are removed. `getItemVersion`
+  gains `view`.
+- `Item`: adds `scope` (always echoed) and `latestVersionId`.
+- `ItemVersion`: removes `versionSeq` and `sessionId`; adds `scope` and typed
+  actor `createdBy`; `redactedBy` is now a typed actor object
+  (`{ actorType, actorId }`) instead of a string.
+- `listItems`, `listItemVersions`, and ranged `deleteItem` may use the
+  left-prefix `*` wildcard (`appId`/`tenantId` exact; once a segment is `*`,
+  all following segments must be `*`); each scope field is capped at 128
+  bytes.
+
+### Added
+
+- `ITEM_TYPE_MEMORY_FILE_PREFIX` constant, `ItemView`, `ItemActor`, and
+  `ItemPrecondition` types, `ItemListFileEntry` / `ItemListPrefixEntry` /
+  `ItemListEntry` for typed `listItems` entries, and
+  `DeleteItemSingleResponse` / `DeleteItemRangedResponse` (with
+  `DeleteItemResponse` now their union).
+
+## 0.0.12
+
+Type-declaration and packaging-metadata release: the request/response models
+were realigned with the service contract. **No runtime behaviour changed**, no
+dependencies were added or removed, and the module layout (`exports`, `types`)
+is unchanged.
+
+### Added
+
+Memory store configuration:
+
+- `CreateMemoryStoreRequest`: `storageMode` (`'ots' | 'file+ots' | 'filemem'`,
+  defaults to `ots`, immutable after creation) and `extractInstructions`.
+- `UpdateMemoryStoreRequest`: `extractInstructions`. Both patchable fields now
+  accept `null` / `UNSET` alongside `string`, matching the PATCH semantics
+  already used by `UpdateKnowledgeBaseRequest` — omitted means "leave
+  unchanged", `''` means "clear".
+- `MemoryStoreInfo`: `storageMode` and `extractInstructions`.
+- `MemoryStoreStorageMode` type.
+
+Memory search:
+
+- `SearchMemoriesRequest`: `contextScope`, `minSimilarity` and
+  `includeEvidence`, all serialized by `toJSONRequest()`.
+- `SearchHit`: `similarity`, `rankingScore` and `rankingSignals`, plus the new
+  `RankingSignals` type.
+
+Dream:
+
+- `CreateMemoryDreamTaskRequest`: `taskType` and `incremental`.
+- `ListMemoryDreamActionsRequest`: `scope` and `actionType`, enabling the
+  scope-based query mode for emitted extracts. `dreamId` is now optional
+  because the two modes are mutually exclusive.
+- `DreamTaskType`, `DreamExtractActionType`, `DreamExtractSpec`,
+  `DreamConfidenceThresholdKey` and `DreamConfidenceThresholds` types.
+- `DreamMemorySpec`: `title`, `keywords`, `effectiveAt` and `timePrecision`,
+  completing the eight fields the service emits.
+- `DreamActionRecord`: `newExtract`.
+- `DreamTask`: `taskType`, `incremental`, `processedThroughMs` and
+  `skippedByReason`.
+- `DreamTaskInputSummary`: `incremental`.
+- `DreamTaskActionStats`: `skippedByReason`.
+- `DreamTaskSummary`: `taskType`, `processedThroughMs` and `instructions`.
+- `CancelMemoryDreamTaskResponse`: `taskType`.
+
+Items:
+
+- `MAX_ITEM_CONTENT_BYTES`, `MAX_ITEM_PATH_BYTES` and `MAX_ITEMS_PER_SCOPE`
+  constants.
+
+### Changed
+
+- `DreamActionType` gained `EMIT_SKILL` and `EMIT_PROFILE` (5 → 7 values).
+- `DreamSkippedReason` gained `superseded_by_skill`, `superseded_by_profile`,
+  `noop_nothing_to_apply` and `conflicting_action` (8 → 12 values).
+- `DreamApplyActionResult.status` is now `DreamActionStatus | 'not_found'`.
+- `ListMemoryStoreMessagesRequest` and `ListMemoryStoreRequestsRequest` accept
+  `number | string` timestamps; these two endpoints take either Unix
+  milliseconds or RFC3339, while every dream endpoint takes Unix milliseconds
+  only.
+- Extensive JSDoc covering field limits, defaults, enum values, mutually
+  exclusive parameters and error codes.
+
+### Compatibility
+
+No field was renamed, removed, or changed from optional to required. Three
+declarations became strictly wider unions and can surface in an exhaustive
+`switch` or in an assignment to the narrower type:
+
+- `DreamActionType` and `DreamSkippedReason` have more members.
+- `DreamApplyActionResult.status` includes `'not_found'`.
+
+`DreamConfidenceThresholds` deliberately keeps a `Record<string, number>` arm
+so dynamically built threshold maps continue to type-check; only `add`,
+`update` and `merge` are accepted by the service.
+
+### Packaging
+
+- Declared `license: "Apache-2.0"`, matching `rust/Cargo.toml` and the
+  repository `LICENSE`; earlier releases published with no license field.
+- Added `repository`, `homepage` and `bugs` pointing at
+  `aliyun/tablestore-agent-storage-sdk`, and `keywords`.
+- Added `publishConfig` (`registry: https://registry.npmjs.org`,
+  `access: public`) so the package always targets the public registry
+  regardless of the local npm mirror configuration.
+- `CHANGELOG.md` is now shipped inside the tarball via `files`.
+
+## 0.0.11
+
+**Breaking (introduced in this release, commit `88f0171`):** the file-memory
+API surface was renamed from `FileMemory*` to `Item*`, replacing nine
+`*FileMemory` client methods with eight item methods. Code written against
+0.0.9 or 0.0.10 must be updated:
+
+- `createFileMemory` → `addItem`
+- `listFileMemories` → `listItems`
+- `readFileMemory` → `getItem`, and `statFileMemory` → `getItem` with
+  `includeContent: false`
+- `updateFileMemory` → `updateItem`, and `renameFileMemory` → `updateItem`
+  with `newPath`
+- `deleteFileMemory` → `deleteItem`
+- `listFileMemoryVersions` → `listItemVersions`
+- `getFileMemoryVersion` → `getItemVersion`
+- `redactItemVersion` was added (no 0.0.10 equivalent)
+
+Types were renamed to match (`FileMemory` → `Item`, `FileMemoryVersion` →
+`ItemVersion`, `CreateFileMemoryRequest` → `AddItemRequest`, …), and the wire
+fields changed too: `memoryId` → `itemId`, `memoryVersionId` → `versionId`,
+and the list response key `memories` → `items`. Requests now extend
+`ItemScopedRequest` and carry `type: 'memoryfile'`, which the client fills in
+when omitted. The old `*FileMemory` routes were removed from the service and
+return `404`.

package/dist/dashboard-runtime/node_modules/@tablestore/agent-storage/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 2026 Alibaba Cloud
+
+   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/dist/dashboard-runtime/node_modules/@tablestore/agent-storage/README.md

@@ -0,0 +1,203 @@
+# Tablestore Agent Storage TypeScript SDK
+
+This package contains the TypeScript SDK for Tablestore agent storage, including knowledge-base and memory APIs.
+
+## Entrypoints
+
+- `src/index.ts`: cross-runtime core client
+- `src/node.ts`: Node-only client with local file upload support
+
+## Usage
+
+ES modules:
+
+```ts
+import { AgentStorageClient } from '@tablestore/agent-storage';
+
+const client = new AgentStorageClient({
+  endpoint: 'https://your-instance.cn-beijing.ots.aliyuncs.com',
+  instanceName: 'your-instance',
+  accessKeyId: process.env.OTS_ACCESS_KEY_ID!,
+  accessKeySecret: process.env.OTS_ACCESS_KEY_SECRET!,
+});
+```
+
+```ts
+import { NodeAgentStorageClient } from '@tablestore/agent-storage/node';
+
+const client = new NodeAgentStorageClient({
+  endpoint: 'https://your-instance.cn-beijing.ots.aliyuncs.com',
+  instanceName: 'your-instance',
+  accessKeyId: process.env.OTS_ACCESS_KEY_ID!,
+  accessKeySecret: process.env.OTS_ACCESS_KEY_SECRET!,
+  ossEndpoint: 'https://oss-cn-beijing.aliyuncs.com',
+  ossBucketName: 'tantan-source',
+});
+```
+
+CommonJS:
+
+```js
+const { AgentStorageClient } = require('@tablestore/agent-storage');
+const { NodeAgentStorageClient } = require('@tablestore/agent-storage/node');
+```
+
+## Signatures
+
+- default: `v2`
+- optional: `v4` with `region`
+
+## Input Modes
+
+All APIs accept:
+
+- plain JSON requests
+- model instances with `toJSONRequest()`
+
+## API Surface
+
+- `AgentStorageClient`: cross-runtime client for knowledge-base and memory APIs
+- `NodeAgentStorageClient`: Node client that adds OSS-backed document upload
+
+Memory APIs include:
+
+- memory store lifecycle: `createMemoryStore`, `getMemoryStore`, `listMemoryStores`, `updateMemoryStore`, `deleteMemoryStore`
+- memory CRUD/search: `addMemories`, `searchMemories`, `listMemories`, `getMemory`, `updateMemory`, `deleteMemory`
+- audit/message queries: `listMemoryStoreMessages`, `listMemoryStoreRequests`
+- ingest task tracking: `getMemoryTask`, `listMemoryTasks`
+- scope discovery: `listMemoryStoreScopes`
+- memory dream tasks: `createMemoryDreamTask`, `getMemoryDreamTask`, `listMemoryDreamTasks`, `cancelMemoryDreamTask`
+- memory dream actions: `listMemoryDreamActions`, `applyMemoryDreamActions`
+- items (file memory): `addItem`, `listItems`, `getItem`, `updateItem`, `deleteItem`, `listItemVersions`, `getItemVersion`, `redactItemVersion`
+
+## Storage modes
+
+A memory store's `storageMode` is chosen at `createMemoryStore` time and cannot
+be changed afterwards:
+
+- `ots` (default): structured memory only. Item APIs are rejected with `400`.
+- `filemem`: writable, versioned memory files, reached through the item APIs.
+- `file+ots`: structured memory plus a **read-only** projected file tree. Item
+  reads work, item writes return `409 READ_ONLY_STORE`, and the version APIs
+  return `400`.
+
+```ts
+await client.createMemoryStore({
+  memoryStoreName: 'agent_memory',
+  storageMode: 'filemem',
+  // description is capped at 1024 bytes; extractInstructions at 4096 runes
+  extractInstructions: '只抽取与订单相关的事实',
+});
+```
+
+`updateMemoryStore` is a strict PATCH and accepts only `description` and
+`extractInstructions`. Omitting a field leaves it unchanged; sending `''`
+clears it.
+
+`listMemoryStores` returns only `memoryStoreName` per entry — call
+`getMemoryStore` per store to read `storageMode`, `description` or
+`extractInstructions`.
+
+## Items (file memory)
+
+All eight item actions carry `"type": "memoryfile"`, which the SDK fills in
+automatically. `addItem`, `getItem`, `updateItem`, exact `deleteItem`,
+`getItemVersion`, and `redactItemVersion` require a **fully specified
+four-part scope**. Only `listItems`, `listItemVersions`, and ranged
+`deleteItem` accept the left-prefix `*` wildcard: `appId` and `tenantId` stay
+exact, and once a segment is `*` every segment after it must be `*` too.
+
+```ts
+const scoped = {
+  memoryStoreName: 'agent_memory',
+  scope: { appId: 'a', tenantId: 't', agentId: 'ag', runId: 'r' },
+};
+
+await client.addItem({ ...scoped, path: '/notes/a.md', content: 'hello' });
+
+// Get and exact delete require exactly one address: itemId or path.
+// view defaults to 'basic' (metadata only); use 'full' for content.
+const item = await client.getItem({ ...scoped, path: '/notes/a.md', view: 'full' });
+
+// Update requires itemId plus content, a target path, or both.
+const updated = await client.updateItem({
+  ...scoped,
+  itemId: item.itemId,
+  content: 'updated',
+  path: '/notes/b.md', // Target path; itemId is the source address.
+  precondition: { expectedVersionId: item.latestVersionId },
+  view: 'full',
+});
+
+await client.deleteItem({
+  ...scoped,
+  itemId: updated.itemId,
+  precondition: { expectedVersionId: updated.latestVersionId },
+});
+
+const listed = await client.listItems({ ...scoped, pathPrefix: '/notes/', depth: 1 });
+// listed.readOnly is true only for file+ots projections; omitted otherwise.
+// depth: 1 rolls deeper directories up into entries typed 'memoryfile_prefix'.
+
+// Ranged delete: wildcard scope and no itemId/path/precondition. The service
+// immediately returns HTTP 200 with { type, taskId, status: 'pending' }.
+const task = await client.deleteItem({
+  memoryStoreName: 'agent_memory',
+  scope: { appId: 'a', tenantId: 't', agentId: '*', runId: '*' },
+  pathPrefix: '/notes/',
+});
+```
+
+Service-enforced limits: content ≤ 100 KiB (`413 PAYLOAD_TOO_LARGE`), path
+≤ 1024 bytes, `limit` defaults to 20 with a maximum of 100 (capped at 20
+when `view: 'full'`). Paths must start with `/` (no longer auto-added), be
+valid UTF-8, and reject `.`/`..`/empty segments. Every item/version response
+echoes its `scope`, items carry a `latestVersionId` head pointer, and version
+attribution uses typed actors (`createdBy` / `redactedBy` objects with
+`actorType` and `actorId`).
+
+Versions are addressed by the self-contained `versionId` alone —
+`getItemVersion` and `redactItemVersion` take no `itemId`/`versionSeq`.
+`listItemVersions` is scope-level: besides `itemId` it supports `sessionId`,
+`apiKeyId`, `createdAtGte`/`createdAtLte` (RFC3339) and `operation` filters.
+
+`redactItemVersion` irreversibly clears one historical version's content and
+path. It is idempotent and first-wins; afterwards `getItemVersion` still
+returns `200` for that version but never its content.
+
+## Dream tasks
+
+`taskType` defaults to `memory`. Use `skill` or `profile` to emit extracts
+instead of memory mutations — those task types reject `applyMode` with a `400`,
+and their `EMIT_SKILL` / `EMIT_PROFILE` actions cannot be applied.
+
+`listMemoryDreamActions` has two mutually exclusive modes: pass `dreamId` to
+list one run's actions, or pass `scope` plus `actionType`
+(`EMIT_SKILL` / `EMIT_PROFILE`) to list emitted extracts across runs. Sending
+both or neither is a `400`.
+
+Dream `minTimestamp` / `maxTimestamp` accept **Unix milliseconds only**;
+`listMemoryStoreMessages` and `listMemoryStoreRequests` additionally accept
+RFC3339.
+
+## Tests
+
+Run unit tests:
+
+```bash
+npm run test:unit
+```
+
+Run e2e tests:
+
+```bash
+OTS_ENDPOINT=https://your-instance.cn-beijing.ots.aliyuncs.com \
+OTS_ACCESS_KEY_ID=your-ak \
+OTS_ACCESS_KEY_SECRET=your-sk \
+OTS_INSTANCE_NAME=your-instance \
+OTS_REGION=cn-beijing \
+OTS_SIGN_VERSION=v2 \
+OSS_ENDPOINT=https://oss-cn-beijing.aliyuncs.com \
+OSS_BUCKET_NAME=tantan-source \
+npm run test:e2e
+```

package/dist/dashboard-runtime/node_modules/@tablestore/agent-storage/dist/cjs/package.json

@@ -0,0 +1,3 @@
+{
+  "type": "commonjs"
+}

package/dist/dashboard-runtime/node_modules/@tablestore/agent-storage/dist/cjs/src/core/auth/request-context.js

@@ -0,0 +1,21 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.RequestContext = void 0;
+class RequestContext {
+    #credentials;
+    #signDate;
+    constructor(credentials, signDate) {
+        this.#credentials = credentials;
+        this.#signDate = signDate;
+    }
+    getCredentials() {
+        return this.#credentials;
+    }
+    getSignDate() {
+        return this.#signDate;
+    }
+    setSignDate(signDate) {
+        this.#signDate = signDate;
+    }
+}
+exports.RequestContext = RequestContext;

package/dist/dashboard-runtime/node_modules/@tablestore/agent-storage/dist/cjs/src/core/auth/sign-base.js

@@ -0,0 +1,70 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.SignBase = void 0;
+exports.hmacSha1Base64 = hmacSha1Base64;
+exports.hmacSha256Base64 = hmacSha256Base64;
+exports.sortAndEncodeQuery = sortAndEncodeQuery;
+const node_crypto_1 = require("node:crypto");
+const client_error_js_1 = require("../errors/client-error.js");
+const OTS_HEADER_PREFIX = 'x-ots-';
+function hmacSha1Base64(signingKey, content) {
+    return (0, node_crypto_1.createHmac)('sha1', signingKey).update(content, 'utf8').digest('base64');
+}
+function hmacSha256Base64(signingKey, content) {
+    return (0, node_crypto_1.createHmac)('sha256', signingKey).update(content, 'utf8').digest('base64');
+}
+function sortAndEncodeQuery(queryString) {
+    if (!queryString) {
+        return '';
+    }
+    const pairs = [...new URLSearchParams(queryString).entries()].sort(([leftKey, leftValue], [rightKey, rightValue]) => {
+        const keyComparison = leftKey.localeCompare(rightKey);
+        if (keyComparison !== 0) {
+            return keyComparison;
+        }
+        return leftValue.localeCompare(rightValue);
+    });
+    return new URLSearchParams(pairs).toString();
+}
+function splitQuery(query) {
+    const hashIndex = query.indexOf('#');
+    const hashStripped = hashIndex >= 0 ? query.slice(0, hashIndex) : query;
+    const queryIndex = hashStripped.indexOf('?');
+    if (queryIndex < 0) {
+        return {
+            uri: hashStripped,
+            queryString: '',
+        };
+    }
+    return {
+        uri: hashStripped.slice(0, queryIndex),
+        queryString: hashStripped.slice(queryIndex + 1),
+    };
+}
+class SignBase {
+    makeHeadersString(headers) {
+        const headerItems = Object.entries(headers)
+            .filter(([key]) => key.toLowerCase().startsWith(OTS_HEADER_PREFIX))
+            .map(([key, value]) => `${key.toLowerCase()}:${value.trim()}`)
+            .sort();
+        return headerItems.join('\n');
+    }
+    getRequestSignatureString(query, headers) {
+        const { uri, queryString } = splitQuery(query);
+        const sortedQuery = sortAndEncodeQuery(queryString);
+        const headersString = this.makeHeadersString(headers);
+        return `${uri}\nPOST\n${sortedQuery}\n${headersString}\n`;
+    }
+    makeResponseSignature(query, headers, signingKey) {
+        const { uri } = splitQuery(query);
+        const headersString = this.makeHeadersString(headers);
+        return hmacSha1Base64(signingKey, `${headersString}\n${uri}`);
+    }
+    requireSignDate(signDate) {
+        if (!signDate) {
+            throw new client_error_js_1.OTSClientError('v4 sign_date is None.');
+        }
+        return signDate;
+    }
+}
+exports.SignBase = SignBase;