integrationPackage manifestv2.0.6

integration.workflow-devkit

Workflow DevKit compiler and runtime bridges for ContractSpec workflows

@lssm-tech/integration.workflow-devkit
Source, release and verification context

Source snapshot bcc79fcc · Declared package version 2.0.6. This page combines the checked-in package guide and manifest; commands and runtime behavior were not executed in this review.

Package source ↗ Manifest ↗
servernode
EXPLORE THE PACKAGE

See where this package fits.

Follow a declared connection, inspect an import, then open the source guide when you need the detail.

THIS PACKAGEintegration.workflow-devkitintegrations

Arrows point from a package to its direct dependency. Each count is derived from the captured manifests.

8 declarations · first 6 shownSELECT TO INSPECT

@lssm-tech/integration.workflow-devkit

Workflow DevKit compiler and runtime bridges for ContractSpec WorkflowSpec.

What it provides

  • Compile a WorkflowSpec into a deterministic Workflow DevKit manifest.
  • Generate Workflow, Next.js, and generic-host scaffolding.
  • Run a WorkflowSpec through injected Workflow DevKit primitives such as sleep, hooks, and webhooks.
  • Create a Workflow-backed AgentRuntimeAdapterBundle For @lssm-tech/lib.ai-agent.
  • Expose chat route helpers and re-export WorkflowChatTransport for reconnectable chat UIs.

Entry points

  • @lssm-tech/integration.workflow-devkit
  • @lssm-tech/integration.workflow-devkit/compiler
  • @lssm-tech/integration.workflow-devkit/runtime
  • @lssm-tech/integration.workflow-devkit/chat-routes
  • @lssm-tech/integration.workflow-devkit/agent-adapter
  • @lssm-tech/integration.workflow-devkit/next

Workflow vs step boundary

Workflow DevKit code runs across two different execution contexts:

  • Workflow functions ("use workflow") orchestrate control flow and must stay deterministic.
  • Step functions ("use step") perform the actual Node.js work.

This matches the Workflow docs: workflow functions do not have full Node.js access, while step functions do. Keep Node.js core modules, SDK clients, database access, and other side effects inside use step helpers. The workflow function itself should only compose Workflow primitives and call step helpers.

For WorkflowSpec authoring in Workflow-hosted apps, import the safe authoring API from @lssm-tech/lib.contracts-spec/workflow/spec, not the broad @lssm-tech/lib.contracts-spec/workflow barrel.

Next.js example

ts
import { withContractSpecWorkflow } from "@lssm-tech/integration.workflow-devkit/next";
import { createWorkflowChatRoutes } from "@lssm-tech/module.ai-chat/core/workflow";

export default withContractSpecWorkflow({
  experimental: {},
});

const routes = createWorkflowChatRoutes({
  workflow: async (payload) => payload,
  getFollowUpToken({ runId }) {
    return `chat:${runId}`;
  },
});

export const POST = routes.start;

Generic host example

ts
import { createHook, createWebhook, sleep } from "workflow";
import {
  runWorkflowSpecWithWorkflowDevkit,
  type WorkflowDevkitRuntimeBridge,
} from "@lssm-tech/integration.workflow-devkit";
import { onboardingWorkflow } from "./onboarding.workflow";

export async function runOnboarding(input: Record<string, unknown>, bridge: WorkflowDevkitRuntimeBridge) {
  "use workflow";

  // Keep this function deterministic. Node.js work belongs in `use step`
  // helpers that your bridge dispatches to.
  return runWorkflowSpecWithWorkflowDevkit({
    spec: onboardingWorkflow,
    initialData: input,
    bridge,
    primitives: {
      sleep,
      createHook,
      createWebhook,
    },
  });
}

Declared capabilities.

Integration Workflow Devkit

Workflow DevKit compiler and runtime bridges for ContractSpec workflows

Use it to

  • Adopt workflow devkit compiler and runtime bridges for contractspec workflows

Requires

  • TypeScript

Choose another boundary when

  • The @lssm-tech/integration.workflow-devkit package constraints do not match the target runtime or platform.

@lssm-tech/integration.workflow-devkit

@lssm-tech/integration.workflow-devkit/agent-adapter

@lssm-tech/integration.workflow-devkit/chat-routes

@lssm-tech/integration.workflow-devkit/compiler

@lssm-tech/integration.workflow-devkit/effect-replay

@lssm-tech/integration.workflow-devkit/helpers

@lssm-tech/integration.workflow-devkit/integration

@lssm-tech/integration.workflow-devkit/next

@lssm-tech/integration.workflow-devkit/runtime

@lssm-tech/integration.workflow-devkit/types

Imports and export paths.

10 entries

These are package-manifest entry points. Named symbols listed above come from the capability catalogue; this is not an exhaustive TypeScript symbol reference.

10 imports

@lssm-tech/integration.workflow-devkit/next

Dependencies and related packages.

Runtime dependencies 8
@workflow/ai
^4.2.1
ai
^6.0.286
workflow
^4.8.9
Development dependencies 3
typescript
catalog:

Package scripts.

Commands declared by this package. Review its setup requirements before running them; no command here was executed by this review.

publish:pkgbun publish --tolerate-republish --ignore-scripts --verbose
publish:pkg:canarybun publish:pkg --tag canary
buildcontractspec-bun-build build
build:bundlecontractspec-bun-build transpile
build:typescontractspec-bun-build types
devcontractspec-bun-build dev
cleanrimraf dist .turbo
lintbun lint:fix
lint:fixnode ../../../scripts/biome.cjs check --write --unsafe --only=nursery/useSortedClasses . && node ../../../scripts/biome.cjs check --write .
lint:checknode ../../../scripts/biome.cjs check .
testbun test
prebuildcontractspec-bun-build prebuild
typechecktsgo --noEmit
Your view

Make room for your context.

Shape the presentation around this moment. You can change it whenever you need.

Your context

The different parts of you

Choose a starting point

A useful mix of context, visuals and gentle guidance.

Tune each dimension
Each dimension can change independently. Product permissions and available actions stay unchanged.

Support the way you begin and return

Tune your support

Reading comfort

Choose your language

Interface language changes text only. Markets, prices and workflows keep their own settings.

Translation coverage

Original source

Navigation151
Graph616
Categories378
Portfolio833
Examples2,035
Source preview1,542

More translations will be added as content is reviewed.

This preference is saved on this browser.

Search the website

Useful starting points

No results. Try a shorter phrase, an operation name or another search area.

A LITTLE ROOM TO EXPLORE

Find something to explore.

Open a closer look on this page, try a different perspective, or follow the detail into its own page.

How previews and controls work
01

Look before you leave

Hover a link or focus it with Tab to see a preview. Clicking the original link or pressing Enter always opens its destination.

02

Stay with the context

Move into the preview to explore its sections. Use Alt + ↓ from a focused link to enter it with the keyboard. Escape closes it.

03

Open the possibilities

Disclosure rows, perspective choices and highlighted controls reveal more. Your view changes reading comfort and the context you explore.

A separate button for a closer look

Show small preview buttons beside links where there is room. Tap the eye to inspect, or tap the link to go straight there. This choice stays in this tab.

No browsing history is collected. Reduced motion follows your device and Your view.