/**
 * Type Safety Convention Rules
 * Enforces type annotation best practices from docs/guide-conventions.md:288-316.
 */
import type { ValidationRule } from '../types.js';
/**
 * Detects redundant type assertions on literal values.
 * Type assertions are for validation, not conversion. Asserting a literal's
 * type is unnecessary because the type is already known at parse time.
 *
 * Redundant patterns:
 * - 5:number (number literal with number assertion)
 * - "hello":string (string literal with string assertion)
 * - true:bool (bool literal with bool assertion)
 *
 * Valid patterns:
 * - parseJson($input):dict (external input validation)
 * - $userInput:string (runtime validation)
 *
 * References:
 * - docs/guide-conventions.md:305-315
 */
export declare const UNNECESSARY_ASSERTION: ValidationRule;
/**
 * Recommends type assertions for external input validation.
 * External inputs (from host functions, user input, parsed data) should be
 * validated with type assertions to ensure type safety.
 *
 * Detection heuristics:
 * - Host function calls (HostCall nodes)
 * - Functions with fetch/read/load in their name
 * - Variables from external sources ($ARGS, $ENV)
 *
 * This is an informational rule - not all external data needs assertions,
 * but it's a good practice for critical paths.
 *
 * References:
 * - docs/guide-conventions.md:307-311
 */
export declare const VALIDATE_EXTERNAL: ValidationRule;