@tangle-network/agent-integrations 0.23.1 → 0.24.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/README.md +9 -3
- package/dist/bin/tangle-catalog-runtime.js +1 -1
- package/dist/{chunk-P4BB4CU6.js → chunk-6SSYWA3J.js} +1140 -1077
- package/dist/chunk-6SSYWA3J.js.map +1 -0
- package/dist/index.d.ts +1 -1
- package/dist/index.js +3 -1
- package/dist/specs.d.ts +39 -1
- package/docs/integration-execution-audit.md +28 -20
- package/docs/integration-execution-matrix.json +7425 -1334
- package/package.json +1 -1
- package/dist/chunk-P4BB4CU6.js.map +0 -1
package/README.md
CHANGED
|
@@ -25,6 +25,7 @@ contract.
|
|
|
25
25
|
## What It Provides
|
|
26
26
|
|
|
27
27
|
- A normalized connector/action/trigger catalog.
|
|
28
|
+
- First-class Tangle integration contracts for every catalog connector.
|
|
28
29
|
- User-owned connection records that reference secrets without storing raw
|
|
29
30
|
credentials in public shapes.
|
|
30
31
|
- Short-lived capability tokens for sandbox-safe access to a subset of a user's
|
|
@@ -109,6 +110,7 @@ pnpm add @tangle-network/agent-integrations
|
|
|
109
110
|
| `composeIntegrationRegistry` | Merges arbitrary catalog sources with explicit aliases, precedence, support tiers, and conflict diagnostics. |
|
|
110
111
|
| `buildIntegrationCoverageConnectors` | Planning catalog for 100+ high-value integrations. |
|
|
111
112
|
| `buildTangleIntegrationCatalogConnectors` | Broad normalized Tangle Integrations Catalog inventory for long-tail connection discovery. |
|
|
113
|
+
| `listTangleIntegrationContracts` | First-class Tangle-owned action/trigger/auth/runtime contracts for every catalog connector. |
|
|
112
114
|
| `createTangleCatalogExecutorProvider` | Promotes catalog entries to gateway-executable only when a runtime executor is explicitly supplied. |
|
|
113
115
|
| `createTangleCatalogHttpExecutor` | Signed HTTP executor client for Tangle-hosted catalog runtimes. |
|
|
114
116
|
| `createTangleCatalogRuntimeHandler` | Server-side `/v1/integration-catalog/actions/invoke` handler with signature, connector, and action validation. |
|
|
@@ -126,9 +128,9 @@ pnpm add @tangle-network/agent-integrations
|
|
|
126
128
|
|
|
127
129
|
## Catalog Registry
|
|
128
130
|
|
|
129
|
-
|
|
130
|
-
|
|
131
|
-
|
|
131
|
+
Every catalog connector has a first-class Tangle contract. Native adapters and
|
|
132
|
+
package runtimes are implementation backends behind that contract; product code
|
|
133
|
+
should route through `IntegrationHub` either way.
|
|
132
134
|
|
|
133
135
|
Use `buildDefaultIntegrationRegistry()` before creating tool catalogs or
|
|
134
136
|
connection pickers. It produces one canonical connector per integration,
|
|
@@ -139,6 +141,10 @@ metadata, and marks each connector with a support tier:
|
|
|
139
141
|
catalogOnly < setupReady < gatewayExecutable < firstPartyExecutable < sandboxExecutable
|
|
140
142
|
```
|
|
141
143
|
|
|
144
|
+
Use `buildDefaultIntegrationRegistry({ tangleCatalogRuntimeExecutable: true })`
|
|
145
|
+
when the Tangle catalog runtime is deployed and should be exposed as executable
|
|
146
|
+
tools.
|
|
147
|
+
|
|
142
148
|
See [Catalog Registry](./docs/catalog-registry.md).
|
|
143
149
|
|
|
144
150
|
## App And Agent Grants
|