Migrate to Client SDK 1.0

@scrydon/sdk 1.0 removes the legacy Agentic public workflow-chat surface. The following exports and methods no longer exist:

• client.chat.stream(...)
• ChatStreamOptions
• the React useChatStream(...) hook

Integration bindings are structured

SDK 1.0 uses one IntegrationBinding object everywhere an integration account or resource is selected. Replace persisted credential strings with the matching structured value:

// Connected integration
{ connectionRef: connectionId }

// Explicit account
{ credentialRef: accountId }

// Explicit account and resource
{ credentialRef: accountId, resource: { type: 'mailbox', id: mailboxId } }

// Resolve the account owned by the verified execution identity
{ credentialSubject: 'acting_principal' }

// Use the product/environment default
{}

Legacy values such as accountId::resourceId and environment-connection:v1:... were pre-production formats and are not parsed by SDK 1.0. Reselect those credentials in the workflow editor; do not attempt to translate opaque persisted strings at runtime.

Governed LLM calls

Use client.chat.completions.create(...) for OpenAI-compatible LLM completions. Your application owns and resends conversation history.

const stream = await client.chat.completions.create({
  model: 'gpt-4o-mini',
  messages: [{ role: 'user', content: 'Summarize Q3' }],
  stream: true,
})

for await (const chunk of stream) {
  process.stdout.write(chunk.choices[0]?.delta.content ?? '')
}

Workflow execution

Use client.workflows.trigger(...) for an inline result or client.workflows.triggerAsync(...) for a long-running workflow. These APIs execute workflows; they do not create a public chat session.

const result = await client.workflows.trigger({
  workflowId: 'wf_abc',
  inputs: { message: 'Summarize Q3' },
})

Agent-to-agent delegation

Use the published A2A endpoint and an official A2A client when another agent, such as Cortex, delegates work to Scrydon. A2A publications and Cortex's own /api/chat interface remain supported and are separate from the retired Agentic public-chat routes.

There is no drop-in replacement for the retired hosted chat UI or its session storage. Build conversation UI and persistence in the calling application when that is still required.