/**
 * publishManifest — best-effort one-way push of the tool inventory to AuthSec.
 *
 * TypeScript parity port of python/runtime/manifest.py and go-sdk's
 * manifest_publisher.go.
 *
 * Endpoint: ``PUT {authorizationServer}/authsec/resource-servers/{id}/sdk-manifest``.
 *
 * Failure never blocks startup — the runtime SDK works the same whether the
 * publish succeeded or not. Manifest sync is purely admin-facing inventory data.
 */
import type { Config, ManifestToolInput } from './config.js';
/** Canonical manifest tool entry. */
export interface ManifestTool {
    name: string;
    title?: string;
    description?: string;
    input_schema?: Record<string, unknown> | null;
    annotations?: Record<string, unknown> | null;
    suggested_scopes?: string[];
}
/**
 * Enumerate tools and PUT the manifest to AuthSec.
 *
 * The ``tools`` argument is the explicit inventory; pass either an array of
 * ``ManifestTool`` shapes or use ``cfg.toolInventoryProvider`` (which takes
 * precedence). Either source is sufficient — synthetic MCP handshake-based
 * enumeration is not implemented in the TypeScript port.
 *
 * Throws on configuration / transport failure. Most callers should use
 * ``publishManifestSafe`` which logs-and-ignores at boot.
 */
export declare function publishManifest(cfg: Config, tools?: Array<ManifestToolInput | ManifestTool>): Promise<void>;
/**
 * Like ``publishManifest`` but logs-and-ignores all failures. Designed for
 * boot-time use where manifest publish must never block startup.
 */
export declare function publishManifestSafe(cfg: Config, tools?: Array<ManifestToolInput | ManifestTool>, logger?: {
    info?: (msg: string) => void;
    warn?: (msg: string) => void;
}): Promise<void>;
//# sourceMappingURL=manifest.d.ts.map