/**
 * sub-agent-sid enforcer — dogfood of Slice 0.5 sid-naming-guard.
 *
 * Per L2 redesign §5.4, "sub-agent-sid" is one of the 5 P0 red lines.
 * Slice 0.5 (Task 7) shipped `isValidSessionId` in
 * `src/services/workspace/sid-naming-guard.ts`. This enforcer exposes the
 * same check to the red-line audit framework, so any invalid sid under
 * `.peaks/_sub_agents/` shows up as a backable red line in the audit.
 */
export interface SubAgentSidCheckResult {
    readonly invalid: readonly string[];
    readonly valid: readonly string[];
    readonly scanned: boolean;
}
/**
 * Find sids under `.peaks/_sub_agents/<sid>/` that fail `isValidSessionId`.
 * Bare forms (sid-3, unknown-sid) and date-mismatched sids all fail.
 */
export declare function findInvalidSubAgentSids(projectRoot: string): SubAgentSidCheckResult;
/**
 * Same check, for `.peaks/_runtime/<sid>/`. Slice 0.5's clean-service
 * already handles the sub-agents dir; the audit framework also wants to
 * know about invalid runtime sids (which would be a different failure mode).
 */
export declare function findInvalidRuntimeSids(projectRoot: string): SubAgentSidCheckResult;