@axiom-lattice/protocols 7.2.0 → 7.4.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.turbo/turbo-build.log +10 -10
- package/CHANGELOG.md +182 -0
- package/dist/index.d.mts +262 -14
- package/dist/index.d.ts +262 -14
- package/dist/index.js +258 -3
- package/dist/index.js.map +1 -1
- package/dist/index.mjs +240 -2
- package/dist/index.mjs.map +1 -1
- package/package.json +1 -1
- package/src/AuthCssContract.ts +45 -0
- package/src/CollectionStoreProtocol.ts +8 -0
- package/src/McpLatticeProtocol.ts +2 -2
- package/src/McpServerConfigStoreProtocol.ts +118 -0
- package/src/McpUiProtocol.ts +2 -0
- package/src/ModelProviderProtocol.ts +20 -4
- package/src/OpenProtocol.ts +2 -2
- package/src/PlatformAuditProtocol.ts +80 -0
- package/src/PlatformBrandingCss.ts +180 -0
- package/src/PlatformOpsProtocol.ts +73 -0
- package/src/PlatformSettingsProtocol.ts +18 -4
- package/src/PluginProtocol.ts +9 -0
- package/src/SandboxResourceProtocol.ts +1 -1
- package/src/__tests__/PlatformBrandingCss.test.ts +103 -0
- package/src/index.ts +4 -0
package/.turbo/turbo-build.log
CHANGED
|
@@ -1,5 +1,5 @@
|
|
|
1
1
|
|
|
2
|
-
> @axiom-lattice/protocols@7.
|
|
2
|
+
> @axiom-lattice/protocols@7.4.0 build /home/runner/work/agentic/agentic/packages/protocols
|
|
3
3
|
> tsup src/index.ts --format cjs,esm --dts --sourcemap
|
|
4
4
|
|
|
5
5
|
[34mCLI[39m Building entry: src/index.ts
|
|
@@ -8,13 +8,13 @@
|
|
|
8
8
|
[34mCLI[39m Target: es2020
|
|
9
9
|
[34mCJS[39m Build start
|
|
10
10
|
[34mESM[39m Build start
|
|
11
|
-
[
|
|
12
|
-
[
|
|
13
|
-
[
|
|
14
|
-
[
|
|
15
|
-
[
|
|
16
|
-
[
|
|
11
|
+
[32mCJS[39m [1mdist/index.js [22m[32m67.83 KB[39m
|
|
12
|
+
[32mCJS[39m [1mdist/index.js.map [22m[32m275.96 KB[39m
|
|
13
|
+
[32mCJS[39m ⚡️ Build success in 639ms
|
|
14
|
+
[32mESM[39m [1mdist/index.mjs [22m[32m59.74 KB[39m
|
|
15
|
+
[32mESM[39m [1mdist/index.mjs.map [22m[32m270.91 KB[39m
|
|
16
|
+
[32mESM[39m ⚡️ Build success in 687ms
|
|
17
17
|
[34mDTS[39m Build start
|
|
18
|
-
[32mDTS[39m ⚡️ Build success in
|
|
19
|
-
[32mDTS[39m [1mdist/index.d.ts [22m[
|
|
20
|
-
[32mDTS[39m [1mdist/index.d.mts [22m[
|
|
18
|
+
[32mDTS[39m ⚡️ Build success in 16969ms
|
|
19
|
+
[32mDTS[39m [1mdist/index.d.ts [22m[32m323.42 KB[39m
|
|
20
|
+
[32mDTS[39m [1mdist/index.d.mts [22m[32m323.42 KB[39m
|
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,187 @@
|
|
|
1
1
|
# @axiom-lattice/protocols
|
|
2
2
|
|
|
3
|
+
## 7.4.0
|
|
4
|
+
|
|
5
|
+
### Minor Changes
|
|
6
|
+
|
|
7
|
+
- 9bbf5ce: ## Collection batch tools and Open MCP consolidation
|
|
8
|
+
|
|
9
|
+
BREAKING (core): the collection agent tool `add_entry` is replaced by
|
|
10
|
+
`add_entries` without a compatibility alias, so agent prompts, skills, and
|
|
11
|
+
saved tool allowlists that name `add_entry` must update. `add_entries` accepts
|
|
12
|
+
1-50 entries, performs one all-or-nothing vector-store call, and generates each
|
|
13
|
+
entry's `_id` and `_created_at`. Collection middleware, plugin metadata,
|
|
14
|
+
capability mapping, built-in guidance, and the React tool catalog are kept in
|
|
15
|
+
sync.
|
|
16
|
+
|
|
17
|
+
The collection delete agent tool `delete_entry` is also replaced by
|
|
18
|
+
`delete_entries` without a compatibility alias: it accepts 1-50 ids and performs
|
|
19
|
+
one idempotent `in` vector-store delete on pgvector/memory, with an exact-ID
|
|
20
|
+
fallback for unknown backends so an unsupported filter cannot wipe a collection.
|
|
21
|
+
`SimpleMemoryVectorStore` now supports `in`/`notIn` metadata filters. Deleting a
|
|
22
|
+
collection now also drops its vector store, and single-entry create/update keep
|
|
23
|
+
server-owned identity and attempt to restore the old entry if a rewrite fails.
|
|
24
|
+
|
|
25
|
+
Open MCP now exposes all ten collection tools under the sole `collection` domain
|
|
26
|
+
(`collection_<action>`) with readOnly/destructive annotations. The built-in
|
|
27
|
+
`kbProvider` / `kb_search` tool and `kb` domain are removed; browser/preview and
|
|
28
|
+
sandbox tokens now carry the read-only `collection.search_collection` grant
|
|
29
|
+
instead. Open credentials still need a collection grant to call the tools, and key
|
|
30
|
+
creation/update rejects empty-item collection grants so a destructive domain
|
|
31
|
+
cannot be granted wholesale by accident.
|
|
32
|
+
|
|
33
|
+
Additive surfaces: REST gains `POST /api/collections/:name/entries/batch` and
|
|
34
|
+
`DELETE /api/collections/:name/entries/batch`, and the client SDK gains
|
|
35
|
+
`client.collections.entries(name).createMany()` / `deleteMany()`, sharing the
|
|
36
|
+
same limit and all-or-nothing semantics. Existing single-entry endpoints,
|
|
37
|
+
`create()`, and `delete(id)` are unchanged.
|
|
38
|
+
|
|
39
|
+
## OIDC public clients
|
|
40
|
+
|
|
41
|
+
Make the OIDC client secret optional so public clients can use Authorization
|
|
42
|
+
Code + PKCE with `token_endpoint_auth_method=none`, matching the protocol
|
|
43
|
+
default. `OIDC_CLIENT_SECRET` may be omitted for the env provider, Platform
|
|
44
|
+
Admin's provider form no longer requires a secret on create, and the gateway,
|
|
45
|
+
client SDK, and Platform Ops provider tools accept a secret-less configuration.
|
|
46
|
+
Confidential clients continue to use the existing encrypted client-secret flow.
|
|
47
|
+
|
|
48
|
+
## Security dependency updates
|
|
49
|
+
|
|
50
|
+
Follow up the Wiz remediation with `pnpm audit`: bump the pinned transitive
|
|
51
|
+
dependencies to the advisories published after the scan (shell-quote 1.11 —
|
|
52
|
+
critical command injection — fastify 5.12.6, @fastify/busboy 3.2.2,
|
|
53
|
+
@hono/node-server 2.1.3, brace-expansion 1.1.21/2.1.7/5.0.12,
|
|
54
|
+
body-parser 1.20.9/2.4.0, decode-uri-component 0.5.1, fast-uri 3.1.9/4.2.3,
|
|
55
|
+
glob 10.5/11.1/14.0.4, langsmith 0.12, picomatch 2.3.2/4.0.4,
|
|
56
|
+
protobufjs 7.6.5/8.8.1, source-map-js 1.2.2, undici 7.30.1, sanitize-html
|
|
57
|
+
2.18.1, tar 7.5.22, tmp 0.2.7, vite 6.4.5, yaml 2.9.1, ajv 6.14/8.18,
|
|
58
|
+
mysql2 3.23.1, uuid 11.1, and others). Overrides are scoped per major line
|
|
59
|
+
where different majors are both required, and none pins below a declaring
|
|
60
|
+
package's range. Further zero-out pass: echarts 5.5 → 6.1 in react-sdk,
|
|
61
|
+
katex 0.19.1 (the patched range starts at 0.18.2), glob 14.0.4 for every
|
|
62
|
+
affected major line (10/11/13/14; glob 7 is outside the advisory range),
|
|
63
|
+
minimatch 11.0.8 for every vulnerable line, rimraf 4/5 → 6.1.4 (drops the
|
|
64
|
+
glob 9 dependency), ibm-cloud-sdk-core 5.9.4 (pulls file-type 21.3.4), and
|
|
65
|
+
fast-xml-parser 5.12.0. The client-sdk build moves from tsup 6.7 to 8.5,
|
|
66
|
+
clearing the last GHSA-3mv9-4h5g-vhg3 finding. Drop the unused `xlsx`
|
|
67
|
+
dependency from `apps/web`, which has no patched npm release.
|
|
68
|
+
|
|
69
|
+
Overrides only apply to this monorepo, so also raise the published packages'
|
|
70
|
+
own dependency ranges to patched versions, otherwise downstream consumers
|
|
71
|
+
(fina_demo) resolve the old lower bounds when they reinstall: fastify
|
|
72
|
+
^5.12.6 (gateway, microsandbox-service, opensandbox-gateway), react-router
|
|
73
|
+
^7.18.2, vite ^6.4.5, mysql2 ^3.23.1 (core), and uuid ^11.1.1 (core, gateway,
|
|
74
|
+
pg-stores, react-sdk, and the cli-a2a peer range).
|
|
75
|
+
|
|
76
|
+
## Reverse-proxy mount-prefix support
|
|
77
|
+
|
|
78
|
+
Support deploying the gateway behind a reverse-proxy path prefix (`/harness`
|
|
79
|
+
or any other mount point) without hardcoding it.
|
|
80
|
+
|
|
81
|
+
Gateway-rendered pages no longer emit root-absolute asset URLs: the embed chat
|
|
82
|
+
shell and MCP App share shell reference their bundles relative to the page, and
|
|
83
|
+
shared HTML gets a relative `<base href>` (plus a page-relative password-unlock
|
|
84
|
+
request). Client-side URL derivation now keeps the externally visible prefix
|
|
85
|
+
instead of reducing URLs to `location.origin`: the embed loader strips its known
|
|
86
|
+
`/embed/agent-chat-loader.js` suffix, the embed page recovers its base from
|
|
87
|
+
`<mount>/api/web-apps/:id/chat`, the MCP App share page keeps `<mount>/s/:token`,
|
|
88
|
+
and MCP App link resolution/sandbox loading use the gateway base derived from the
|
|
89
|
+
client `baseURL`. Root-path deployments resolve to the same absolute URLs as
|
|
90
|
+
before. Adds a deterministic `/harness` embed e2e (prefix-stripping proxy) and
|
|
91
|
+
random-prefix unit coverage.
|
|
92
|
+
|
|
93
|
+
## 7.3.0
|
|
94
|
+
|
|
95
|
+
### Minor Changes
|
|
96
|
+
|
|
97
|
+
- e5dd58b: Add Admin Center management for the full gateway rate-limit policy matrix.
|
|
98
|
+
Platform admins can set per-policy `limit` and `enabled` overrides (except the
|
|
99
|
+
read-only `platform.ops.write` guard), reset one policy to its deployment
|
|
100
|
+
default, and browse policies as EntityList list rows with human-readable
|
|
101
|
+
titles and descriptions. Add
|
|
102
|
+
`GET /api/platform/rate-limits` and `client.platform.rateLimits()`. Window and
|
|
103
|
+
dimension limits remain deployment-owned. The previous unshipped flattened
|
|
104
|
+
Admin Center fields are removed; `rateLimits.policies` is the only platform
|
|
105
|
+
format. No new store or migration.
|
|
106
|
+
- 2554b78: Add personal-assistant-scoped MCP server configs in their own data domain.
|
|
107
|
+
Configs live in a dedicated `lattice_personal_mcp_server_configs` /
|
|
108
|
+
`lt_personal_mcp_configs` table (PG v220) keyed by
|
|
109
|
+
`(tenantId, ownerAssistantId, key)`, so tenant listings, tenant export/import,
|
|
110
|
+
startup restore, and older replicas never read them. A new
|
|
111
|
+
`/api/personal-mcp-servers` route family resolves the caller's personal
|
|
112
|
+
assistant server-side (no client-supplied assistant id) and returns 404 on
|
|
113
|
+
replicas that predate it rather than falling back to tenant CRUD.
|
|
114
|
+
|
|
115
|
+
Personal MCP tools register into a per-assistant tool bucket and are mounted
|
|
116
|
+
automatically only for the owning assistant, with personal keys shadowing the
|
|
117
|
+
same tenant key and tenant tools still available as fallback. Connections are
|
|
118
|
+
established lazily on the first assistant build, bounded by a sync budget, and
|
|
119
|
+
cross-replica invalidation rides a separate `personal-mcp-config-changed`
|
|
120
|
+
outbox topic that older replicas ignore. Deleting a personal assistant or an
|
|
121
|
+
assistant purges its personal MCP configs and runtime.
|
|
122
|
+
|
|
123
|
+
The MCP drawer now takes an `apiBasePath`, and the personal assistant page
|
|
124
|
+
opens it against the personal routes. Tool selection is reconciled onto the
|
|
125
|
+
live tool list so servers that rename tools each session no longer lose the
|
|
126
|
+
saved selection; the tools endpoint returns the reconciled `selectedTools`, and
|
|
127
|
+
the tools modal gains select-all/deselect-all controls.
|
|
128
|
+
|
|
129
|
+
- 1a4f8fa: Add an append-only platform audit foundation. Admin Center platform mutations are
|
|
130
|
+
captured with the real human initiator, source, route, target tenant, redacted
|
|
131
|
+
request/response, status, and duration. The audit store is available in InMemory, Local
|
|
132
|
+
SQLite, and PostgreSQL, with `GET /api/platform/audit` and client SDK methods.
|
|
133
|
+
- cb411cc: Add a platform-owned model provider catalog under the reserved `__platform__`
|
|
134
|
+
namespace, stored in the existing encrypted model-provider store. Resolution is
|
|
135
|
+
all-or-nothing: a tenant with providers uses only its own models, a tenant with
|
|
136
|
+
none falls back to the platform catalog, and only an empty platform catalog
|
|
137
|
+
falls through to the deployment environment.
|
|
138
|
+
|
|
139
|
+
Platform admins manage the catalog from Admin Center → Settings → Model
|
|
140
|
+
Providers (auditor is read-only). The platform catalog's last provider is
|
|
141
|
+
deletable so the deployment fallback stays reachable, and platform catalog
|
|
142
|
+
mutations are captured by the platform audit hook.
|
|
143
|
+
|
|
144
|
+
- a43e635: Add the read-only Platform Ops Agent. A hidden `__platform__` tenant owns a
|
|
145
|
+
fixed `platform-ops` agent (feature-flagged by `PLATFORM_OPS_AGENT_ENABLED`,
|
|
146
|
+
default off) with read-only platform tools, private per-initiator Ops threads
|
|
147
|
+
and SSE streaming under `/api/platform/ops`, a typed `client.platform.ops`
|
|
148
|
+
surface, and an Admin Center Ops page placed after Overview. There are no write
|
|
149
|
+
tools or playbooks in this release.
|
|
150
|
+
- 9107769: Add role-inherited Platform Ops Agent write tools and high-risk playbooks.
|
|
151
|
+
Owners and admins can create/update/delete platform users, grant roles, manage
|
|
152
|
+
invitations/invite links/tenants/members, configure OIDC providers, resolve SSO
|
|
153
|
+
claims, patch settings, and update branding; auditors stay read-only, owner-role
|
|
154
|
+
changes require an owner, and the hidden `__platform__` tenant is protected.
|
|
155
|
+
Every write is audited with the human initiator and the Ops Agent
|
|
156
|
+
thread/tool executor. High-risk operations raise a HITL `confirm` interrupt and execute only after
|
|
157
|
+
the user approves them. The old private Ops thread/message/SSE routes,
|
|
158
|
+
`platformOpsConfirmation` store/service, PG v220 migration, confirm/cancel
|
|
159
|
+
routes, and custom `OpsAgentPanel`/`OpsToolCard` were removed; only
|
|
160
|
+
`/api/platform/ops/config` remains. The Admin Center Ops page now reuses the
|
|
161
|
+
standard `LatticeChat`/AgentRun stack (including the embedded chat sidebar for
|
|
162
|
+
New Thread and History). Platform scope only opens the standard chat route
|
|
163
|
+
families for the fixed `platform-ops` assistant after re-checking the live
|
|
164
|
+
platform role (including the legacy Admin Center `/api/users`, `/api/tenants`,
|
|
165
|
+
and `/api/oidc-providers` routes). Ops threads/runs use a fixed internal **sandbox** workspace/project (with filesystem middleware) inside the hidden
|
|
166
|
+
platform tenant, preserving normal workspace/project thread isolation. The
|
|
167
|
+
signed console session is the tenant authority, not a client-supplied header. A real-Gateway Playwright spec covers the
|
|
168
|
+
platform Ops chat, HITL confirm/resume, and the resulting playbook audit row.
|
|
169
|
+
Ops gains a read-only `ops_list_audit` tool with filters and bounded pagination.
|
|
170
|
+
List tools accept bounded `limit` values, and writes share a per-user
|
|
171
|
+
`platform.ops.write` rate limit (60/minute) that returns
|
|
172
|
+
`PLATFORM_OPS_RATE_LIMITED` and records the refusal in the audit log. Tool
|
|
173
|
+
failures now consistently use `{ success:false, error:{ code, message } }`.
|
|
174
|
+
|
|
175
|
+
### Patch Changes
|
|
176
|
+
|
|
177
|
+
- b3a3428: Fix setting one tenant default model clearing the defaults of the other kinds.
|
|
178
|
+
The flag is scoped per `(tenant, kind)`, but the model panel wrote back the
|
|
179
|
+
provider's whole model set and flagged every non-selected row `false`, so
|
|
180
|
+
saving the chat default dropped the embedding (and ASR) default. The panel now
|
|
181
|
+
clears only same-kind siblings and omits the field for other kinds, which the
|
|
182
|
+
server reads as "keep the stored flag". The provider model endpoint's
|
|
183
|
+
validation likewise accepts one default per kind in a single write.
|
|
184
|
+
|
|
3
185
|
## 7.2.0
|
|
4
186
|
|
|
5
187
|
### Minor Changes
|