@openscout/protocol 0.2.63 → 0.2.82

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -4,16 +4,61 @@
 
 This package is intentionally not named `relay`. Relay is now a surface and compatibility layer. The control protocol is the canonical model underneath it.
 
-For the definitive Scout glossary, see [docs/glossary.md](../../docs/glossary.md). For Scout's current A2A posture and vocabulary mapping, see [docs/a2a-alignment.md](../../docs/a2a-alignment.md).
+For the definitive Scout vocabulary and A2A posture, see [docs/concepts.md](../../docs/concepts.md).
 
 Scout is aware of adjacent standards such as A2A, but this package is not trying to become an A2A clone. The goal is clean correspondence without giving up Scout-specific mechanics such as broker-owned routing, `invocation` plus `flight`, or the `question` / `work_item` collaboration model.
 
-## What Makes This A Good Local Communication Protocol
+## Quickstart
+
+`@openscout/protocol` is pure, dependency-free TypeScript: typed records, discriminated-union control events, and hand-written validators for the OpenScout control plane. Use it at the boundary where user intent becomes broker-owned state.
+
+```ts
+import {
+  parseScoutComposerRoute,
+  validateCollaborationRecord,
+  type CollaborationUpsertCommand,
+  type QuestionRecord,
+} from "@openscout/protocol";
+
+const parsed = parseScoutComposerRoute(">> hudson Can you review the parser?");
+if (!parsed.route) {
+  const reason = parsed.diagnostics[0]?.message ?? "missing Scout route";
+  throw new Error(reason);
+}
+
+const now = Date.now();
+const question: QuestionRecord = {
+  id: crypto.randomUUID(),
+  kind: "question",
+  state: "open",
+  acceptanceState: "none",
+  title: parsed.body,
+  createdById: "person:arach",
+  ownerId: parsed.route.target.value,
+  nextMoveOwnerId: parsed.route.target.value,
+  createdAt: now,
+  updatedAt: now,
+  metadata: {
+    route: parsed.route.target,
+    source: "composer",
+  },
+};
+
+const problems = validateCollaborationRecord(question);
+if (problems.length > 0) throw new Error(problems.join("; "));
+
+const command: CollaborationUpsertCommand = {
+  kind: "collaboration.upsert",
+  record: question,
+};
+```
+
+## Protocol Properties
 
 The target is a protocol that is:
 
 - explicit: conversation, work, delivery, and external bindings are separate records
-- durable: the broker is the only writer and local state is stored canonically
+- durable: clients and adapters submit commands to the broker instead of writing coordination records directly
 - addressable: actors, conversations, messages, invocations, flights, and deliveries all have stable IDs
 - replayable: read models can be rebuilt from durable records and events
 - observable: status, ownership, outputs, and failures are inspectable
@@ -38,35 +83,37 @@ The protocol keeps a small set of nouns and gives each one a single job:
 
 For discovery, Scout also uses a `ScoutAgentCard`: a local discovery and routing card that overlaps intentionally with A2A-style discovery fields such as provider, skills, supported interfaces, and security hints without claiming to be the A2A wire-level `AgentCard`.
 
-## Emerging Collaboration Model
+## Collaboration Model
 
-The protocol package now also exports a collaboration vocabulary for the next layer above
-messages and invocations. This is the first thin slice toward explicit human-agent and
-agent-agent workflow tracking. It is intentionally small.
+Use collaboration records when an ask or task needs durable ownership, state, or
+handoff. Keep ordinary discussion in `message` records. Use `invocation` and
+`flight` for execution requests and their runtime lifecycle. Use collaboration
+records for questions and work items that need to be tracked across surfaces.
 
-The current canonical collaboration kinds are:
+The canonical collaboration kinds are:
 
