/**
 * COMP002: dangling-wiring-ref
 *
 * Flags a wiring reference (`@Phase.field` or `@<component>.publish.*`,
 * carried in a step's `imageRef`/`jar`/`revision`/`inputs`/any other
 * capability-specific field — see ../../../components/component.ts's
 * `Wiring`) that points at a phase or component that does not exist:
 *
 *  - `@Phase.field` naming a phase not declared anywhere in this component's
 *    own `deploy` (top-level phase names only — a nested fan-out phase's
 *    name is addressed by its own name, never a parent's, matching how
 *    ../../../components/driver.ts's `resolveWiring` keys `phaseOutputs` by
 *    the phase the step ran directly under).
 *  - `@<component>.publish.<field>` naming a component that either is not
 *    discovered at all, or is discovered but not listed in this component's
 *    `dependsOn` — the graph only resolves an artifact reference for a
 *    declared dependency (composition-and-wiring.mdx#cross-component-outputs).
 *
 * Triggers on: `imageRef: "@Build.digest"` when no phase named "Build"
 * exists, or `jar: "@some-lib.publish.uri"` when "some-lib" is undiscovered
 * or missing from `dependsOn`.
 * OK: `imageRef: "@Publish.digest"` when a "Publish" phase exists in the same
 * component, or `jar: "@jar-lib.publish.uri"` when "jar-lib" is discovered
 * and listed in `dependsOn`.
 */
import type { ComponentCheck } from "../../component-checks.js";
export declare const comp002DanglingWiringRefRule: ComponentCheck;
//# sourceMappingURL=comp002-dangling-wiring-ref.d.ts.map