/**
 * Built-in platform pack loader.
 *
 * Reads `packs/platforms/<category>.yaml` at module-load time and assembles the
 * `CategoryConfig[]` that pre-1.5 lived as hardcoded TypeScript arrays. Adding
 * or editing a platform now means editing a YAML file — no TypeScript edit, no
 * `npm publish` for built-in updates if you ship the YAML in your install.
 *
 * Resolution path:
 *   1. Walk up from the compiled `dist/engine/config/platformLoader.js` to find
 *      the package root, then look for `packs/platforms/`.
 *   2. Also accept a sibling `packs/` next to the module (covers npm-installed
 *      consumers — `node_modules/clarifyprompt-mcp/packs/`).
 *   3. If neither exists, fall back to the hardcoded built-ins via
 *      `getFallbackCategories()` so a malformed install still boots.
 *
 * Failure mode: any individual YAML that fails to parse logs ONE stderr line
 * and is skipped; other categories still load. A missing `packs/platforms/`
 * dir entirely → falls through to the fallback table without throwing.
 */
import type { CategoryConfig } from './categories.js';
/**
 * Load all `packs/platforms/*.yaml` files. Returns one CategoryConfig per
 * loadable file. Categories not represented (missing file, parse error) are
 * filled in by the caller from the fallback table.
 */
export declare function loadCategoriesFromPacks(): CategoryConfig[];
/**
 * Merge YAML-loaded categories with a fallback table. Any category present in
 * the YAML wins; categories missing from YAML come from the fallback. This is
 * the resilience layer — a malformed install still has all 7 categories.
 */
export declare function mergeWithFallback(loaded: CategoryConfig[], fallback: CategoryConfig[]): CategoryConfig[];