/**
 * Pilot: ALB/ECS target (#555, epic #551).
 *
 * Exercises the build + cross-stack + auto-rollback axes: `docker-build` →
 * `publish-image` (promote by digest, deploy-time) → `cfn-deploy` (importing
 * the shared ALB's listener/cluster/subnets as cross-stack outputs, resolved
 * by `chant graph --stacks` rather than a `describe-stacks | jq` pipeline
 * step — see composition-and-wiring.mdx#cross-stack-outputs) →
 * `ecs-update-service` → `wait-steady-state` + `health-gate`.
 *
 * This is the direct component-native replacement for the hand-rolled GitLab
 * pipeline in `examples/gitlab-aws-alb-api/src/pipeline.ts`: the
 * `describe-stacks`/`jq` glue in that pipeline's `deployService` job is
 * exactly the cross-stack `stackOutput()` wiring below, and its
 * `docker build`/`docker push` steps are the `docker-build` + `publish-image`
 * capabilities. `service` archetype: build → publish → apply → verify, the
 * fullest of the three archetypes.
 *
 * The JSON projection of this pilot is authoritative at
 * ../__fixtures__/alb-ecs-service.json (already schema-validated by
 * component-schema.test.ts) — this module is the real typed `Component`
 * authoring form (#560, ../component.ts) that composes to that same
 * document; see ./pilots.test.ts, which asserts the two never diverge.
 */
import type { Component } from "../component.js";
export declare const searchService: Component;
//# sourceMappingURL=alb-ecs.pilot.d.ts.map