docs: update toolkits, API spec, and meta tools data - #4330
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
50329f3 to
7309979
Compare
7309979 to
611b4f4
Compare
611b4f4 to
29aa401
Compare
29aa401 to
92db49e
Compare
92db49e to
7211b66
Compare
7211b66 to
68eb860
Compare
68eb860 to
5d5c9de
Compare
5d5c9de to
dce2675
Compare
dce2675 to
2ac2ca1
Compare
2ac2ca1 to
7a288eb
Compare
7a288eb to
eed567d
Compare
eed567d to
b28305a
Compare
b28305a to
1388552
Compare
1388552 to
dfe7d39
Compare
dfe7d39 to
23affcb
Compare
23affcb to
0bda7bf
Compare
|
Claude finished @sdkrelease[bot]'s task in 5m 13s —— View job Docs review
The sync itself is structurally clean: all four JSON files parse, Two things to resolve, and some follow-ups that this sync surfaces but didn't cause. 1.
|
0bda7bf to
6be9d6d
Compare
|
Claude finished @sdkrelease[bot]'s task in 5m 2s —— View job Docs reviewRe-reviewed after the force-push (the sync picked up more upstream changes:
Data sanity: clean. All four JSON files parse. Test note, so nobody chases it: Still blocking1.
|
6be9d6d to
769a140
Compare
|
Claude finished @sdkrelease[bot]'s task in 3m 55s —— View job Docs reviewRe-reviewed after this push. The sync moved again:
Data sanity: clean. All four JSON files parse. Generated pages are complete. I re-ran Test note, so nobody chases it: Action needed1.
|
The production catalog refresh in #4330 renamed Stripe's triggers without the _TRIGGER suffix, so the Stripe guide cited two slugs the corpus verifier now reports as dead and every docs PR fails "Docs - Tests". The guide keeps the one renamed slug the catalog lists and points readers at the catalog for invoice payment events. The catalog only ever lists a toolkit's first 20 triggers because the generator fetched trigger types without a page limit; it now asks for up to 1000, matching the tools fetch. Claude-Session: https://claude.ai/code/session_019wRk1S4Z6V6FWr4UsybGvR
This PR: - Closes #4343 - stamps eve's durable callback descriptors on every tool `EveProvider` wraps, via the new internal `withDurableClosure(closure, callback)` helper — eve only stamps them on `defineTool` calls its build transform finds in the agent's own source, which never runs on this package inside `node_modules`, so eve discarded the whole resolver result and the agent silently lost every Composio tool - persists `{ slug, binding }` per callback, where `binding` is an id minted per `wrapTools` call and prefixed with a per-process token, and re-attaches it to that resolve's Composio executor through a module-level binding map. `executeTool` is bound to one Composio session, so a slug-only closure would have routed a call to whichever session resolved last; sessions for different users share one provider, and eve's callback registry is keyed by tool name only, so the map lives at module level rather than on the instance - covers `execute` and, when `needsApproval` is set, `approvalRequest`; the descriptor key is the global-registry symbol `Symbol.for('eve:durable-dynamic-callback')`, so no eve internal is imported and the stamp is inert on eve versions that predate the contract - adds 9 regression tests: descriptor presence and shape, JSON-serializability of the closure, replay of execute and approval from the closure alone, per-resolve executor isolation when sessions share a provider, hooks of the producing provider on replay, the unknown-slug and unknown-binding errors, that two fresh module instances never mint the same binding id, and one suite that loads eve 0.52.1's own `validateDurableDynamicToolCallbacks`, `replayDynamicTools`, and callback registry from the installed package to validate and replay a wrapped tool end to end. Before the change eve threw `Dynamic tool "..." callback "execute" does not have a durable descriptor` ## Context The reporter hit this on eve 0.50 as `non-serializable capture`; 0.52.1 reports the same root cause as a missing descriptor. eve exports no public durable-callback helper (tracked at vercel/eve#2967), so the provider stamps the descriptor itself rather than pinning users to an older eve. Bindings are kept for the life of the process: eve can resume a parked call at any time. A binding lives only in the process that resolved the tools, so a call parked across a restart cannot be replayed; the per-process token in the id makes the stale closure fail the lookup loudly instead of matching whichever resolve reused its counter value in the new process. Growth is one entry per `session.tools()` resolve. Docs (`/docs/providers/eve`) now state the contract, the restart limit, and the real reason the `step.started` resolver runs each step (principal re-evaluation and retry, cached per session). Also unblocks `Docs - Tests` on this branch: the catalog refresh in #4330 renamed Stripe's triggers, so the Stripe knowledge-base guide cited two dead slugs and the corpus verifier failed for any PR touching docs. The guide now cites only the renamed slug the catalog lists, and `generate-toolkits.ts` fetches trigger types with `limit=1000` so the catalog stops truncating every toolkit to its first 20 triggers. https://claude.ai/code/session_019wRk1S4Z6V6FWr4UsybGvR EOF -R ComposioHQ/composio
2 participants
Summary
Automated sync of backend data into the docs site.
schedulen/an/aWhat changed
docs/public/data/toolkits.json,toolkits-list.json) — refreshed list of available toolkits, auth schemes, and tools from the backend APIdocs/public/openapi.json,docs/public/openapi-v3.json,docs/public/openapi-webhooks.json) — latest v3.1 and v3.0 API specifications plus the webhook-events spec, fetched from productiondocs/content/reference/api-reference/,docs/content/reference/v3/api-reference/) — regenerated index pages for both API versionsdocs/public/data/meta-tools.json,docs/content/toolkits/meta-tools/*.mdx) — updated meta tool schemas and reference docs