-- `question`: a lightweight information-seeking interaction with states such as `open`,
-  `answered`, `closed`, and `declined`
-- `work_item`: a durable execution object with states such as `open`, `working`,
-  `waiting`, `review`, `done`, and `cancelled`
+- `question`: a specific ask that can be `open`, `answered`, `closed`, or
+  `declined`
+- `work_item`: durable execution with an owner, next move, progress, and states
+  such as `open`, `working`, `waiting`, `review`, `done`, and `cancelled`
 
 These are peers, not points on one severity ladder:
 
 - a question can resolve directly
 - a question can attach to a work item
 - a question can spawn a work item
-- a work item can accumulate progress, waiting conditions, and review state without
-  pretending it started as a question
+- a work item can accumulate progress, waiting conditions, and review state
 
 Acceptance is modeled separately from workflow state so that a reply and satisfaction do
 not collapse into one transition. A work item can be done without peer acceptance, and a
 question can be answered without being closed yet.
 
-The exported collaboration shapes are a protocol vocabulary for upcoming runtime and UI
-work. They do not yet imply that the broker persists the full collaboration layer today.
-See [docs/collaboration-workflows-v1.md](../../docs/collaboration-workflows-v1.md) for the
-v1 model.
+These collaboration shapes are backed by the runtime. The broker persists collaboration
+records and events to its local store (`collaboration.upsert` and
+`collaboration.event.append` commands, `collaboration_records` and `collaboration_events`
+tables) and emits `collaboration.upserted` / `collaboration.event.appended` control events.
+See [docs/agents-and-collaboration.md](../../docs/agents-and-collaboration.md) for the
+full collaboration model.
 
 ## Identity Model
 
@@ -81,6 +128,22 @@ The important distinction is between a helper and an agent:
 
 This lets a person work with a helper in Codex or Claude while still invoking real agents as first-class targets.
 
+## Composer Route Operator
+
+Scout-aware text inputs can use `>>` to route without relying on `@` mentions
+owned by the host UI:
+
+```text
+/scout:ask >> hudson Review the parser.
+```
+
+The route operator is composer syntax, not message payload. The protocol package
+exports `parseScoutComposerRoute`, `SCOUT_COMPOSER_ROUTE_OPERATOR`, and
+`SCOUT_TARGET_HANDLE_SHORTHAND` so clients can translate `>> hudson`,
+`>> target:mw-talkie`, `>> ⌖mw-talkie`, `>> ref:8kj4pd`, `>> channel:ops`,
+or `>> broadcast` into structured `ScoutRouteTarget` metadata before
+submitting to the broker.
+
 ## Core Design Rules
 
 1. A message is conversation.
@@ -88,19 +151,8 @@ This lets a person work with a helper in Codex or Claude while still invoking re
 3. A flight is the tracked lifecycle of that work.
 4. Delivery is planned explicitly per target and transport.
 5. Bindings map external channels into the same internal model.
-6. Voice is metadata and transport, not the canonical message body.
-7. The broker is the only canonical writer.
-
-## Bootstrap And Startup
-
-The intended machine lifecycle is:
-
-1. `scout setup` creates machine-local settings, a relay agent registry, and repo-local `.openscout/project.json` when needed.
-2. The runtime installs a launch agent under `~/Library/LaunchAgents/` for the broker.
-3. `launchd` keeps the broker process alive and restarts it if it exits.
-4. Workspace discovery scans configured roots and repo-local manifests to map projects to agent identities.
-5. Agents register endpoints that describe their harness, transport, session, cwd, and project root.
-6. Surfaces such as the desktop shell, CLI, and relay compatibility layer talk to the broker instead of writing shared files directly.
+6. Clients and adapters submit commands to the broker instead of writing Scout-owned coordination records directly.
+7. Harnesses own their primary transcripts and logs; Scout links to and observes them without importing them as canonical messages.
 
 ## Conversation, Work, And Delivery
 
@@ -177,7 +229,7 @@ The important part is the separation:
 
 ## Storage Model
 
-The runtime package owns the SQLite schema. The durable model is:
+The runtime package owns the local storage and projection schema for Scout-owned control-plane records. The durable model is:
 
 - `nodes`
 - `actors`
