import { b as AcpDefinition } from './types-DUWAu0g6.js';
export { c as AcpAuditConfig, d as AcpCapabilities, a as AcpHandle, e as AcpMcpServer, A as AcpPermissionResolution, f as AcpRole, g as AcpTier, h as AcpTransport, i as Aip44Extensions, B as BackgroundTaskInfo, S as StreamEvent } from './types-DUWAu0g6.js';
export { A as AcpFrontmatter, b as Aip44ExtensionsSchema, a as acpFrontmatterSchema } from './schema-BPlcZAeS.js';
import 'zod';

/**
 * AIP-44 reference implementation of `defineAcp`.
 *
 * Built on `createDoctype` so the cross-AIP invariants (id pattern,
 * description length, top-level freeze, "defineAcp (AIP-44): …"
 * error prefix) run uniformly with every other AIP defineX.
 *
 * Field-level validation runs the schema-derived zod from
 * `./schema.ts`. Same source of truth as the .md path uses
 * (`parseAcpManifest`), so a malformed TS-authored definition fails
 * with the same diagnostic as a malformed manifest.
 *
 * Cross-field rules (kind=server requires `metadata.aip44.operator`;
 * tier=sandboxed requires `metadata.aip44.sandbox`) run after the
 * zod check so callers see one consistent error path.
 */
declare const defineAcp: (def: AcpDefinition) => Readonly<AcpDefinition>;

/**
 * @agentproto/acp — AIP-44 ACP.md `defineAcp` reference impl + thin
 * wrappers around the upstream Agent Client Protocol SDK.
 *
 * Spec: https://agentproto.sh/docs/aip-44
 * Upstream protocol: https://agentclientprotocol.com/
 *
 * Authoring paths:
 *   - TS:  `defineAcp({...})` → `AcpHandle`
 *   - MD:  `parseAcpManifest(src) → acpFromManifest({...})` → `AcpHandle`
 *
 * Runtime paths:
 *   - Drive a subprocess agent: `createAcpClient({ output, input, ... })`
 *   - Expose an operator as a server: `createAcpServer({ handle, ... })`
 */
declare const SPEC_NAME: "agentacp/v1";
declare const SPEC_VERSION: "0.1.0-alpha";

export { AcpDefinition, SPEC_NAME, SPEC_VERSION, defineAcp };