import type { ChannelAccountLifecycleAction, ChannelConversationKind, ChannelDirectoryScope } from '../types.js';
import type { SecretScope } from '../../config/secrets-store-paths.js';
export declare function readLifecycleAction(value: unknown): ChannelAccountLifecycleAction | null;
export declare function readConversationKind(value: unknown): ChannelConversationKind | null;
export declare function readDirectoryScope(value: unknown): ChannelDirectoryScope | null;
export declare function readString(value: unknown): string | undefined;
export declare function readStringList(value: unknown): string[] | undefined;
/**
 * Read a caller-supplied secret scope, defaulting to `project` as it always has.
 *
 * `daemon` is accepted because these actions store CHANNEL credentials, and a
 * channel is served by the daemon: an operator setting up Slack or Discord for
 * a machine that may hand the surface over at failover needs to say "this
 * belongs to the daemon, not to this checkout". Refusing the value here would
 * have silently downgraded such a request to `project`, the setup would report
 * success and put the token somewhere the daemon does not read back.
 *
 * The default stays `project` rather than following the key's ownership: these
 * are bare operator-chosen names (`SLACK_BOT_TOKEN`), not names derived from a
 * daemon-owned config path, so nothing here can tell which runtime consumes
 * them without being told.
 */
export declare function readSecretScope(value: unknown): SecretScope;
//# sourceMappingURL=parsing.d.ts.map