@@ -195,9 +247,11 @@ The runtime package owns the SQLite schema. The durable model is:
 - `delivery_attempts`
 - `events`
 
-SQLite is the canonical store because it stays local and inspectable while handling append races, indexing, leases, retries, and subscriptions better than raw JSONL.
+These are first-party Scout facts: records created by Scout surfaces, agent tools, the broker, or mesh forwarding. Local projections such as SQLite make those facts cheap to inspect, query, and render across surfaces.
 
-## Why Work Does Not Get Lost
+External harness transcripts are different. Claude Code JSONL, Codex session JSONL, and future harness logs are source material owned by their harnesses. Scout can observe them through adapters and tail views, but the protocol should not treat every external transcript turn as a Scout `message` or require bulk transcript replication into the control-plane database.
+
+## Durability
 
 The protocol is designed so that the system does not depend on terminal scrollback to remember what happened.
 
@@ -207,6 +261,7 @@ The protocol is designed so that the system does not depend on terminal scrollba
 - deliveries and delivery attempts make routing and failures inspectable
 - bindings make external channel mappings durable
 - append-only events let read models be rebuilt
+- external harness transcript files remain linkable and observable without becoming Scout-owned conversation records
 
 That does not require every surface to be smart. The broker owns the hard part, and the surfaces can recover by reading the canonical store.
 
@@ -221,31 +276,27 @@ OpenScout should not fork its protocol per harness.
 
 This keeps the protocol stable even when the execution layer changes.
 
-## Modalities
+## Transport And Media
 
-The protocol supports multiple modalities, but text remains canonical.
+The protocol is text-first and transport-agnostic. Commands, subscriptions,
+bridge delivery, and media references travel through transport records or
+metadata; raw media does not belong in the canonical conversation log.
 
 - HTTP: commands, admin, webhook intake
 - WebSocket: subscriptions, streaming flight updates, typing/presence
 - local socket: trusted local clients such as the native app and CLI
 - bridges: Telegram, Discord, telecom adapters
-- voice: transcripts, playback directives, media references
-
-Raw media does not belong in the primary message log. The protocol stores transcript, speech, and attachment metadata while media transport stays on a dedicated transport.
+- media attachments: transcripts, playback directives, and file references
 
-## What The Protocol Is Not
+Transport-specific behavior belongs at adapters and runtime surfaces. The
+protocol keeps the durable record shape stable.
 
-OpenScout is intentionally not trying to be:
+## Package Commands
 
-- a hosted chat service
-- a workflow engine with mandatory plan bureaucracy
-- a harness-specific control plane
-- a replacement for Telegram, Discord, or tmux
+From the repo root:
 
-It is the durable local substrate that makes agent communication legible, inspectable, and recoverable.
-
-## Migration Direction
-
-The control protocol replaces Relay as the core architecture.
-
-Any remaining Relay-specific tools should be treated as surfaces or compatibility utilities, not as canonical storage or runtime paths.
+```bash
+npm --prefix packages/protocol run build
+npm --prefix packages/protocol run check
+npm --prefix packages/protocol run test
+```

package/dist/a2a.d.ts

