@nestos/kanban 0.0.0-stage → 0.5.2

package/README.md

@@ -1,3 +1,166 @@
-# Temporary Holding Version
+# @nestos/kanban
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+## 独立安装与开发
+
+```sh
+npm install @nestos/kanban @nestos/vfs-core
+# 在本仓库开发
+pnpm install --frozen-lockfile
+pnpm typecheck
+pnpm test
+pnpm build
+pnpm pack
+```
+
+本包提供领域服务与运行时，不包含 DOM 界面、CSS 或 UI 依赖。`/contracts` 为前台与远程调用提供无 I/O 的契约和纯函数。
+
+基于 VFS 的通用看板与工作协调库，存储与运行时通过可选 peer `@nestos/vfs-core` 接入 VFS；使用这些入口时显式安装该依赖。提供唯一责任人、估算与在制额度、依赖、验收、归档、日志和决策，以及持久派发意图。库不调用模型、不创建 Session/Task、不安装后台调度器。执行、来源与资源活动通过可选端口接入。
+
+```ts
+import {SeqKanbanStore, createKanbanModule} from '@nestos/kanban';
+
+const service = createKanbanModule({
+    store: await SeqKanbanStore.open(authorizedFS, '/work'),
+    actor: authenticatedPrincipal,
+    authorize: authorizeOperation,
+    verifyOutputs: verifyImmutableArtifacts,
+    onCommitted: async (boardId, source) => publishPersistedEvents(boardId, source),
+    log: logMetadata,
+});
+```
+
+`actor`、授权及产物核验均来自可信宿主，不能从命令 JSON 中采信。`create` 传入 scope、members、职责和 policy；`execute` 传入稳定 operationId、expectedRevision 和强类型 command。并发冲突由调用方重新读取后决定，不能换 ID 盲目重试外部执行。
+
+## 公共入口
+
+| 入口 | 内容 |
+| --- | --- |
+| 根入口 | `createKanban` 分组 API；`createKanbanModule` 服务工厂与 `SeqKanbanStore` |
+| `/contracts` | 无副作用 DTO、命令、事件与默认配置 |
+| `/storage` | `SeqKanbanStore`、`ConditionalKanbanStore`、内容安装与传输端口 |
+| `/execution` | `createKanbanExecutionBridge`；宿主提供 prepare/start/inspect |
+| `/discovery` | `createKanbanDiscovery`；宿主提供来源、分析和授权 |
+| `/runtime` | `createKanbanRuntime`；单一工厂、执行意图/句柄/回执及完整协调 |
+| `/integration` | 自定义宿主的装配、业务协调与语义状态接口 |
+| `/activity` | `createKanbanActivityModule`；注入来源和外部引用 namespace |
+
+`createKanban(options)` 提供 `boards.create/get/list/overview`、`items.get/query`、`records.get/query`、`planning.get`、`references.resolve/suggest`、`execute`、`events`、`tick` 和 `quiesce/dispose`。execute 返回 `{boardId, operationId, revision}`；幂等重放时 revision 是当前返回快照的版本。需要 KanbanService（例如 UI、执行桥）时直接使用 `createKanbanModule`，二者共享同一实现与命令协议。
+
+主体 ID、Session/Task/Message ID 及历史持久格式保留。独立 Agent 可以只提供自己的 ID；若提供执行身份，所有权继续按该身份隔离。NestOS 在适配边界继续要求真实 Session/Task，宿主始终负责实际权限核验。
+
+## 前台界面
+
+界面由独立包 `@nestos/kanban-ui` 提供，样式入口为 `@nestos/kanban-ui/style.css`。前台仅通过本库 `/contracts` 中的 KanbanClient 接入本地或远程服务，不依赖后台存储、执行或恢复实现。
+
+## 版本化内容安装
+
+`/contracts` 自包含定义 `KanbanContent`、`KanbanClient` 及领域 DTO。`/storage` 的 `installKanbanContent({store, actor, authorize, log, content, operationId})` 安装宿主提供的内容；显式授权 action=install-content，在同一事务保存工作项、记录、修改建议、归档、事件、回执与安装版本。安装内容不授予执行或审核权限。库不携带 NestOS 示例、文案或模板。
+
+默认只补充新版本新增的身份，保留用户修改和删除。显式 fillMissing 可以恢复缺失项，已存在或已归档身份不会重新创建。missingReferences=detach 是明确选择的引用修复策略，默认仍按领域约束拒绝无效关系。inspectKanbanContent 返回安装版本与完整性，不向宿主泄露 reducer 状态。
+
+## 验证
+
+```bash
+pnpm --filter @nestos/kanban typecheck
+pnpm --filter @nestos/kanban test
+pnpm --filter @nestos/kanban build
+pnpm --filter @nestos/kanban example
+```
+
+[独立示例](examples/standalone.ts) 只使用 VFS 与假执行器，完成两节点依赖计划，显式自动验收后关闭；没有 NestOS Runtime、模型或网络调用。内存后端用于演示，生产需提供持久后端和实际授权。
+
+## 计划与执行
+
+管理主体以 `publish-plan` 发布 `kanban.plan/1`：每项指定 assignee、dependsOn、验收条件及输入/输出名称。决策可保存 `coordination.manager/executor`，关联计划只允许该管理主体发布；成员和宿主权限仍需独立检查。计划校验循环、悬空依赖及版本冲突后，原子创建工作项。
+
+执行主体提交 `prepare-dispatch`，同一事务完成认领、估算、依赖产物固定和派发意图持久化。可选 execution 入口负责冻结请求和提交前日志，再通过宿主端口调用既有执行器。`observe-execution` 只接收原 dispatchId/fence 的真实观察；`unknown` 保留责任，禁止自动重派。成功首先进入 review；默认需要独立主体 `accept-execution`。显式 review=assignee 时可信成功可自动验收。只有依赖已验收且输出存在，后续任务才能进入 ready。
+
+`workflow(boardId)` 返回计划、派发和 ready 摘要。核心只解锁已发布 DAG；动态分解和业务决策仍由管理主体提交下一版计划。修改任务定义需要新任务 ID，未结算执行阻止替换计划或转交责任。`completedPlans` 仅说明已封闭计划中的事项完成，不能替代业务目标验收。
+
+## 文件协议
+
+默认存储 `/kanban/boards.seq`，可注入目录或完全替换 KanbanStore。SeqFile 必须支持 transaction。键中身份使用 encodeURIComponent：
+
+| 键 | 内容 |
+| --- | --- |
+| `index` | 看板 ID 列表 |
+| `board/<boardId>` | layout=2 清单：板元数据、摘要索引、workflow、序列及状态 |
+| `item/<boardId>/<itemId>` | 工作项正文或内容寻址引用 |
+| `record/<boardId>/<recordId>` | 日志/决策正文或引用 |
+| `archive/<boardId>/<itemId>` | 已关闭归档项与关闭事实 |
+| `event/<boardId>/<16位序号>` | 不可变事件/outbox |
+| `receipt/<boardId>/<operationId>` | 请求指纹，防止重复或异义提交 |
+
+看板编号使用同文件的计数器与反向索引。计划及派发目前在 board 清单的 state.workflow 中，不另建伪数据库键。一个命令的所有控制记录在同一事务提交；回滚不发布其中任一变化。
+
+正文超过 8 KiB 时先保存为同 SeqFile 的 `<sha256>.json` 资产并核验摘要/长度，再提交引用。失败可留下未引用资产，不会发布半个正文；自动垃圾回收和历史裁剪尚未启用。产物引用 `{name,ref,sha256,bytes}` 的权限与实际内容由宿主核验，引用字符串本身不授予文件访问。
+
+VFS `seq:committed` 可用于唤醒宿主，但持久状态与定期补扫才是恢复依据。`content:finished` 在读取关闭时也会发出，不能当成任务完成。禁止直接改内部 JSON 或用普通文件复制覆盖活动数据库；外部 Agent 应调用授权命令接口。
+
+## 生命周期与宿主边界
+
+关闭顺序：停止事件/定时准入 → service.quiesce（拒新操作、等待已准入事务）→ 排空执行适配器 → 最后关闭 VFS。宿主重启后扫描持久派发、检查原执行身份并补投 outbox。SeqFile 不能与模型调用、远程服务或另一数据库组成单一事务，执行桥必须保留提交前日志和 unknown 状态。
+
+NestOS 的默认目录、远程 HttpSeqClient、Session 来源读取、发布 Agent/Flow、Kernel 回执、系统 notify 与调度接线均位于 `backend/app-core/src/kanban/`。扫描状态机、批量提交、远程事务编码与执行恢复归独立库；UI 的 NestOS 包装位于 `ui/app-shell/src/kanban/`。应用入口只导出实际 NestOS 绑定，不代转出库 API，核心没有这些运行依赖。完整规范见 [Kanban 协调设计](https://github.com/nest-agentos/NestOS/blob/main/doc/design/kanban-coordination.md)。
+
+会话活动入口 `executionSession(boardId, itemId)` 只读取当前执行摘要。显式传入 `{includeRelated: true}` 时，通过可选 `KanbanSessionSource.related` 合并宿主关联与已有执行绑定、参与者；返回的 `sessions` 按不透明 Session ID 去重，各自包含用途和 `executions` 执行记录。续办在同一 Session 下保留不同尝试，`current` 仅由正式执行绑定决定。UI 在展开「相关会话」时加载，支持刷新和宿主注入的原始资源链接；普通活动轮询不读取历史。资源属性由宿主提供，库不识别工作区、Git 或原生会话协议。
+
+## Optional automation integration
+
+Boards may store automation settings with opaque planner/executor references and trusted coordinator/worker principals. `configure-automation` changes configuration only; the host owns model calls and scheduling. Existing unassigned work may join a sealed plan with `expectedRevision`; adoption preserves its identity and manual dependencies. `edit-item` updates unplanned work while published definitions remain immutable. Execution bridges accept a dynamic `autoDispatch` predicate so pausing prevents new claims while existing admissions are still inspected. Optional client `automationCatalog` and `analysisStatus` ports supply the generic configuration UI and analysis details.
+
+宿主已有工作区导航时，可直接构造 `KanbanWorkbench` 并省略 `sidebar`，通过 `createBoard()` 接入导航动作，通过 `committed` 刷新目录；`mountKanban` 的独立默认侧栏保持可用。父项详情提供子事项分页与新建入口，子项通过 `planning.parentId` 关联父项，执行依赖仍单独保存在 `planning.dependencies`。
+
+Task 的持久 startAt、编辑租约、单一状态投影与文件协议见 [执行规范](https://github.com/nest-agentos/NestOS/blob/main/doc/design/kanban-task-execution.md)。`item().task` 和 query 的 `task` 为相同宿主事实的投影，`phase` 过滤在服务端执行。
+
+事项支持 `request-control action=cancel` 的持久取消中状态及宿主停止回执；父项取消原子登记后代取消意图。`delete-item`、`delete-record` 保存逻辑删除墓碑，默认查询隐藏，`includeDeleted` 显式包含，原 ID 和审计保留。决策取消分为 `request-record-cancellation` 与结算后的 `cancel-record`。可选宿主端口 `controlRecord`、`taskFixes`、`cancelFix` 提供关联执行控制及修复澄清放弃；库不自行控制 Session。资源 `ownership` 独立于 `state`，归属未知或其他事项的资源必须保留，不得从归属未知推断执行已停止。
+
+看板 `lifecycle` 支持整体取消与等待删除屏障：`request-board-stop` 冻结新任务/计划/准入/派发/续办，`observe-board-stop` 保存收尾阶段。宿主可提供 `cancelBoard`、`requestBoardDeletion`；后者保存跨重启删除请求，默认 drain 等待原执行结束，或显式 cancel 后再删除。独立库不自装调度器，宿主扫描负责最终预检和自动删除，UI 显示请求已接纳与具体阻塞项。
+
+## 完整运行时
+
+普通接入使用一个工厂，直接获得可查询、提交命令、扫描和关停的看板实例：
+
+```ts
+import {createKanbanRuntime} from '@nestos/kanban/runtime';
+
+const kanban = await createKanbanRuntime({
+    fs: authorizedFS,
+    actor: authenticatedPrincipal,
+    authorize: authorizeOperation,
+    execution: executionAdapter, // Optional for boards without automated execution.
+});
+
+await kanban.scan();
+await kanban.dispose();
+```
+
+默认目录为 `/kanban`，可通过 `directory` 设置。`resources` 注入资源目录与权限校验，`activity` 注入执行活动来源，`onCommitted` 接入已有事件通道，`log` 接入诊断。库不自动创建定时器。返回值只包含看板语义操作，不暴露 store、journal、serviceFor 或原始 VFS。
+
+执行适配器只实现以下协议：
+
+```ts
+const executionAdapter = {
+    catalog: () => authorizedTargets(),
+    prepare: intent => prepareExternalRequest(intent),
+    submit: handle => submitExternalRequest(handle),
+    inspect: handle => inspectExternalReceipt(handle),
+    control: (handle, command) => controlExternalExecution(handle, command),
+};
+```
+
+- `ExecutionIntent` 包含稳定身份、作用域、目标与结构化上下文；`purpose` 区分规划和工作。规划返回 `ready/dependencies/reason` 及可选 estimate/subtasks，不引入宿主 Session/Flow DTO。
+- `ExecutionHandle` 是可持久化的 `{id,data?}`，由适配器解释。prepare 不能启动外部执行；运行时先保存句柄再 submit，恢复时使用原句柄 inspect。
+- 回执返回 `outcome`、可选 `result/executionId/code/controlCapabilities`。运行时保存并校验结果，通过 `kanban.results(boardId, dispatchId)` 读取授权产物。成功但结果未到达时保持 unknown；无正文结果显式返回 `result: null`。
+- 控制统一接收句柄与 `{operationId,action}`。不提供 control 时返回明确的 `TASK_CONTROL_UNSUPPORTED`，不能把取消意图当作取消完成。
+- 当前事项正文只放在 context.task 一处；决策只携带身份与修订，规划的 related 为摘要。执行依赖只传直接依赖的已验收产物。适配器按需通过授权查询读取额外内容。
+
+运行时负责幂等认领、回执丢失恢复、日志投影、产物归属、取消协调和删除屏障。宿主无需了解持久键，也无需自行编写这些状态机。完整接入、重启恢复、失败处理和取消验收见 `tests/public-runtime.test.ts`。
+
+## 自定义宿主集成
+
+`/integration` 面向需要自定义预设、交互确认或底层装配的受信任宿主，显式导出 `assembleKanbanRuntime`、协调组件与语义状态接口。它与普通 `/runtime` 入口分开；远程 HTTP/MCP 服务应只暴露经过授权的看板语义操作，不能透传 integration 对象。
+
+`KanbanCollaboration` 提供修复准备、冻结确认、接纳与决策快照，`collaborationRelations` 提供关联执行投影；适配器无需读取 fix、record-runs 或 task-reply 的内部持久键。宿主仍负责确认文案、通道交互和系统事件投影。
+
+`KanbanOperationRecord` 与 `coordinateOperation` 提供自定义业务操作的统一持久协调；执行请求和结果保持不透明，业务插件负责结果约束。只有正式“未启动”回执允许重试提交，连接中断只核对原身份。

package/dist/activity-BbC4sgKL.d.cts

@@ -0,0 +1,258 @@
+import { u as KanbanExternalReference, y as KanbanItemQuery, x as KanbanItemPage, z as KanbanItemSummary, r as KanbanDispatch, T as KanbanService, v as KanbanFixSession, f as KanbanAutomationCatalog, b as KanbanAnalysisStatus } from './planning-CHrOqQ6b.cjs';
+
+/** Hosts resolve opaque resources and execute records; the library owns no project policy. */
+interface KanbanRecordResource {
+    reference: KanbanExternalReference;
+    label: string;
+}
+interface KanbanItemResourceCatalog {
+    resources: KanbanRecordResource[];
+    selected?: KanbanExternalReference;
+    required?: boolean;
+    readonly?: boolean;
+}
+interface KanbanRecordExecution {
+    id: string;
+    recordId: string;
+    recordRevision: number;
+    boardId: string;
+    rootItemId?: string;
+    itemIds?: string[];
+    state: 'preparing' | 'running' | 'blocked' | 'review' | 'completed' | 'failed' | 'cancelling' | 'cancelled' | 'pausing' | 'paused' | 'resuming' | 'unknown';
+    createdAt: number;
+    updatedAt: number;
+    code?: string;
+}
+interface KanbanRecordRunRequest {
+    operationId: string;
+    recordId: string;
+    expectedRevision: number;
+    placement?: 'current-board' | 'new-board';
+}
+
+/** Host-owned execution resources; the coordination library does not interpret their backend. */
+interface KanbanWorkResource {
+    id: string;
+    kind: string;
+    title: string;
+    location: string;
+    version: string;
+    ownership?: 'current' | 'other' | 'unknown';
+    state: 'associated' | 'in-use' | 'retained' | 'cleanup-ready' | 'cleaned' | 'unknown';
+    reasons: string[];
+    properties: Array<{
+        label: string;
+        value: string;
+    }>;
+    canCleanup: boolean;
+}
+interface KanbanWorkResourceQuery {
+    inspect?: boolean;
+}
+interface KanbanWorkResourceCleanup {
+    operationId: string;
+    itemId: string;
+    resourceId: string;
+    version: string;
+}
+
+interface KanbanOperationChoice {
+    id: string;
+    label: string;
+    detail?: string;
+}
+interface KanbanOperationField {
+    id: string;
+    label: string;
+    choices: KanbanOperationChoice[];
+    selected?: string;
+}
+/** Host-owned operations; the portable view does not interpret deployment or Git policy. */
+interface KanbanItemOperation {
+    id: string;
+    label: string;
+    state: 'unavailable' | 'ready' | 'running' | 'unknown' | 'succeeded' | 'failed' | 'waiting-confirmation';
+    enabled: boolean;
+    code?: string;
+    reason?: string;
+    runId?: string;
+    sessionId?: string;
+    summary?: string;
+    fields?: KanbanOperationField[];
+    confirmation?: string;
+    configurable?: boolean;
+    binding?: KanbanExternalReference;
+    openSessionOnRun?: boolean;
+}
+interface KanbanItemOperations {
+    revision: string;
+    operations: KanbanItemOperation[];
+    targets?: Array<{
+        label: string;
+        reference: KanbanExternalReference;
+    }>;
+}
+interface KanbanItemOperationRequest {
+    operationId: string;
+    itemId: string;
+    action: string;
+    expectedRevision: string;
+    selections?: Record<string, string>;
+    confirmed?: boolean;
+}
+interface KanbanItemOperationBinding {
+    operationId: string;
+    itemId: string;
+    action: string;
+    expectedRevision: string;
+    target: KanbanExternalReference;
+}
+
+interface KanbanDeletionPreview {
+    boardId: string;
+    title: string;
+    revision: number;
+    version: string;
+    blockers: Array<{
+        code: string;
+        itemId?: string;
+        sessionId?: string;
+    }>;
+    pendingItems: number;
+    pendingDeletion?: {
+        operationId: string;
+        mode: 'drain' | 'cancel';
+        phase: 'waiting' | 'ready' | 'blocked';
+        code?: string;
+    };
+    /** Display labels for items referenced by blockers and resources. */
+    itemTitles?: Record<string, string>;
+    resources: Array<{
+        itemId: string;
+        resource: KanbanWorkResource;
+    }>;
+}
+interface KanbanDeletionRequest {
+    operationId: string;
+    version: string;
+    expectedRevision: number;
+    cleanup: boolean;
+}
+
+type KanbanSessionPhase = 'running' | 'queued' | 'waiting' | 'waiting-input' | 'waiting-approval' | 'paused' | 'idle' | 'completed' | 'failed' | 'cancelled' | 'unknown';
+interface KanbanExecutionSession {
+    sessionId: string;
+    resourceId?: string;
+    title?: string;
+    state: KanbanSessionPhase;
+    createdAt?: number;
+    lastActivityAt?: number;
+    observedAt?: number;
+    stale: boolean;
+    recent: boolean;
+    code?: string;
+}
+interface KanbanSessionActivityQuery extends KanbanItemQuery {
+    execution?: 'all' | 'running' | 'recent' | 'active';
+}
+interface KanbanSessionItemSummary extends KanbanItemSummary {
+    execution?: KanbanExecutionSession;
+}
+interface KanbanSessionItemPage extends Omit<KanbanItemPage, 'items'> {
+    items: KanbanSessionItemSummary[];
+}
+type KanbanSessionPurpose = 'execution' | 'planning' | 'fix' | 'finalization' | 'discussion';
+/** A run belongs to a Session; continuing it does not create another Session. */
+interface KanbanSessionExecution {
+    id: string;
+    purpose: KanbanSessionPurpose;
+    dispatchId?: string;
+    attempt?: number;
+    previousDispatchId?: string;
+    roundId?: string;
+    turnId?: string;
+    state?: KanbanSessionPhase;
+    outcome?: KanbanDispatch['outcome'];
+    createdAt?: number;
+    completedAt?: number;
+    code?: string;
+    resources?: Array<{
+        label: string;
+        value: string;
+    }>;
+}
+interface KanbanSessionAssociation {
+    sessionId: string;
+    purpose: KanbanSessionPurpose;
+    execution?: KanbanSessionExecution;
+}
+interface KanbanRelatedSession extends KanbanExecutionSession {
+    current: boolean;
+    purposes: KanbanSessionPurpose[];
+    executions: KanbanSessionExecution[];
+}
+interface KanbanSessionDetailQuery {
+    includeRelated?: boolean;
+}
+interface KanbanExecutionSessionDetail {
+    continuation?: {
+        previousDispatchId: string;
+    };
+    current?: KanbanExecutionSession;
+    history: Array<{
+        sessionId: string;
+        bindingId?: string;
+        current: boolean;
+    }>;
+    /** Loaded explicitly so activity polling never enumerates historical Sessions. */
+    sessions?: KanbanRelatedSession[];
+    sessionsCode?: string;
+}
+/** Transport-facing service with optional authorized resource activity. */
+interface KanbanClient extends KanbanService {
+    cancelBoard?(boardId: string, request: {
+        operationId: string;
+        expectedRevision: number;
+    }): Promise<void>;
+    requestBoardDeletion?(boardId: string, request: KanbanDeletionRequest & {
+        mode: 'drain' | 'cancel';
+    }): Promise<void>;
+    previewDeletion?(boardId: string): Promise<KanbanDeletionPreview>;
+    deleteBoard?(boardId: string, request: KanbanDeletionRequest): Promise<void>;
+    itemOperations?(boardId: string, itemId: string): Promise<KanbanItemOperations>;
+    runItemOperation?(boardId: string, request: KanbanItemOperationRequest): Promise<KanbanItemOperations>;
+    bindItemOperation?(boardId: string, request: KanbanItemOperationBinding): Promise<KanbanItemOperations>;
+    workResources?(boardId: string, itemId: string, query?: KanbanWorkResourceQuery): Promise<KanbanWorkResource[]>;
+    cleanupWorkResource?(boardId: string, request: KanbanWorkResourceCleanup): Promise<KanbanWorkResource>;
+    replyTask?(boardId: string, request: {
+        itemId: string;
+        attemptId: string;
+        replyTo: string;
+        operationId: string;
+        content: string;
+    }): Promise<void>;
+    taskFixes?(boardId: string, itemId: string): Promise<KanbanFixSession[]>;
+    cancelFix?(boardId: string, request: {
+        fixId: string;
+        operationId: string;
+    }): Promise<KanbanFixSession>;
+    controlRecord?(boardId: string, request: {
+        recordId: string;
+        operationId: string;
+        action: 'pause' | 'resume' | 'cancel';
+    }): Promise<void>;
+    fixTask?(boardId: string, request: {
+        itemId: string;
+        operationId: string;
+    }): Promise<KanbanFixSession>;
+    itemResources?(boardId: string, parentId?: string): Promise<KanbanItemResourceCatalog>;
+    recordResources?(): Promise<KanbanRecordResource[]>;
+    runRecord?(boardId: string, request: KanbanRecordRunRequest): Promise<KanbanRecordExecution>;
+    recordExecutions?(boardId: string, recordId: string): Promise<KanbanRecordExecution[]>;
+    automationCatalog?(): Promise<KanbanAutomationCatalog>;
+    analysisStatus?(boardId: string, itemId: string): Promise<KanbanAnalysisStatus | null>;
+    queryActivity?(boardId: string, query?: KanbanSessionActivityQuery): Promise<KanbanSessionItemPage>;
+    executionSession?(boardId: string, itemId: string, query?: KanbanSessionDetailQuery): Promise<KanbanExecutionSessionDetail>;
+}
+
+export type { KanbanClient as K, KanbanDeletionPreview as a, KanbanDeletionRequest as b, KanbanExecutionSession as c, KanbanExecutionSessionDetail as d, KanbanItemOperation as e, KanbanItemOperationBinding as f, KanbanItemOperationRequest as g, KanbanItemOperations as h, KanbanItemResourceCatalog as i, KanbanOperationChoice as j, KanbanOperationField as k, KanbanRecordExecution as l, KanbanRecordResource as m, KanbanRecordRunRequest as n, KanbanRelatedSession as o, KanbanSessionActivityQuery as p, KanbanSessionAssociation as q, KanbanSessionDetailQuery as r, KanbanSessionExecution as s, KanbanSessionItemPage as t, KanbanSessionItemSummary as u, KanbanSessionPhase as v, KanbanSessionPurpose as w, KanbanWorkResource as x, KanbanWorkResourceCleanup as y, KanbanWorkResourceQuery as z };