@@ -0,0 +1,224 @@
+import type { MetadataMap, ScoutId } from "./common.js";
+import type { FlightRecord, InvocationRequest } from "./invocations.js";
+import type { ScoutAgentCard } from "./scout-agent-card.js";
+export declare const A2A_PROTOCOL_VERSION = "1.0";
+export declare const A2A_JSON_RPC_CONTENT_TYPE = "application/json";
+export declare const A2A_HTTP_JSON_CONTENT_TYPE = "application/a2a+json";
+export declare const A2A_JSON_RPC_METHODS: {
+    readonly sendMessage: "SendMessage";
+    readonly sendStreamingMessage: "SendStreamingMessage";
+    readonly getTask: "GetTask";
+    readonly listTasks: "ListTasks";
+    readonly cancelTask: "CancelTask";
+    readonly subscribeToTask: "SubscribeToTask";
+    readonly createTaskPushNotificationConfig: "CreateTaskPushNotificationConfig";
+    readonly getTaskPushNotificationConfig: "GetTaskPushNotificationConfig";
+    readonly listTaskPushNotificationConfigs: "ListTaskPushNotificationConfigs";
+    readonly deleteTaskPushNotificationConfig: "DeleteTaskPushNotificationConfig";
+    readonly getExtendedAgentCard: "GetExtendedAgentCard";
+};
+export declare const A2A_LEGACY_JSON_RPC_METHODS: {
+    readonly sendMessage: "message/send";
+    readonly sendStreamingMessage: "message/stream";
+    readonly getTask: "tasks/get";
+    readonly listTasks: "tasks/list";
+    readonly cancelTask: "tasks/cancel";
+    readonly subscribeToTask: "tasks/subscribe";
+    readonly getExtendedAgentCard: "agent/getAuthenticatedExtendedCard";
+};
+export type A2AJsonRpcMethod = typeof A2A_JSON_RPC_METHODS[keyof typeof A2A_JSON_RPC_METHODS] | typeof A2A_LEGACY_JSON_RPC_METHODS[keyof typeof A2A_LEGACY_JSON_RPC_METHODS];
+export type A2ARole = "ROLE_USER" | "ROLE_AGENT";
+export type A2ATaskState = "TASK_STATE_SUBMITTED" | "TASK_STATE_WORKING" | "TASK_STATE_INPUT_REQUIRED" | "TASK_STATE_AUTH_REQUIRED" | "TASK_STATE_COMPLETED" | "TASK_STATE_FAILED" | "TASK_STATE_CANCELED" | "TASK_STATE_REJECTED" | "TASK_STATE_UNKNOWN";
+export type A2APart = {
+    text: string;
+    metadata?: MetadataMap;
+} | {
+    file: {
+        name?: string;
+        mimeType?: string;
+        bytes?: string;
+        uri?: string;
+    };
+    metadata?: MetadataMap;
+} | {
+    data: unknown;
+    metadata?: MetadataMap;
+};
+export interface A2AMessage {
+    role: A2ARole;
+    parts: A2APart[];
+    messageId: ScoutId;
+    taskId?: ScoutId;
+    contextId?: ScoutId;
+    extensions?: string[];
+    metadata?: MetadataMap;
+}
+export interface A2AArtifact {
+    artifactId: ScoutId;
+    name?: string;
+    description?: string;
+    parts: A2APart[];
+    metadata?: MetadataMap;
+}
+export interface A2ATaskStatus {
+    state: A2ATaskState;
+    message?: A2AMessage;
+    timestamp?: string;
+}
+export interface A2ATask {
+    id: ScoutId;
+    contextId: ScoutId;
+    status: A2ATaskStatus;
+    artifacts?: A2AArtifact[];
+    history?: A2AMessage[];
+    metadata?: MetadataMap;
+}
+export interface A2ATaskStatusUpdateEvent {
+    taskId: ScoutId;
+    contextId: ScoutId;
+    status: A2ATaskStatus;
+    final?: boolean;
+    metadata?: MetadataMap;
+}
+export interface A2ATaskArtifactUpdateEvent {
+    taskId: ScoutId;
+    contextId: ScoutId;
+    artifact: A2AArtifact;
+    append?: boolean;
+    lastChunk?: boolean;
+    metadata?: MetadataMap;
+}
+export type A2AStreamResponse = {
+    task: A2ATask;
+} | {
+    message: A2AMessage;
+} | {
+    statusUpdate: A2ATaskStatusUpdateEvent;
+} | {
+    artifactUpdate: A2ATaskArtifactUpdateEvent;
+};
+export interface A2AAgentProvider {
+    organization: string;
+    url?: string;
+}
+export interface A2AAgentCapabilities {
+    streaming?: boolean;
+    pushNotifications?: boolean;
+    stateTransitionHistory?: boolean;
+    extendedAgentCard?: boolean;
+    extensions?: Array<{
+        uri: string;
+        description?: string;
+        required?: boolean;
+        params?: MetadataMap;
+    }>;
+}
+export interface A2AAgentSkill {
+    id: string;
+    name: string;
+    description: string;
+    tags?: string[];
+    examples?: string[];
+    inputModes?: string[];
+    outputModes?: string[];
+}
+export interface A2AAgentInterface {
+    url: string;
+    transport?: string;
+    protocolBinding: string;
+    protocolVersion?: string;
+    tenant?: string;
+}
+export interface A2AAgentCard {
+    protocolVersion: string;
+    name: string;
+    description: string;
+    url: string;
+    preferredTransport?: string;
+    provider?: A2AAgentProvider;
+    version?: string;
+    documentationUrl?: string;
+    capabilities: A2AAgentCapabilities;
+    defaultInputModes: string[];
+    defaultOutputModes: string[];
+    skills: A2AAgentSkill[];
+    supportedInterfaces?: A2AAgentInterface[];
+    securitySchemes?: Record<string, unknown>;
+    security?: Array<Record<string, string[]>>;
+    iconUrl?: string;
+    signatures?: unknown[];
+    metadata?: MetadataMap;
+}
+export interface A2AJsonRpcRequest<TParams = unknown> {
+    jsonrpc: "2.0";
+    id: string | number | null;
+    method: A2AJsonRpcMethod | string;
+    params?: TParams;
+}
+export interface A2AJsonRpcResponse<TResult = unknown> {
+    jsonrpc: "2.0";
+    id: string | number | null;
+    result?: TResult;
+    error?: A2AJsonRpcError;
+}
+export interface A2AJsonRpcError {
+    code: number;
+    message: string;
+    data?: unknown;
+}
+export interface A2ASendMessageParams {
+    message: A2AMessage;
+    configuration?: {
+        acceptedOutputModes?: string[];
+        historyLength?: number;
+        blocking?: boolean;
+        pushNotificationConfig?: unknown;
+    };
+    metadata?: MetadataMap;
+}
+export interface A2ATaskIdParams {
+    id?: string;
+    taskId?: string;
+    metadata?: MetadataMap;
+}
+export interface A2AListTasksParams {
+    contextId?: string;
+    limit?: number;
+    pageSize?: number;
+    pageToken?: string;
+    state?: A2ATaskState | string;
+    metadata?: MetadataMap;
+}
+export interface A2AListTasksResult {
+    tasks: A2ATask[];
+    pageSize: number;
+    nextPageToken?: string;
+    totalSize?: number;
+}
+export declare function a2aTaskStateFromFlightState(state: FlightRecord["state"]): A2ATaskState;
+export declare function isA2ATerminalTaskState(state: A2ATaskState): boolean;
+export declare function a2aTextPart(text: string, metadata?: MetadataMap): A2APart;
+export declare function a2aTextMessage(input: {
+    role: A2ARole;
+    text: string;
+    messageId: string;
+    contextId?: string;
+    taskId?: string;
+    metadata?: MetadataMap;
+}): A2AMessage;
+export declare function a2aTextFromParts(parts: unknown): string;
+export declare function a2aTextFromMessage(message: unknown): string;
+export declare function a2aContextIdForInvocation(invocation: InvocationRequest, fallback?: string): string;
+export declare function a2aTaskFromFlight(flight: FlightRecord, invocation?: InvocationRequest, options?: {
+    contextId?: string;
+    includeHistory?: boolean;
+    timestamp?: string;
+}): A2ATask;
+export declare function a2aAgentCardFromScoutCard(card: ScoutAgentCard, options: {
+    url: string;
+    protocolVersion?: string;
+    protocolBinding?: string;
+    transport?: string;
+    capabilities?: Partial<A2AAgentCapabilities>;
+}): A2AAgentCard;
+//# sourceMappingURL=a2a.d.ts.map